Model Components#
The SfincsModel consists of several components that together
represent the full SFINCS model setup. Each component manages a specific part of the
model (e.g., configuration, grid definition, forcings, or output) and can be read from or
written to disk using the corresponding read() and write() methods. Furhermore,
each component has its own data attribute that stores the relevant data for that component,
and a create() method to generate or update the component data (see also Model Methods).
An overview of all model components is presented in HydroMT-SFINCS workflow diagram, and each component will be introduced in the following sections. For more details about each component, see the SFINCS documentation.
HydroMT-SFINCS workflow diagram#
Configuration component#
The configuration component manages the main SFINCS configuration settings and parameters. Only files or settings that are mentioned in the configuration file will be used by the SFINCS model.
Component |
Description |
Associated Files / Relations |
|---|---|---|
Model configuration settings and parameters. |
|
Regular grid components#
These components define the model grid and its physical parameters for SFINCS models on regular grids. The different components are interrelated, since they all share the same spatial grid definition.
Component |
Description |
Associated Files / Relations |
|---|---|---|
Base model grid. |
|
|
Elevation (bathymetry/topography). |
|
|
Active domain and boundary mask. |
|
|
Manning’s n roughness. |
|
|
Infiltration capacity. |
|
|
Initial water levels. |
|
|
Storage volume to account for green infrastructure. |
|
|
Subgrid table with cell-specific elevation and roughness data. |
|
Note
Please be aware that the indexfile is not describing a grid variable.
Instead, it is generated during the writing process based on the mskfile,
and it is utilized for the purpose of reading grid variables in binary files.
Geometries and structures#
These model components manage vector-based geometries and structures within the SFINCS model, such as observation points to monitor water levels at specific locations or weirs to represent flow control structures.
Component |
Description |
Associated Files / Relations |
|---|---|---|
Observation points for validation. |
|
|
Cross-section definitions. |
|
|
Weir locations and parameters. |
|
|
Thin dams and barriers. |
|
|
Drainage infrastructure. |
|
Forcing components#
These components handle time-varying boundary and meteorological forcings applied to the model, such as water level boundaries, discharge sources, precipitation, wind, and atmospheric pressure.
Component |
Description |
Associated Files / Relations |
|---|---|---|
Water level boundary conditions. |
|
|
Discharge source terms. |
|
|
Spatially and/or temporally variable rainfall. |
|
|
Spatially and/or temporally variable wind forcing. |
|
|
Atmospheric pressure fields. |
|
|
River network and flow attributes. |
|
Note
The rivers component is not directly used by the SFINCS model,
but it can be helpful for setting up discharge boundary conditions based on river network data.
Output component#
Component |
Description |
Associated Files / Relations |
|---|---|---|
Model simulation results |
|