WES
WES is a two-dimensional model for hurricane calculations.
...
- The model needs Matlab Compiler runtime 2013b x64 v8.2 to be installed
- The adapter needs Java version 1.7 or higher.
- The adapter needs the following Java libraries:
- castor-0.9.5.jar
- commons-httpclient-3.0.1.jar
- Delft_Util.jar
- fews-WES-adapter.jar
- log4j-1.2.14.jar
- netcdf-4.2.jar
- slf4j-api-1.5.6.jar
- slf4j-log4j12-1.5.6.jar
- xercesImpl.jar
Example configuration
...
Start up activities
As a first activity it can be useful to delete all files present in the workDir, if for example it would be filled with files from a previous run.
...
Code Block |
---|
|
CYCLONE_PAR._FILE = wes_adapter_track.trk
SPIDERS_WEB_DIMENS. = 500 36
RADIUS_OF_CYCLONE = 1000000.0
WIND CONV. FAC (TRK)= 0.88
NO._OF_HIS._DATA = 0
HIS._DATA_FILE_NAME =
OBS._DATA_FILE_NAME =
EXTENDED_REPORT = yes
|
By replacing $WAVE_HEIGHT$ with value 5 cil0_30mv3.xyz will be:
Code Block |
---|
title | wes_adapter_track.trk |
---|
|
* File for tropical cyclone
* File contains Cyclone information ; TIMES in UTC
* File generated by WES adapter
* UNIT = Kts, Nmi ,Pa
* METHOD= 1:A&B; 4:Vm,Pd; Rw default
* 2:R100_etc; 5:Vm & Rw(RW may be default - US data; Pd = 2 Vm*Vm);
* 3:Vm,Pd,RmW, 6:Vm (Indian data); 7: OLD METHOD - Not adviced
* Dm Vm
0.0 0.0
* Date and time lat lon Method Vmax Rmax R100 R65 R50 R35 Par B Par A Pdrop
* yyyy mm dd HH deg deg (-) (kts) (NM) (NM) (NM) (NM) (NM) (-) (-) (Pa)
2000 11 03 00 14.00 -80.00 4 30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1400
2000 11 03 06 15.00 -80.00 4 35 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1500
2000 11 03 12 16.00 -80.00 4 40 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1600
2000 11 03 18 17.00 -80.00 4 45 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 2000
2000 11 04 00 17.00 -80.00 4 50 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 4000
2000 11 04 06 17.00 -81.00 4 55 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 7000
2000 11 04 12 18.00 -81.00 4 60 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 10000
2000 11 04 18 18.00 -81.00 4 65 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 12000
2000 11 05 00 18.00 -81.00 4 70 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 13000
2000 11 05 06 18.00 -81.00 4 75 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 13000
2000 11 05 12 19.00 -82.00 4 80 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 12000
2000 11 05 18 19.00 -82.00 4 85 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 12000
2000 11 06 00 19.00 -82.00 4 90 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 11000
2000 11 06 06 20.00 -82.00 4 95 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 11000
2000 11 06 12 20.00 -82.00 4 100 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 11000
2000 11 06 18 20.00 -81.00 4 105 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 10000
2000 11 07 00 21.00 -81.00 4 110 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 10000
2000 11 07 06 21.00 -81.00 4 115 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 9000
2000 11 07 12 21.00 -81.00 4 120 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 9000
2000 11 07 18 21.00 -80.00 4 125 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 8000
2000 11 08 00 20.00 -80.00 4 130 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 7000
2000 11 08 06 20.00 -80.00 4 135 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 6000
2000 11 08 12 19.00 -80.00 4 140 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 5000
2000 11 08 18 19.00 -80.00 4 145 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 4000
2000 11 09 00 18.00 -79.00 4 150 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 1E+30 3000
|
...
Code Block |
---|
| xml |
---|
| xml |
---|
title | module run execute activity |
---|
|
<executeActivity>
<command>
<executable>wes.exe</executable>
</command>
<arguments>
<argument>wes_input.inp</argument>
</arguments>
<timeOut>99999999</timeOut>
<ignoreDiagnostics>true</ignoreDiagnostics>
</executeActivity>
|
Executing post adapter
The post adapter converts Converts model output (cil0wes_30mv3_outinput.ascspw) in esri in spiderweb grid format to fews netcdf rotated pole grid format for T0. The name of the netcdf file will be the name configured for the netcdf import activity which is stored in the netcdf run file, for each time step a seperate netcdf file is created because each time step has a seperate grid definition.
The post adapter writes log messages to log file called Fast_Post_Adapterwes.log which can be read into FEWS by coupling line patterns to FEWS log messages.
Code Block |
---|
| xml |
---|
| xml |
---|
title | post adapter execute activity |
---|
|
<executeActivity>
<command>
<className>nl.deltares.wes.fastpost.FastPostAdapter<WesPostAdapter</className>
<binDir>adapter\bin</binDir>
</command>
<arguments>
<argument>run.nc</argument>
</arguments>
<logFile>
<file>Fast_Post_Adapter<file>wes.log</file>
<errorLinePattern>ERROR*</errorLinePattern>
<warningLinePattern>WARN*</warningLinePattern>
<infoLinePattern>INFO*</infoLinePattern>
<debugLinePattern>DEBUG*</debugLinePattern>
</logFile>
<timeOut>99999999</timeOut>
<ignoreDiagnostics>true</ignoreDiagnostics>
</executeActivity>
|
...
The last part of the general adapter run is importing the post adapter output. It uses <folder> and <fileNamePattern> in order to import the netcdf files for each time step.
Code Block |
---|
| xml |
---|
| xml |
---|
title | model run output import activity |
---|
|
<importActivities>
<importNetcdfActivity>
<importFile>postAdapterOutput<folder>workdir</folder>
<fileNamePatternFilter>wes_grid_*.nc</importFile>fileNamePatternFilter>
<timeSeriesSets>
<timeSeriesSet>
<moduleInstanceId>Run_WES_XBeach<Import</moduleInstanceId>
<valueType>grid</valueType>
<parameterId>H_max<<parameterId>Wind.speed</parameterId>
<locationId>Fast<<locationId>WilmaTest21</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="hour" multiplier="nonequidistant1"/>
<readWriteMode>read complete forecast</readWriteMode>
</timeSeriesSet>
</timeSeriesSets>
</importNetcdfActivity>
</importActivities>
|