This notebook demonstrates how to prepare a Wflow sediment model using the command line interace (CLI).
All lines in this notebook which start with !
are executed from the command line. Within the notebook environment the logging messages are shown after completion. You can also copy these lines and paste these in your shell to get more direct feedback.
Lets first check if the Wflow sediment model is recognized by hydromt
# this should return "wflow, wflow_sediment"
!hydromt --models
Using the hydromt build API we can setup a complete model from scratch. Let's get an overview of all the available options:
!hydromt build --help
The ini-file contains the model setup configuration and determines which components are build and in which order and optionally sets non-default arguments for each component. This configuration is passed to hydromt using -i <path_to_ini_file>
. We have prepared several example ini-files which are available in the model repository examples folder and from the docs(build_configuration).
Each header as shown between [...]
(e.g. [setup_basemaps]
) corresponds to a model component. All model components are explained in the docs(model_components).
We will load the default wflow sediment build ini file for inspection:
fn_ini = 'wflow_sediment_build.ini'
with open(fn_ini, 'r') as f:
txt = f.read()
print(txt)
# NOTE: copy this line (without !) to your shell for more direct feedback
!hydromt build wflow_sediment "./wflow_test_sediment" "{'subbasin': [12.2051, 45.8331], 'strord': 4, 'bounds': [11.70, 45.35, 12.95, 46.70]}" -r 0.00833 -i wflow_sediment_build.ini -vv
The example above means the following: run hydromt build with:
wflow_sediment
: i.e. build a wflow sediment model./wflow_test_sediment
: output model folder"{'subbasin': [12.2051, 45.8331], 'strord': 4, 'bounds': [11.70, 45.35, 12.95, 46.70]}"
: derive a subbasin with its outlet at the given x,y coordinates and within the given bounds [xmin, ymin, xmax, ymax] (WGS84) snapped to a river with minimum stream order (strord) of 4. All REGION options are described in the docs-r 0.0083333
: build the model at a 30 arc sec (~1km) resolution-i wflow_sediment_build.ini
: setup configuration file using-vv
: give some extra verbosity (2 * v) to display feedback on screen. Now debug messages are provided.Next we check which files have been created. The model root should contain two netcdf (.nc) files, one for the staticmaps and one for the forcing data, a wflow configuration (.toml) file. These files are sufficient to run the wflow sediment model. In addition several geometry (.geojson) files are saved in the staticgeoms folder. Finally, the setup process is logged in the hydromt.log file.
import os
root = 'wflow_test_sediment'
for path, _, files in os.walk(root):
print(path)
for name in files:
if name.endswith('.xml'):
continue
print(f' - {name}')
You can (copy and) adapt the following example notebooks in order to visualize your Wflow sediment model:
If you already have a hydrological Wflow model and you want to extend it in order to include sediment as well, then you do not need to build the wflow_sediment from scratch. You can instead update the wflow model with the additional components needed by wflow_sediment.
These components are available in the template wflow_extend_sediment.ini:
fn_ini = 'wflow_extend_sediment.ini'
with open(fn_ini, 'r') as f:
txt = f.read()
print(txt)
Let's update the hydrological Wflow model available from our example for the Piave subbasin:
# NOTE: copy this line (without !) to your shell for more direct feedback
!hydromt update wflow_sediment "wflow_piave_subbasin" -o "./wflow_test_extend_sediment" -i wflow_extend_sediment.ini -vv
The example above means the following: run hydromt update with:
wflow_sediment
: i.e. update a wflow_sediment model (in our case a wflow model but with wflow_sediment components)wflow_piave_subbasin
: hydrological wflow model folder-o "./wflow_test_extend_sediment"
: output combined wflow hydrology+sediment models-i wflow_extend_sediment.ini
: setup configuration file containing wflow sediment specific components-vv
: give some extra verbosity (2 * v) to display feedback on screen. Now debug messages are provided.