Skip to content

Commit

Permalink
Rewrap text
Browse files Browse the repository at this point in the history
  • Loading branch information
vers-w committed Sep 12, 2024
1 parent a740933 commit fa38e36
Showing 1 changed file with 15 additions and 11 deletions.
26 changes: 15 additions & 11 deletions docs/src/user_guide/step1_requirements.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,22 @@
# Step 1: Understanding the requirements

To run wflow, several files are required. These include a settings file and
input data. The input data is typically separated into static maps and forcing data, and both
are provided in netCDF files, except for lake storage and rating curves that are supplied
via CSV files. Below is a brief overview of the different files:
To run wflow, several files are required. These include a settings file and input data. The
input data is typically separated into static maps and forcing data, and both are provided
in netCDF files, except for lake storage and rating curves that are supplied via CSV files.
Below is a brief overview of the different files:

- The `settings.toml` file contains information on the simulation period, links to the
input files (and their names in the netCDF files), and connect the correct variable names in the netCDF files to the variables and parameters of wflow.
- The `staticmaps.nc` file contains spatial information such as elevation, guage locations, land use, and drainage direction, etc. This file can also contain maps with parameter
input files (and their names in the netCDF files), and connect the correct variable names
in the netCDF files to the variables and parameters of wflow.
- The `staticmaps.nc` file contains spatial information such as elevation, guage locations,
land use, and drainage direction, etc. This file can also contain maps with parameter
values.
- The `forcing.nc` file contains time series data for precipitation, temperature and potential evaporation (as a 3D array).
- The `forcing.nc` file contains time series data for precipitation, temperature and
potential evaporation (as a 3D array).

Wflow supports several model configurations, each requiring slightly different input, but with a similar general structure. A wflow model configuration consists of a `vertical` concept like [SBM](@ref
vert_sbm), [HBV](@ref vert_hbv) or [FLEXTOPO](@ref vert_flextopo) in
Wflow supports several model configurations, each requiring slightly different input, but
with a similar general structure. A wflow model configuration consists of a `vertical`
concept like [SBM](@ref vert_sbm), [HBV](@ref vert_hbv) or [FLEXTOPO](@ref vert_flextopo) in
combination with `lateral` concepts that control how water is routed for example over the
land or river domain. For the wflow\_sbm model, different model configurations are possible.
The following configurations are supported in wflow:
Expand All @@ -28,5 +32,5 @@ The following configurations are supported in wflow:
- wflow\_sediment as post processing of wflow\_sbm or wflow\_hbv output

In the following pages, some examples will be given on how to prepare a basic wflow\_sbm
model. Sample data for other model configurations is provided in the [sample
data](@ref sample_data) section.
model. Sample data for other model configurations is provided in the [sample data](@ref
sample_data) section.

0 comments on commit fa38e36

Please sign in to comment.