...
Code Block | ||||
---|---|---|---|---|
| ||||
<map parameter="Mean wave direction" layer="1" fewsParameter="Wave.direction.mean.ext" fewsLocation="Guanabara.wave.ext"/> <map parameter="Mean wave period" layer="1" fewsParameter="Wave.period.mean.ext" fewsLocation="Guanabara.wave.ext"/> <map parameter="Peak wave direction" layer="1" fewsParameter="Wave.direction.peak.ext" fewsLocation="Guanabara.wave.ext"/> <map parameter="Peak wave period" layer="1" fewsParameter="Wave.period.peak.ext" fewsLocation="Guanabara.wave.ext"/> <map parameter="Sign.wave height" layer="1" fewsParameter="Wave.sign.height.ext" fewsLocation="Guanabara.wave.ext"/> |
For examples, see the adapterConfiguration_example_*.xml files attached to this WiKi page.
3. Template files and keywords
In the table below the various keywords are explained. It is important to note that these keywords are filled whenever they are encountered in a template file – the keywords are not associated with a particular type of file. The format for the keywords and any arguments there may be is as follows:
$(keyword: argument1, argument2, ...)
or, if there are no arguments:
$(keyword)
(Technical note: the entire text from the opening "$(" to the trailing ")" is replaced, without a trailing new line, by whatever the contents should be. The arguments should not contain commas parenthesis and there should be at least one space after the comma. This syntax makes it easy to implement the template mechanism.)
Delft3D-PART (example):
For PART the option <formatForPart>NEFIS</formatForPart> has been added to switch converting the model output from the binary map files to the NEFIS map files, because the binary map files do not support file sizes above 2GB and NEFIS map files do.
Code Block | ||||
---|---|---|---|---|
| ||||
<postAdapter>
<mapOutput>
<formatForPart>NEFIS</formatForPart>
<map parameter="Oil" layer="1" fewsParameter="Oil.simulated.L1" fewsLocation="delwaq.nonaggregated.L1"/>
<map parameter="localdepth" layer="20" fewsParameter="WaterDepth.sim" fewsLocation="delwaq.nonaggregated"/>
<map parameter="Oil disp" layer="1" fewsParameter="Oil.dispersed.simulated.L1" fewsLocation="delwaq.nonaggregated.L1"/>
<map parameter="Oil disp" layer="2" fewsParameter="Oil.dispersed.simulated.L2" fewsLocation="delwaq.nonaggregated.L2"/>
<map parameter="Oil disp" layer="3" fewsParameter="Oil.dispersed.simulated.L3" fewsLocation="delwaq.nonaggregated.L3"/> |
For examples, see the adapterConfiguration_example_*.xml files attached to this WiKi page.
3. Template files and keywords
In the table below the various keywords are explained. It is important to note that these keywords are filled whenever they are encountered in a template file – the keywords are not associated with a particular type of file. The format for the keywords and any arguments there may be is as follows:
$(keyword: argument1, argument2, ...)
or, if there are no arguments:
$(keyword)
(Technical note: the entire text from the opening "$(" to the trailing ")" is replaced, without a trailing new line, by whatever the contents should be. The arguments should not contain commas parenthesis and there should be at least one space after the comma. This syntax makes it easy to implement the template mechanism.)
Keyword | Description | |
---|---|---|
FLOW_TIME_START | Start of the simulation (format in accordance with Delft3D-FLOW). | |
FLOW_TIME_STOP | Stop of the simulation (format in accordance with Delft3D-FLOW) | |
FLOW_TIME_RST | Duration of the simulation – useful for setting the time interval of writing the restart files so that only one restart file is written at the end of the simulation. | |
FLOW_TIMESERIES | Placeholder to fill in the timeseries in the so-called tim format (only the time and data, not the header). | |
FLOW_MAPSTACK | Placeholder for the name of the file that will hold the scalar field data (as found in the map stack files). It should be followed by the name of the parameter:
| |
WAVE_TIMEFRAME | Placeholder to fill values for TimePoint from start time to end time with specified increment. Example: $(WAVE_TIMEFRAME: 60, USE_WATERLEVEL_FLOW, USE_CURRENTS_FLOW)
| |
WAQ_TIME_START | Start | |
Keyword | Description | |
FLOW_TIME_START | Start of the simulation (format in accordance with Delft3D-FLOW). | |
FLOW_TIME_STOP | Stop of the simulation (format in accordance with Delft3D-FLOW) | |
WAQFLOW_TIME_RSTSTOP | Duration of the simulation – useful for setting the time interval of writing the restart files so that only one restart file is written at the end of the simulation. | Stop of the simulation (format in accordance with Delft3D-WAQ/ECO: yyyy/mm/dd-hh:mm:ss) |
WAQFLOW_TIMESERIES | Placeholder to fill in the timeseries in the so-called tim WAQ /ECO format (only the time and data, not the header). | FLOW_MAPSTACK | Placeholder for the name of the file that will hold the scalar field data (as found in the map stack files). It should be followed by the name of the parameter:
WAVE_TIMEFRAME | Placeholder to fill values for TimePoint from start time to end time with specified increment. Example: $(WAVE_TIMEFRAME: 60, USE_WATERLEVEL_FLOW, USE_CURRENTS_FLOW)
| |
WAQ_TIME_START | Start of the simulation (format in accordance with Delft3D-WAQ/ECO: yyyy/mm/dd-hh:mm:ss) | |
WAQ_TIME_STOP | Stop of the simulation (format in accordance with Delft3D-WAQ/ECO: yyyy/mm/dd-hh:mm:ss) | WAQ_TIMESERIES | Placeholder to fill in the timeseries in the WAQ /ECO format (only the time and data, not the header). WAQ_MAPSTACK | Placeholder for the name of the file that will hold the scalar field data (as found in the map stack files). It should be followed by the name of the parameter:
WAQ_MAPSTACK | Placeholder for the name of the file that will hold the scalar field data (as found in the map stack files). It should be followed by the name of the parameter:
| |
PART_RUNID | The run ID for the Delft3D-PART computation (used in the filename.dat file) | |
PART_TIME_START | Placeholder to fill in start time in PART format, similar to WAQ and FLOW keywords. NOTE. PART requires the formating of the inp file to be very specific (incl. specific numbers of spaces/tabs before keywords.) Also, all text following the keyword will be replace/removed by the adapter when substituting the keyword | |
PART_TIME_STOP | Placeholder to fill in end time in PART format, similar to WAQ and FLOW keywords. NOTE. PART requires the formating of the inp file to be very specific (incl. specific numbers of spaces/tabs before keywords.) Also, all text following the keyword will be replace/removed by the adapter when substituting the keyword | |
PART_TIMESERIES | Placeholder to fill in the timeseries in the PART format, similar to the WAQ and FLOW timeseries keywords. | |
PART_NUMBER_BREAKPOINTS | Placeholder to fill in the number of time steps required for the wind input in the *.inp file. ; Wind_parameters | |
PART_RUNID | The run ID for the Delft3D-PART computation (used in the filename.dat file) | |
PART_TIME_START | Placeholder to fill in start time in PART format, similar to WAQ and FLOW keywords. | |
PART_TIME_STOP | Placeholder to fill in end time in PART format, similar to WAQ and FLOW keywords. | |
PART_TIMESERIES | Placeholder to fill in the timeseries in the PART format, similar to the WAQ and FLOW timeseries keywords. | |
PART_MAPSTACK | Placeholder to fill in mapstacks in the PART format. Example: ^(PART_MAPSTACK: x_wind,m s-1) | |
PART_INIFILE | File name for the initial patch - the header information is to be written by Delft-FEWS. Example: ^(PART_INIFILE: patch.ini) | |
PART_SHAPEFILE | File name for the shape file holding the polygon within which the particles will be released. Example: ^(PART_SHAPEFILE: patch.shp) Use in combination with the keyword "PART_INIFILE". The coordinates will be appended to the ini-file as written by FEWS. | |
TEKAL_FILE | Additional keyword for PART. Example: ^(TEKAL_FILE: dispers.pol) | |
TEKAL_VALUES | Additional keyword for PART. Example: ^(TEKAL_VALUES: lon.cleaned/obs1, lat.cleaned/obs1) | |
COUP_TIME_START | Start time of coupling (in seconds; time frame is that of Delft3D-FLOW) | |
COUP_TIME_STOP | Stop time of coupling (in seconds; ditto) | |
P.M. | Keywords specific to Delft3D-WAVE |
For examples, see the MDF, MDW, BCC, WND, BND and INP files attached to this WiKi page.
...