...
The technical implementations for both modes of working are quite different. For running HEC-RAS in operational forecasting mode from FEWS, a software interface will be required that directly controls the model runs.
Calibration is considered as an activity that should be carried out offline from the forecasting system. This means that no direct control from FEWS will be required but a user will need to be able to migrate model datasets (calibrated schematizations) from the HEC-RAS calibration environment to the forecasting environment.
Present documentation will describe the first mode of operation. For details about operating model in the calibration mode please check standard HEC-RAS documentation.
Operating Forecasting Model
Figure 1 Components used to run forecasts using HEC-RAS model in the FEWS/CHPS system
Operating HEC-RAS Model and FEWS Adapter
...
The FEWS Adapter for HEC-RAS forms the interface between the FEWS Forecasting Shell and the HEC-RAS model. The adapter accepts the request from the Forecasting Shell to run HEC-RAS, and imports the required data provided by the Forecasting Shell.
This data shall be provided in a standardized XML interface format, the FEWS Published Interface. Once a HEC-RAS run has been completed, relevant results are passed back to the Forecasting Shell in the form of the standardized XML interface format.
A schematic representation of the communication between the Forecasting Shell and the HEC-RAS model via the FEWS Adapter is shown in the diagram below.
Figure 2 Data flows involved during run of HEC-RAS model FEWS adapter
The FEWS Adapter allows running of HEC-RAS by FEWS. The FEWS Adapter should be considered as a thin communication (software) layer on top the existing HEC-RAS engine. The adapter is tightly connected to the model engine. For longer term consistency, a FEWS adapter should therefore preferably be maintained by the owner of the model code, in this case HEC. The FEWS Adapter for HEC-RAS shall be developed by HEC or handed over to HEC upon completion.
Several design options for the FEWS Adapter will be discussed in this section. Red box in the diagram below outlines the components within the adapter itself. The technical options will be discussed in the next section.
The features of the are listed in the tables below.
Preprocessing 01 | Clean up work and output folder |
Preprocessing 02 | Create module diagnostics file in Published Interface (PI) format |
Preprocessing 03 | Read the time series from PI time series |
Preprocessing 04 | Convert input PI time series into RAS DSS files |
Launcher 01 | Run HEC-RAS with run period and model alternative |
Postprocessing 01 | Open/create module diagnostics file in PI format |
Postprocessing 02 | Read a selection (output-dss-paths.txt) of output time series in the output RAS DSS file |
Postprocessing 03 | Write the time series to the output.xml |
Postprocessing 04 | Write the updated PI state file to export folder |
...
The data directories and configuration files that are required for operating the FEWS Adapter for HEC-RAS have been shown in the diagram below. The information
Note that only binary and configuration files relevant to the HEC-RAS for a normal run requires 
model directory, (ii) alternative to run, (iii) starting time of simulation, (iv) end time of simulation, (v) look back time, (vi) boundary conditions, and (vii) carryover date (model state) that should be used.
The information that HEC-RAS will feed back to FEWS will generally include model output, (ii) diagnostics, and (iii) saved carryover date (model state) in case of a carryover run.
Communication will strictly follow the FEWS Published Interface format.
Below the list of HEC-RAS mode data files is presented which need to be read or written by the HEC-RAS adapter.adapter are included, in a real configuration a lot more files can be involved used by another modules of the FEWS system.
| No Format |
|---|
+---bin
| hec.jar
| heclib.jar
| heclib60.dll
| javaHeclib.dll
| libjavaHeclib.so
| module-adapter-hec-ras.jar......................... pre- and pos- adapter, Coverts HEC-RAS data files to/from FEWS-PI format
| nwsras.jar......................................... main library used by the adapter, reads and writes HEC-RAS data files
|
\---region1
+---ColdStates
| hecras_connecticut_Historical Default.zip...... cold state files
|
+---Config
| +---IdMapFiles
| | IdExportHECRAS.xml......................... custom mappings for the HEC-RAS variables and locations
| |
| \---ModuleConfigFiles
| hecras_Connecticut_Forecast.xml............ main configuration file of the adapter
|
\---Modules
\---hec-ras
+---bin........................................ directory which contains all HEC-RAS executables for Windows and Linux platforms
| DSSWriter.exe.......................... generates binary file containing detailed model output
| dss_writer
| GeomPreprocessor.exe................... converts geometry files from GUI ASCII format to binary
| geo_pre
| Steady.exe............................. performs steady flow simulations
| steady
| Unsteady.exe........................... performs unsteady flow simulations
| unsteady
|
\---connecticut
+---input.................................. input directory of the adapter, input FEWS-PI time series files
| inputs.xml
|
+---log.................................... log messages written by the pre- and post- adapters
| postadapter.xml
| preadapter.xml
|
+---output................................. contains HEC-RAS output converted from the binary and dss output files
| binary-output.xml
| output.xml
|
\---work................................... working directory of the adapters
clean.cmd.......................... Windows and Linux scripts used to clean temporary files
clean.sh
run.cmd............................ Windows and Linux scripts used to execute the HEC-RAS model
run.sh
ctfld2ras.b01
ctfld2ras.b02
ctfld2ras.b03
ctfld2ras.c02
ctfld2ras.f04
ctfld2ras.g02
ctfld2ras.p01
ctfld2ras.p02
ctfld2ras.p05
ctfld2ras.prj
ctfld2ras.r01
ctfld2ras.r02
ctfld2ras.r03
ctfld2ras.r05
ctfld2ras.u01
ctfld2ras.u02
ctfld2ras.x02
|
Communication between FEWS system and pre-/post- adapter strictly follows the FEWS Published Interface format.
Pre-Adapter
...
Post-Adapter
...
Description of the HEC-RAS data files
Table 1 List of files to be read and written by adapter
Extension | Description |
| pre-adapter input | pre-adapter output | post-adapter input | post-adapter output |
|---|---|---|---|---|---|---|
.prj | project file | |
| |
| |
.p01 | plan files |
|
|
|
| |
.g01 | geometry files |
|
|
|
| |
.f01 | flow files |
|
|
|
| |
.u01 | unsteady flow files |
|
|
|
| |
.b01 | unsteady run files |
|
|
|
| |
.x01 | input file for geometry preprocessor |
|
|
|
| |
.r01 | steady run file |
|
|
|
| |
.o01 | binary output file |
|
|
|
| |
.bco | model log file |
|
|
|
| |
.c01 | output of geometry preprocessor |
|
|
|
| |
.dss | input / output files |
|
|
|
| |
.hyd01 | input file for geometry preprocessor |
Running model from FEWS
|
|
|
|
Running model from FEWS
Running model using command-line
The following software components play a role when running a model:
•heclib60.dll - library used to read and write HEC DSS files
•Steady.exe - steady flow model
•Unsteady.exe - unsteady flow model
•nwsras.jar - library allowing for reading and writing model input and output files.
•DSSWriter.exe - generates binary file containing detailed model output
•GeomPreprocessor.exe - converts geometry files from GUI ASCII format to binary
The following command line-based script will be used to run a HEC-RAS model:
echo Running Geometry preprocessor ...
%RAS_HOME%\GeomPreprocessor.exe Combined.x01 runnext=1
echo Running Unsteady.exe ...
%RAS_HOME%\Unsteady.exe Combined.c01 b03 runnext=1
echo Writing DSS ...
%RAS_HOME%\DSSWriter.exe Combined.c01 p03 runnext=1
Note that other command-line arguments will be defined to operate system under Linux.