Page History

...

It will read "ExtForceFileNew" value and "ExtForceFile" specifically for wind forcing.

[external forcing]
ExtForceFile      =
ExtForceFileNew   = FlowFM_bnd.ext

...

Other parameters like wind, precipitation and atmospheric pressure can be supplied by FEWS only for 2D using a netcdf export directly to the file-location the model expects the nc-file to be. In the model you can use the old-style ext format file (in mdu keyword ExtForceFile) to use these netcdf-files. How to do this can be found in the D-Flow FM manual.

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"

rr_dll component

Will be used if library "rr_dll" is configured as component within the dimr config file:

Since 2022.02 there is support for windxy tim files. Only 1 timeseries for windspeed and 1 for winddirection are supported in the pi xml file. The adapter looks at the parameterIds "Windspeed" and "Winddirection" and replaces the whole tim file with the values from these timeseries including new timesteps referenced to the refdate in the mdu file. It is advised to set METHOD=7 in the .ext file for wind timeseries.

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"

rr_dll component

Will be used if library "rr_dll" is configured as component within the dimr config file:

  <component name="DRR">
    <library>rr_dll</library>
    <workingDir>rr</workingDir>
    <inputFile>Sobek_3b.fnm</inputFile>
  </component>

...

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:

...

• dWaveNetcdfBoundaryFileToConvert = relative path of the boundary conditions netCdf file
• dWaveBoundaryFilePrefix = prefix for the filenames of the output ASCII files, the default prefix is  "WW3_"
• dWaveBoundaryFileNumberOfCopies = the number of file copies to provide for each boundary, the default number is 3
  
  

Installing and running the Delft3D-FM model on Windows and Linux

A Delft3D-FM model can be run on Windows and LINUX. Installation of the model binaries on Windows and Linux can be straight forward when simple models are run on single VM's. A typical Delft-FEWS configuration solution can be the following.

• Create a ModuleDataSet "D3D_bin_Windows.zip" with the Windows binaries
• Create a ModuleDataSet "D3D_bin_Linux.zip" with the Linux binaries
• Create a ModuleDataSet "D3D_bin_adapter.zip" with the Delft3D Dimr Java Adapter
• In your fss_windows_clientConfig.xml file add a line:  <autoExportModuleDataSet name="D3D_bin_Windows" exportDir="Modules"/>
• In your fss_linux_clientConfig.xml file add a line: <autoExportModuleDataSet name="D3D_bin_Linux" exportDir="Modules"/>
• In your Windows and Linux clientConfig.xml file add a line:  <autoExportModuleDataSet name="D3D_bin_adapter" exportDir="Modules"/>
• In your Delft-FEWS General Adapter executeActivity element, start the Delft3D model with the following command  <executable>%REGION_HOME%/Modules/Delft3DFM/bin_delft3dfm/$D3D_MODEL_EXE$</executable>
• In your fss_linux_global.properties add a line: D3D_MODEL_EXE=/bin/run_dimr.sh
• In your fss_windows_global.properties add a line: D3D_MODEL_EXE=dimr\\scripts\\run_dimr.bat

When a Delft-FEWS FSS is started the clientConfig.xml file automatically unzips the correct Delft3D-FM binaries to your \Modules folder ( \Delft3DFM). When the Delft3D-FM model is started in a workflow from the General Adapter the correct script is started to run the DIMR.

...