...
| Code Block |
|---|
| xml |
|---|
| xml |
|---|
| title | Example of the FEWS-PI containing DSS output of the HEC-RAS model |
|---|
|
<TimeSeries
xsi:schemaLocation="http://www.wldelft.nl/fews/PI http://fews.wldelft.nl/schemas/version1.0/pi-schemas/pi_timeseries.xsd"
version="1.2" xmlns="http://www.wldelft.nl/fews/PI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<timeZone>0.0</timeZone>
<series>
<header>
<type>instantaneous</type>
<locationId>CT RIVER R1/0.00</locationId>
<parameterId>FLOW</parameterId>
<timeStep unit="second" multiplier="3600"/>
<startDate date="2008-11-06" time="00:00:00"/>
<endDate date="2008-11-08" time="00:00:00"/>
<missVal>NaN</missVal>
<units>CFS</units>
</header>
<event date="2008-11-06" time="00:00:00" value="24.38823" flag="0"/>
<event date="2008-11-06" time="01:00:00" value="-5.8442316" flag="0"/>
<event date="2008-11-06" time="02:00:00" value="68.705124" flag="0"/>
<event date="2008-11-06" time="03:00:00" value="391.09784" flag="0"/>
...
<event date="2008-11-07" time="23:00:00" value="438.6425" flag="0"/>
<event date="2008-11-08" time="00:00:00" value="-5259.6562" flag="0"/>
</series>
<series>
<header>
<type>instantaneous</type>
<locationId>CT RIVER R1/0.00</locationId>
<parameterId>STAGE</parameterId>
<timeStep unit="second" multiplier="3600"/>
<startDate date="2008-11-06" time="00:00:00"/>
<endDate date="2008-11-08" time="00:00:00"/>
<missVal>NaN</missVal>
<units>FEET</units>
</header>
<event date="2008-11-06" time="00:00:00" value="5.0" flag="0"/>
<event date="2008-11-06" time="01:00:00" value="5.0" flag="0"/>
<event date="2008-11-06" time="02:00:00" value="5.0" flag="0"/>
<event date="2008-11-06" time="03:00:00" value="5.0" flag="0"/>
...
|
Beste Practise Considerations
The HEC-RAS adapter requires quite some synergy between FEWS, Java and the actual HEC-RAS software versions. While a FEWS General Adapter config that uses embedded Java adapters is technically preferred above a custom JRE, it very sensitive to any software update. From past implementations we experience that using old models that run with older RAS versions, do not run anymore with actual adapter and Java versions. Therefore from an organizational and robustness perspective, it is preferred to have your both softwares as independent as possible, so with a custom JRE.
So instead of using the below default config:
| Code Block |
|---|
| language | xml |
|---|
| title | Embedded GA execute activity, running with FEWS 2016.02 and HEC-RAS v5 |
|---|
|
<executeActivity>
<command>
<className>nl.wldelft.fews.adapter.hec.HecRasAdapter</className>
<binDir>$HECRASBINDIR$</binDir>
</command>
<arguments>
<argument>%ROOT_DIR%/run_info.xml</argument>
</arguments>
<timeOut>3600000</timeOut>
</executeActivity>
|
one can better use a config like:
| Code Block |
|---|
| language | xml |
|---|
| title | Independent GA execute activity running with FEWS 2023.02 and HEC-RAS v5 |
|---|
|
<executeActivity>
<command>
<className>nl.wldelft.fews.adapter.hec.HecRasAdapter</className>
<binDir>$HECRASBINDIR$</binDir>
<!-- use old Java 8, while 2023.02 uses 11-->
<customJreDir>$CUSTOMJRE_64B_DIR$</customJreDir>
<!-- in case of custom JRE, pass correct default Parser definition-->
<jvmArg>-Dorg.xml.sax.parser=com.sun.org.apache.xerces.internal.parsers.SAXParser</jvmArg>
</command>
<arguments>
<argument>%ROOT_DIR%/run_info.xml</argument>
</arguments>
<console>
<!-- dump console in txt file, so in case of a crash, you see what happend-->
<redirectToLogFile>%ROOT_DIR%/log/adapter_console_logging.txt</redirectToLogFile>
</console>
<timeOut>3600000</timeOut>
</executeActivity>
|
Running model from FEWS
Check Using Delft-FEWS - User Guide on how to run configured model from the Delft-FEWS system.