...
TStart | Start time of the model run, in units of Tunit relative to RefDate. |
|---|---|
TStop | End time of the model run, in units of Tunit relative to RefDate. |
RestartFile | Either * pathname of the input state file relative to the MDU file if the input state file is not empty (warm state start) or * empty string if the input state file is an empty dummy file of 0 bytes length (cold state start) or * empty string if there is no input state file at all (cold state start). |
RestartDateTime | The restart time, this is set equal to the start time of the model run. |
RstInterval | Interval (in seconds) for writing *_rst.nc restart files. |
...
MDU file name format
The mdu file(s) to update should be in the workDir specified in the netcdf run file. This program only supports:
a single mdu file with file name format <model_id>.mdu or
Valid example: gtsm.mdu(in case of domain decomposition) one mdu file for each partition with file name format <model_id>_<partition_number>.mdu
Valid example: gtsm_0000.mdugtsm_0001.mdugtsm_0002.mduThe restart file:
Restart file name format
In case of a warm state start, there should be exactly one input state file (restart file) for each mdu file. This program only supports a single input state file with file name format
- <model_id>_rst.nc , or
Valid example: gtsm_rst.nc - <model_id>_<timestamp>_rst.nc
Valid example: gtsm_rst.ncgtsm_20160407_140000_rst.nc(in
In case of domain decomposition
...
there should be one input state file for each partition with file name format
<model_id>_<partition_number>_rst.nc, or
Valid example: gtsm_0001_rst.nc<model_id>_<partition_number>_<timestamp>_rst.nc
Valid example: gtsm_0001_20160407_140000_rst.nc
Convert input grid time series (optional)
The netcdf file(s) specified in the property "input_grid_files_to_convert" will be converted to files in arcinfo/curvi format. Each netcdf file will be converted to a file with the same path and name as the netcdf file but with a different extension (.amu, .amv or .amp). If the property "input_grid_files_to_convert" is not specified, then this step does nothing.
...
Conversion variable to file extension
Each netcdf file should contain only one variable with grid data. A netcdf file with multiple variables with grid data results in an error. The extension of the created file depends on the name of the variable in the netcdf file
...
. For example the original file input/x_wind.nc is converted to input/x_wind.amu
| netcdf variable name | extension |
|---|---|
| x_wind | .amu |
| y_wind | .amv |
| air_pressure | .amp |
| precipitation | not supported by DFlowFM (for rainfall DFlowFM can use the netcdf file directly) |
| any other name | not supported by DFlowFM |
...
Auxiliary grid file
The format (meteo_on_equidistant_grid/meteo_on_curvilinear_grid) of each of the created files depends on whether there is an auxiliary grid file present for that file. To use an auxiliary grid file for a given netcdf file, it must have the same path and name as the netcdf file, but a different extension (.grd). If an auxiliary grid file is present, then the netcdf file will be converted to a curvi file of type meteo_on_curvilinear_grid that refers to the auxiliary grid file. Otherwise it will be converted to an arcinfo file of type meteo_on_equidistant_grid. For rectangular and curvilinear grids there must always be an auxiliary grid file present, otherwise an error is given. For regular grids no auxiliary grid file is needed.
| grid type | auxiliary grid (.grd) file needed | type of created file |
|---|---|---|
| regular | no | arcinfo file of type meteo_on_equidistant_grid |
| rectangular | yes | curvi file of type meteo_on_curvilinear_grid |
| curvilinear | yes | curvi file of type meteo_on_curvilinear_grid |
Order of grid cells written
The order of the grid cell values in the arcinfo/curvi grid file created by this adapter depend on the type of grid (regular/rectangular/curvilinear). For regular grids (arcinfo meteo_on_equidistant_grid file format or curvi meteo_on_curvilinear_grid file format) the grid cells are always ordered per row from left to right, starting with the upper row of the grid. For rectangular grids (curvi meteo_on_curvilinear_grid file format) the grid cells are always ordered per row from left to right, starting with the upper row of the grid. For curvilinear grids (curvi meteo_on_curvilinear_grid file format) the grid cells are always in the same order as in the netcdf file, which depends in turn on the order of the grid cells in the corresponding grid definition in Delft-FEWS (if the file was exported from Delft-FEWS). If an auxiliary grid (.grd) file is used, then the grid cell coordinates in the .grd file must be in the same order as the grid cell values in the corresponding curvi file. The easiest way to accomplish this is to run the adapter once, then check the order of the grid cell values in the created curvi file(s), then manually make sure that the grid cell coordinates in the corresponding .grd file(s) are in the right order.
Coordinate system used
The coordinate system for the coordinates in an arcinfo meteo_on_equidistant_grid file created by this adapter depends on the coordinate system used in the netcdf file, which depends in turn on the coordinate system (geodatum) in the corresponding grid definition in Delft-FEWS (if the file was exported from Delft-FEWS). Need to manually make sure that this is the same coordinate system as the coordinate system used by the model.
System requirements
- This program needs Java version 8 or higher.
- This program needs the following Java libraries:
- commons-httpclient-3.0.1.jar
- Delft_Util.jar (revision 60330)
- grib-8.0.jar
- log4j-1.2.14.jar
- netcdf-4.2.jar
- slf4j-api-1.5.6.jar
- slf4j-log4j12-1.5.6.jar
- TimeSeriesImport.jar (revision 60330)
...