This repository contains all the lessons for hte basic WRF-Hydro training.
The easiest and recommended way to run these lessons is via the wrfhydro/training Docker container, which has all software dependencies and data pre-installed.
- Docker >= v.17.12
- Web browser (Google Chrome recommended)
If you have general questions about Docker, there are ample online resourves including the excellent Docker documentation at https://docs.docker.com/.
The best place ask questions or post issues with these lessons is via the Issues page of the GitHub repository at https://github.com/NCAR/wrf_hydro_training/issues.
Make sure you have Docker installed and that it can access your localhost ports. Most out-of-the-box Docker installations accepting all defaults will have this configuration.
Step 1: Open a terminal or PowerShell session
Step 2: Pull the wrfhydro/training Docker container for the desired code version Each training container is specific to a release version of the WRF-Hydro source code, which can be found at https://github.com/NCAR/wrf_hydro_nwm_public/releases. Note: Training IS NOT SUPPORTED for bleeding-edge, unreleased code
Issue the following command in your terminal to pull a specific version of the training corresponding to your code release version. In this example, we will pull the training container for v5.0.0.
docker pull wrfhydro/training:v5.0.0
Step 3: Start the training container Issue the following commnand in your terminal session to start the training Docker container.
docker run --name wrf-hydro-training -p 8888:8888 -it wrfhydro/training
The container will start and perform a number of actions before startign the training.
- First, the container will pull the model code corresponding to the specified major version, in this case v5.
- Second, the container will pull an example test case compatible with the model code release.
- Third, the container will launch a Jupyter Notebook server and echo the address to your terminal.
Note: Port forwarding is setup with the -p 8888:8888 argument, which maps your localhost port to the container port. If you already have sometihng running on port 8888 on your localhost you will need to change this number