1515
1616[ ![ DOI:10.5066/P13EWPEV] ( https://img.shields.io/badge/DOI-10.5066/P13EWPEV-b4a9fe.svg )] ( https://doi.org/10.5066/P13EWPEV )
1717
18- [ ![ WholeTale] ( https://raw.githubusercontent.com/whole-tale/wt-design-docs/master/badges/wholetale-explore.svg )] ( https://dashboard.wholetale.org/run/64ae29e8a887f48b9f173678?tab=metadata )
19-
20-
2118<!-- START doctoc generated TOC please keep comment here to allow auto update -->
2219<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
23- ** Table of Contents**
2420
2521- [ About] ( #about )
2622- [ Installation] ( #installation )
@@ -51,34 +47,34 @@ of well-established hydrologic process modeling.
5147
5248For more information on the goals and status of pywatershed, please see the [ pywatershed docs] ( https://pywatershed.readthedocs.io/ ) .
5349
54-
5550## Installation
5651
5752` pywatershed ` uses Python 3.10 or 3.11.
5853
5954The ` pywatershed ` package is [ available on
6055PyPI] ( https://pypi.org/project/pywatershed/ ) but installation of all
6156dependencies sets (lint, test, optional, doc, and all) may not be reliable on
62- all platforms.
57+ all platforms.
6358
6459The ` pywatershed ` package is [ available on
6560conda-forge] ( https://anaconda.org/conda-forge/pywatershed ) . The installation
6661is the quickest way to get up and running by provides only the minimal set of
6762dependencies (not including Jupyter nor all packages needed for running the
68- example notebooks, also not suitable for development purposes).
63+ example notebooks, also not suitable for development purposes).
6964
7065We recommend the following installation procedures to get fully-functional
7166environments for running ` pywatershed ` and its example notebooks. We strongly
7267recommend using [ Mamba] ( https://mamba.readthedocs.io/en/latest/ ) to first
7368instal dependencies from the ` environment_y_jupyter.yml ` file in the
7469repository before installing ` pywatershed ` itself. Mamba will be much faster
75- than Ananconda (but the conda command could also be used).
70+ than Ananconda (but the conda command could also be used).
7671
77- If you wish to use the stable release, you will use ` main ` in place of
72+ If you wish to use the stable release, you will use ` main ` in place of
7873` <branch> ` in the following commands. If you want to follow development, you'll
7974use ` develop ` instead.
8075
8176Without using ` git ` (directly), you may:
77+
8278```
8379curl -L -O https://raw.githubusercontent.com/EC-USGS/pywatershed/<branch>/environment_w_jupyter.yml
8480mamba env create -f environment_w_jupyter.yml
@@ -97,53 +93,35 @@ pip install -e .
9793```
9894
9995(If you want to name the environment other than the default ` pws ` , use the
100- command
96+ command
10197` mamba env update --name your_env_name --file environment_w_jupyter.yml --prune `
10298you will also need to activate this environment by name.)
10399
104-
105- We install the ` environment_w_jupyter.yml ` to provide all known dependencies
106- including those for running the example notebooks. (The ` environment.yml `
107- does not contain Jupyter or JupyterLab because this interferes with installation
108- on WholeTale, see Getting Started section below.)
109-
100+ We install the ` environment_w_jupyter.yml ` to provide all known dependencies
101+ including those for running the example notebooks.
110102
111103## Getting started / Example notebooks
112104
113105Please note that you can browse the API reference, developer info, and index
114- in the [ pywatershed docs] ( (https://pywatershed.readthedocs.io/) ) . But
115- * the best way to get started with pywatershed is to dive into the example
116- notebooks * .
106+ in the [ pywatershed docs] ( < (https://pywatershed.readthedocs.io/) > ) . But
107+ _ the best way to get started with pywatershed is to dive into the example
108+ notebooks _ .
117109
118110For introductory example notebooks, look in the
119111[ ` examples/ ` ] ( https://github.com/EC-USGS/pywatershed/tree/main/examples> )
120112directory in the repository. Numbered starting at 00, these are meant to be
121113completed in order. Numbered starting at 00, these are meant to be completed
122- in order. Notebook outputs are not saved in Github. But you can run these
123- notebooks locally or using WholeTale (an NSF funded project supporting logins
124- from many institutions, free but sign-up or log-in required)
125- where the pywatershed environment is all ready to go:
126-
127- [ ![ WholeTale] ( https://raw.githubusercontent.com/whole-tale/wt-design-docs/master/badges/wholetale-explore.svg )] ( https://dashboard.wholetale.org )
128-
129- * [ Run latest release in WholeTale] ( https://dashboard.wholetale.org/run/64ae29e8a887f48b9f173678?tab=metadata )
130- * [ Run the develop branch in WholeTale] ( https://dashboard.wholetale.org/run/64ae25c3a887f48b9f1735c8?tab=metadata )
131-
132- WholeTale will give you a JupyterLab running in the root of this
133- repository. You can navigate to ` examples/ ` and then open and run the notebooks
134- of your choice. The develop container may require the user to update the
135- repository (` git pull origin ` ) to stay current with development.
114+ in order. Notebook outputs are not saved in Github.
136115
137116Non-numbered notebooks in ` examples/ ` cover additional topics. These
138117notebooks are not yet covered by testing and you may encounter some
139118issues. In ` examples/developer/ ` there are notebooks of interest to
140119developers who may want to learn about running the software tests.
141120
142-
143121## Community engagement
144122
145123We value your feedback! Please use [ discussions] ( https://github.com/EC-USGS/pywatershed/discussions )
146- or [ issues] ( https://github.com/EC-USGS/pywatershed/issues ) on Github.
124+ or [ issues] ( https://github.com/EC-USGS/pywatershed/issues ) on Github.
147125For more in-depth contributions, please start by reading over
148126the pywatershed
149127[ DEVELOPER.md] ( https://github.com/EC-USGS/pywatershed/blob/develop/DEVELOPER.md ) and
@@ -164,4 +142,4 @@ software as needed pursuant to further analysis and review. No warranty, express
164142is made by the USGS or the U.S. Government as to the functionality of the software and related
165143material nor shall the fact of release constitute any such warranty. Furthermore, the software
166144is released on condition that neither the USGS nor the U.S. Government shall be held liable
167- for any damages resulting from its authorized or unauthorized use.
145+ for any damages resulting from its authorized or unauthorized use.
0 commit comments