The DIMR-software is used to run a SOBEK 3 model in Delft-FEWS. In the General Adapter of Delft-FEWS we refer to the different components of the dimr-tool. This wiki will describe what you need to do to convert a SOBEK3 model to a dimr-model and how to set-up the different components of your Delft-FEWS configuration. Read the steps in this guide to implement your SOBEK 3 model in Delft-FEWS using the dimr-software. When updating an existing model, some steps are not necessary.
The Delft-FEWS DIMR-adapter requires a fixed folder structure:
|dimr_bin||sub-folder with binaries for the DIMR-software.|
|dimr_model||sub-folder with DIMR-files that describe the SOBEK3 model.|
|fews-dimr-adapter-bin||sub-folder with binaries for the fews adapter that communicates with the DIMR.|
|Input||sub-folder with input files requried to run the model.|
|Logs||sub-folder for the log-files that are created during the model run.|
Follow the steps below to set-up a DIMR model folder in your Delft-FEWS system. Step 1 can be skipped when updating an existing model.
|Create a rootDir folder for your SOBEK 3 model at $REGION_HOME$/Modules/<put_your_rootDir_here>. All sub-folders described in the table above can be put in this Modules folder.|
The contents of the Modules folder can now be filled. We will start with the getting the dimr_bin files.
There are two ways for getting the dimr_bin files:
It is good practice to add a README.txt file in the dimr_bin directory where you document to DIMR version and from where you got the DIMR files.
The actual model files must be created by converting your SOBEK 3 model. DeltaShell contains standard functionality to aid you in this step.
It is possible that a message will appear in DeltaShell stating that your project was made in an older version and needs to be migrated to the latest version of DeltaShell. Press "Yes" and the model will automatically migrate to this version. If this is not preferred, because of new model developments or stability, use the DeltaShell which belongs to the SOBEK 3 version you used to create the model.
When your model can finish awithout displaying errors it is possible to convert the SOBEK 3 model to a dimr-model.
The contents of the fews-dimr-adapter-bin folder can be downloaded.
The DIMR and Delft-FEWS are communicating through the fews adapter. This adapter is part of Delft-FEWS and must be downloaded from the build.deltares.nl:
The folders Input and Logs will be filled when you run the model.
When the contents of every directory is set-up, we can run the DIMR model. The model can be executed using a batch file with an argument pointing to the DIMR configuration xml file.
You could enter this command in a seperate batch file for easier starting the model run.
In SOBEK 3 you can specify for which parameters you want to write the output. This is the same in the DIMR model and can be specified in the *.md1d file located in .\dimr_model\dflow1d.
Default, all results options are set to None. Apply the same output options as used in the SOBEK 3 model (e.g. Current, Average, ...)
DIMR has the option to make cache files of the SOBEK 3 model to read the model itself faster. This can be up to 100 times faster, because it does not have to processing large ASCII files. Therefore, it is good practice to generate the cache files.
To make the cache files, do the following:
Delft-FEWS will need a state file to be able to run the SOBEK model. In order to generate the first state files of the SOBEK model it is recommended to do a stand-alone run of the DIMR from the command line (see How to run the DIMR model? how to do that).
or in newer versions of the software
for newer versions of the software
Delft-FEWS can distribute model files to FSS machines. It is recommended to zip the model files and put it in the Delft-FEWS configuration.
Not yet completed
For more detailed information on the use of the General Adapter Module, see this link.
An example of the general section of the general adapter can be found below.
In the example configuration above it can be seen that the working directory of the DIMR should always be the folder ./dimr_model. The Delft-FEWS exports timeseries to the folder .\Input. After the modelrun is completed the output of the model is expected in the folder .\dflow1d/output.
The activities section is divided into four sub-sections: startUp-, export-, execute- and importActivities. The contents of all of these sections will be discussed in the info sections below. When you want to test your configuration during the building process then it is recommended to start with the startUpActivity, ExportActivities and ExecuteActivity sections. When no information (e.g. timeseries, states) are provided to the model DIMR will take its own default timeseries and states to perform a model run. Hence, this trick enables you to test if the model can be run from Delft-FEWS. The importDir can be checked to see if output has been generated.
Similarly, it is also possible to define a single input timeseries in the exportActivities. The DIMR will add default values to the missing timeseries in order to start the run. This trick allows you to check early on whether your ExportActivity and IdMapping is working properly.
The startUpActivities are typically used to purge the model directory in the Modules folder to ensure a clean slate. See example below
The exportActivities are used to export all the necessary data and the model itself. These typically consists of (in order): exportStateActivity, exportTimeSeriesActivities, exportDataSetActivity and exportRunFileActivity. See examples below.
This activity exports the state of the model. This can be a cold state (the one generated under How to generate ColdStateFiles?) or a warm state saved in the Delft-FEWS database.
This activity exports all the necessary data from FEWS to be used in the model. There can be multiple activities.
This activity exports the ModuleDataSet file to the working directory.
This activity makes a run xml file which the pre- and post adapter uses to distribute the timeseries to the correct locations for the model to pick up.
In the ImportActivities the state files and the timeseries can be imported to Delft-FEWS.
It is important to convert the extension of the state files before you import it to Delft-FEWS, this can be done by adding the </relativeExportFile> to your configuration.
The new DimrPreAdapter needs to be called with as only argument a reference to the run file.
Diagnostics can be ignored because it will write a plain text file dimr_pre_adapter.log in the workDir.
<executeActivity> <description>Run DIMR FEWS pre-adapter</description> <command> <className>nl.deltares.dimr.DimrPreAdapter</className> <binDir>%ROOT_DIR%/fews-dimr-adapter-bin</binDir> </command> <arguments> <argument>%ROOT_DIR%/input/pi-run.xml</argument> </arguments> <timeOut>1200000</timeOut> <ignoreDiagnostics>true</ignoreDiagnostics> </executeActivity>
In the pi run file property with key="dimrConfigFile" must be present with a reference to the dimr configuration file. This reference must be relative to the parent directory of the pi run file.
If multiple pi time series files are exported, it must be specified which file is meant for which component, there are 3 different properties for the components:
The time series xml files must be numbered in the order they appear in the <inputTimeSeriesFile> elements
<?xml version="1.0" encoding="UTF-8"?> <Run xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.wldelft.nl/fews/PI" xsi:schemaLocation="http://www.wldelft.nl/fews/PI http://fews.wldelft.nl/schemas/version1.0/pi-schemas/pi_run.xsd" version="1.5"> <timeZone>0.0</timeZone> <startDateTime date="2017-03-26" time="06:00:00"/> <endDateTime date="2017-03-29" time="06:00:00"/> <time0 date="2017-03-26" time="06:00:00"/> <workDir>X:\XXX\DimrPreAdapterTest\piRunFile1d2dRTC\dimr_model</workDir> <inputTimeSeriesFile>X:\XXX\piRunFile1d2dRTC\Input\export_pi_flow1d.xml</inputTimeSeriesFile> <inputTimeSeriesFile>X:\XXX\piRunFile1d2dRTC\Input\export_pi_fm.xml</inputTimeSeriesFile> <inputTimeSeriesFile>X:\XXX\piRunFile1d2dRTC\Input\export_pi_fbc.xml</inputTimeSeriesFile> <outputDiagnosticFile>notUsed.xml</outputDiagnosticFile> <properties> <!-- Reference to dimr configuration file, relative to parent directory of the/this pi-run.xml file --> <!-- This file will be read to see which components of the dimr are used and find references to .md1d, .mdu, flow1d2d.ini and/or fbc runtime config --> <string key="dimrConfigFile" value="../dimr_config.xml"/> <!-- Specify which of the above time series xml files is meant for flow1d --> <string key="piFileForFlow1d" value="inputTimeSeriesFile-1"/> <!-- Overwrite RstInterval value in the .mdu file with this property --> <string key="restartIntervalForFm" value="600"/> <!-- Specify which of the above time series xml files is meant for FM --> <string key="piFileForFm" value="inputTimeSeriesFile-2"/> <!-- Specify which of the above time series xml files is meant for FBC (rtc1) --> <string key="piFileForFbc" value="inputTimeSeriesFile-3"/> <!-- Will write the pi time series values for fbc as binary in timeseries_import.bin--> <string key="piTimeSeriesAsBin" value="true"/> <!-- Will convert the specified boundary NetCDF file to ASCII write the pi time series values for fbc as binary in timeseries_import.bin--> <string key="dWaveNetcdfBoundaryFileToConvert" value="input/boundary.nc"/> <!-- Optional settings for conversion of boundary file to ASCII, values shown here are default--> <string key="dWaveBoundaryFilePrefix" value="WW3_"/> <string key="dWaveBoundaryFileNumberOfCopies" value="3"/> </properties> </Run>
The dimr configuration file will be read to find the components that are being used so it knows which files need to be changed.
<?xml version="1.0" encoding="UTF-8"?> <dimrConfig xsi:schemaLocation="http://schemas.deltares.nl/dimr http://content.oss.deltares.nl/schemas/dimr-1.0.xsd" xmlns="http://schemas.deltares.nl/dimr" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <documentation> <fileVersion>1.00</fileVersion> <createdBy>Deltares, Coupling Team</createdBy> <creationDate>2018-07-07T14:49:48.9157275Z</creationDate> <control> <parallel> <startGroup> <time>1 60 2678500</time> <coupler name="1d2d_to_rtc"/> <start name="real-time control"/> <coupler name="rtc_to_1d2d"/> </startGroup> <start name="1d2d"/> </parallel> </control> <component name="real-time control"> <library>FBCTools_BMI</library> <workingDir>rtc</workingDir> <inputFile>.</inputFile> </component> <component name="1d2d"> <library>flow1d2d</library> <workingDir>1d2dcoupler</workingDir> <inputFile>1d2d.ini</inputFile> </component> <coupler name="rtc_to_1d2d"> <sourceComponent>real-time control</sourceComponent> <targetComponent>1d2d</targetComponent> <item> <sourceName>output_Langel_zu_Crest level (s)</sourceName> <targetName>water flow 1d/weirs/Langel_zu/structure_crest_level</targetName> </item> <item> <sourceName>output_02_Wehr_Duis~~1_Crest level (s)</sourceName> <targetName>water flow 1d/weirs/02_Wehr_Duis~~1/structure_crest_level</targetName> </item> </coupler> <coupler name="1d2d_to_rtc"> <sourceComponent>1d2d</sourceComponent> <targetComponent>real-time control</targetComponent> <item> <sourceName>water flow 1d/observations/P_Langel/water_level</sourceName> <targetName>input_P_Langel_Water level (op)</targetName> </item> <item> <sourceName>water flow 1d/observations/RuhrOWDuisburg/water_level</sourceName> <targetName>input_RuhrOWDuisburg_Water level (op)</targetName> </item> </coupler> </dimrConfig>
Also when the <time> element is present within <control> <parallel> <startGroup> its contents will be replaced with the appropriate values.
Will be used if library "FBCTools_BMI" is configured as component within the dimr config file
<component name="real-time control"> <library>FBCTools_BMI</library> <workingDir>rtc</workingDir> <!-- Look hardcoded for rtcRuntimeConfig.xml --> <inputFile>.</inputFile> </component>
It will look for the hardcoded file name rtcRuntimeConfig.xml in working directory relative to the parent dir of dimr config file.
It will replace start date and end date in rtcRuntimeConfig.xml with the appropriate values.
It will look for the hardcoded file name timeseries_import.xml in the working dir and insert all timeseries from the time series file configured by "piFileForFbc" (or the first time series xml if there is only 1) by matching headers.
Will be used if library "dflowfm" is configured as component within the dimr config file
<component name="dflowFM"> <library>dflowfm</library> <workingDir>fm</workingDir> <inputFile>mackay.mdu</inputFile> </component>
It will look for the .mdu file in working directory relative to the parent dir of dimr config file.
It will read "ExtForceFileNew" value.
[external forcing] ExtForceFile = ExtForceFileNew = FlowFM_bnd.ext
It will look for .ext file relative to .mdu file parent directory and extract all "forcingfile" properties from it.
[boundary] quantity = waterlevelbnd locationfile = mackay_bnd.pli forcingfile = mackay_bnd.bc [boundary] quantity = rainfall locationfile = mackay_ugrid_wgs84_net.nc forcingfile = ..\input\mackay_rain.bc
Insert all timeseries from "piFileForFm" (or the first time series xml if there is only 1) into all .bc files (relative to .ext file parent dir) by matching headers.
In the .mdu file itself it will replace Tstart, Tstop and RstInterval with the appropriate values.
RstInterval can be overwritten by a property in the run info file called "restartIntervalForFm"
Will be used if library "cf_dll" is configured as component within the dimr config file
<component name="Hydrodynamics"> <library>cf_dll</library> <workingDir>dflow1d</workingDir> <inputFile>Hydrodynamics.md1d</inputFile> </component>
It will look for the .md1d file in working directory relative to the parent dir of dimr config file.
It will replace StartTime and StopTime with the appropriate values.
It will look for "boundCondFile" to find .bc file (relative to .md1d file parent dir) and insert all timeseries from "piFileForFlow1d" (or the first time series xml if there is only 1) by matching headers.
Will be used if library "flow1d2d" is configured
<component name="1d2d"> <library>flow1d2d</library> <workingDir>1d2dcoupler</workingDir> <!-- Will be read to find references to .md1d and. mdu file--> <inputFile>1d2d.ini</inputFile> </component>
It will look for the .ini file in working directory relative to the parent dir of dimr config file.
[Model] type = Flow1D name = water flow 1d directory = ..\dflow1d modelDefinitionFile = water flow 1d.md1d [Model] type = FlowFM name = FlowFM directory = ..\dflowfm modelDefinitionFile = FlowFM.mdu
It will extract .md1d file (with directory and model definition file relative to parent dir of the .ini file) by looking for model = Flow1D
It will extract .mdu file (with directory and model definition file relative to parent dir of the .ini file) by looking for model = FlowFM
It will process the .md1d and .mdu file the same way as described in DFlow1D and DFlowFM component
Will be used if library "wave" is configured
<component name="1d2d"> <library>wave</library> <workingDir>wave</workingDir> <inputFile>stmartin.mdw</inputFile> </component>
It will look for the .mdw file in working directory relative to the parent dir of dimr config file.
At this point the DIMR adapter only performs a conversion of the boundary conditions NetCDF file to ASCII format. The relative path of the netCDF file to convert must be provided in the PI runinfo file using the dWaveNetcdfBoundaryFileToConvert property as shown in the example runinfo file above. Two additional properties are provided, to summarize: