ABSTRACT:

This includes the basic design idea of the composite resource type for discussion

ABSTRACT:

The HydroDS tasks required to be executed to get complete UEB model inputs for an example watershed are given in the Python file “HydroDS_UEB_Setup”. This file calls functions from the other file, "hydrods_python_client" that has declarations for data service functions available from HydroDS.

To run the workflow for a different watershed in the Western US, modify the coordinates of the watershed boundary, outlet location, the start and end time of model period, and the spatial reference (projection) information in the form of EPSG Code (http://spatialreference.org/ref/epsg/). The commands in the workflow script can also be called interactively from any Python command line, or from a user application that uses incorporates the Python Client Library.

For watersheds outside of the Western US, but in the CONUS, you need to upload your own DEM. The services are currently limited to the US.
You need to have a HydroDS account to use these services.

These scripts are for the following paper
Gichamo, T. Z., N. S. Sazib, D. G. Tarboton and P. Dash, (2020), "HydroDS: Data Services in Support of Physically Based, Distributed Hydrological Models," Environmental Modelling & Software, https://doi.org/10.1016/j.envsoft.2020.104623.

ABSTRACT:

This is the model simulation of snow water equivalent in Logan River watershed from 2008 to 2009. The model used is the Utah Energy Balance model which is a snowmelt model. The simulation result is used as the input data for SAC-SMA model to simulate the stream flow of the watershed.

ABSTRACT:

This is a resource to test registration of metadata in iguide catalog.

ABSTRACT:

Testing timeout error with file list endpoint.

ABSTRACT:

IGUIDE registration testing

ABSTRACT:

IGUIDE register HS resource testing

ABSTRACT:

This netCDF data is the simulation output from Utah Energy Balance (UEB) model.It includes the simulation result of snow water equivalent during the period Oct. 2009 to June 2010 for TWDEF site in Utah.

ABSTRACT:

This resource contains updated (code re-organization and cleanup) of Ayman's notebooks from the following 3 resources.

- AORC Notebook https://www.hydroshare.org/resource/72ea9726187e43d7b50a624f2acf591f/
- NWM retrospective data retrieval https://www.hydroshare.org/resource/6ca065138d764339baf3514ba2f2d72f/
- HydroFabric subsetter and retrieval https://www.hydroshare.org/resource/631be88704ef4167b12e9ad9d2529ba9/

ABSTRACT:

This resource contains the following bash scripts which can be used by the user in any of the JupterHub instances accessible via the "Open with" functionality of HydroShare to create conda environment to run AORC related notebooks. In order to run any of the listed bash script files in JupyterHub, first make the file executable using the JupyterHub terminal. Here is an example:

chmod +x setup_aorc_conda_env_cuahsi_jh.sh

Then the above script can be executed from the command line as follows:

./setup_aorc_conda_env_cuahsi_jh.sh

After executing the script as above, it will create a new conda environment called 'aorc'. It will also register this new conda environment as a new Jupyter kernel with name 'Python [conda env:.conda-aorc]'. In order for any of the AORC related notebooks to use this kernel you have to first shut down all kernels and then use the option 'Change Kernel" to select this new kernel.

- setup_aorc_conda_env_cuahsi_jh.sh (This script should be used in CUAHSI JupyterHub to create a new conda environment called 'aorc')

- setup_aorc_conda_env_cybergis_jh.sh (This script should be used in CyberGIS Jupyter for Water) to create a new conda environment called 'aorc')

- environment.yml (This file contains the python modules needed to run the AORC notebooks - similar to requirements.txt file used with pip install). The above script files use this yml file to install the python modules listed in that file.

- delete_aorc_conda_env_cuahsi_jh.sh (This script can be run to delete the conda env 'aorc' in CUAHSI JupyterHub)

- delete_aorc_conda_env_cybergis_jh.sh (This script can be run to delete the conda env 'aorc' in CyberGIS Jupyter for Water)

- setup_aorc_conda_env_2i2c_jh.sh (This script should be used in 2i2c JupyterHub to create a new conda environment called 'aorc')

- environment-2i2c.yml (This file is used in the above script that creates the aorc conda env in 2i2c. This environment file has few python modules for conda installation)

- requirements-2i2c.txt (This file is used in the above script that creates the aorc conda env in 2i2c to pip install most of the python modules needed for AORC notebooks. The reason for using 'pip install' in case of 2i2c to install majority of python modules for the new conda environment is that 2i2c gives error 'no space left on device' if the modules are installed using 'conda'.)

- delete_aorc_conda_env_2i2c_jh.sh (This script can be run to delete the conda env 'aorc' in 2i2c JupyterHub)

- sample_commands_to_create_conda_env_jh.md (This file contains example commands to create a new conda environment - without using a bash script)

How to update the aorc conda environment after it has been created?
Update here means installing additional python modules or upgrading to a newer version of any modules that is already installed in the aorc conda environment. The following commands are applicable to CUAHSI and CyberGIS JH instances.

- Update the environment.yml file by adding new modules or updating the version of any modules in that file.

- In the JupyterHub instance, use a terminal and run the following 2 commands:

- conda activate aorc
- mamba env update -f environment.yml

Update aorc environment in 2i2c:
If you have updated the environments-2i2c.yml, run
- conda env update -f environment-2i2c.yml

If you have updated the requirements-2i2c.txt file, run
- pip install -r requirements-2i2c.txt

If you just want to install fe new modules or upgrade existing modules without updating environment or requirements file, then run
conda install <module-1-name> <module-2-name>
OR
pip install <module-1-name> <module-2-name>

NOTE: It is better to update environment or requirements file when there is a need to update the environment as it helps reproducibility.