...
The WATFLOOD model files, including the WATFLOOD binaries are saved in the /Config/ModuleDataSet directory. These are copied to the /Modules/WATFLOOD/$BASIN$ directory during the exportDataSet activity in the General Adapter file.
...
General Design choices for the WATFLOOD preAdapter
- The adapter will be written in Java (no FORTRAN)
- The (pre)Adapter will only write to the
...
- nudge_flags.xyz
...
- The file is space delineated. Only the first 4 columns are read by WATFLOOD. The rest of the line is ignored.
- The nudge flag is stored in column 3 (see image above - green box)
- The preAdapter will use the stationId (column 4, see image above - red box) to make the connection to update the correct row in the nudge_flags.xyz file.
- The nudge flags file has 8 characters for the stationId.
- Reading the nudge_flags.xyz file is automatically left justified. Trailing blanks are chopped and not used for matching.
- The WATFLOOD executable (version October 2019) now pick up the stationId instead of lat/lon to match to the flows for nudging.
Design Choices for nudge_flag updating
...
- and basin parameter .csv file, not read from it (and pass info back to FEWS)
- The adapter runs with (any or all) of the following updating mechanisms. I.e.: the preAdapter also works when either the nudge_flag or the parameter updating is configured.
- The parameter files exported from Delft-FEWS are in pi-xml format.
- The WATFLOOD adapter is coded to read/parse runFiles in netCDF format. Exporting to pi-xml format and referencing the xml runfile with the preAdapter is not supported.
| Anchor | ||||
|---|---|---|---|---|
|
The nudge_flags file is part of the model configuration. It is typically located in the following directory: /strfw/nudge_flags.xyz
The file is space delineated. Only the first 4 columns are read by WATFLOOD. The rest of the line is ignored. The nudge flag is stored in column 3 (see image above - green box), the preAdapter will use the stationId (column 4, see image above - red box) to make the connection to update the correct row in the nudge_flags.xyz file. The nudge flags file has 8 characters for the stationId. Reading the nudge_flags.xyz file is automatically left justified. Trailing blanks are chopped and not used for matching.
The WATFLOOD executable (version October 2019) now pick up the stationId instead of lat/lon to match to the flows for nudging.
Design Choices for nudge_flag updating
We assume that all locations in the nudge flags params xml (as exported by the General Adapter from Delft-FEWS) file are present in the nudge_flags.xyz file, no new locations can be dynamically introduced by the params file.
...
To indicate to the preAdapter that nudge flags updating should take place, 2 specific keys need to be defined in the RunInfo file
...
:
...
- <string key="WFNudgeFlagsFile" value="strfw/nudge_flags.xyz"/>
(indicates to the preAdapter where the nudge file is located.) - <string key="NudgeFlagsParamsFile" value="strfw/$BASIN$_NudgeFlags_params.xml"/>
(indicates to the preAdapter where the nudge flags parameter file for nudge flags updating is located.
This then also indicates that nudge flags updating should take place)
| Info | ||
|---|---|---|
| ||
the location of the nudge_flag and Params files should be defined relative to the directory where the run_info file is written. |
Convention for the IdMapping in the params xml file for Nudge Flags
...