...
- The ability to switch values on/off for streamflow nudging within the WATFLOOD nudge_flags file;
- The ability to update model parameters on-the-fly for a model simulation in the WATFLOOD basin parameter file
In November 2022 the model adapter was updated to update model routing parameters on-the-fly for a model simulation in the WATFLOOD basin parameter file
| Info | ||
|---|---|---|
| ||
This documentation page is under development |
...
locationId is free, not required to be equal to the 'Parameter block name' in the *_par.csv file. E.g. 'SnowParameters', because all parameters are unique
parameterId: The naming convention for the parameter id's is as follows: <parameter_id>-<column number>[*-**]
The <parameter_id> part is required. It should be equal to the WATFLOOD parameter id. The <parameter_id> element is 'closed' by a "-"(hyphen) character
The <column number> bit is required. It specifies which column needs to be updated by the preAdapter.
"01" is to be interpreted as the first column after the column with the parameterId
Leading zero's are not required, this part of the parameterId will be parsed as a number
The [-*] part is free to choose (and optional).
The values in the parameter.xml files from Delft-FEWS will be read as strings and are not interpreted.
This means that the representation in the params file should be correct.
Only exception is NaN's. These will not be read in/used and will be ignored. For parameterId's with NaN's, no warning/info message will be generated
An example where these design choices are followed is given in the screenshot below, where we want to update the "base" parameter in the basin file, for 19 landclasses
Design Choices
The adapter will parse the relevant lines of the WF parameter csv file to columns (comma separated) and replace . A parameter_id in the par file from Watflood always starts with a ":", e.g. ":fm" or ":base"
One can update all parameters with this design, if the parameterId convention is followed.
If less parameters are provided in the params.xml file as compared to the amount of columns as defined in the WATFLOOD par.csv file, the remainder of parameters will not be touched and stay in place. A WARN message should be thrown if this is the case to indicate to the user/configurator that only a subset of available parameters are being updated/passed to the model.
We will provide a specific key in the RunInfo file:
<string key="WFBasinParFile" value="%ROOT_DIR%/basin/lnrb_par.csv"/>
This file will be used for the parameter updating.
<string key="BasinParamsFile" value="%ROOT_DIR%/basin/$BASIN$_Basin_params.xml"/>
indicates to the preAdapter where the parameter file for parameter updating is located.
This then also indicates that parameter updating should take place.
Since November 2022, Routing parameters can also be changed on the fly when specified in a separate *_params.xml file
<string key="RoutingParamsFile" value="%ROOT_DIR%/basin/$BASIN$_Routing_params.xml"/>
indicates to the preAdapter where the routing parameter file for parameter updating is located.
This then also indicates that routing parameter updating should take place
Configuration Instructions for updating Basin Parameters
...