Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Contents

Table of Contents

Introduction

The conceptual solution for the interface between HEC-RAS and FEWS has been illustrated in Figure 1. Two modes of working are identified that each support a basic use case. The modes of working are:

...

Interface between FEWS and HEC-RAS

HEC-RAS model adapter follows standard way of integrating external models into the DELFT-FEWS system by use of General Adapter. For more details about configuration of General Adapter please check 05 General Adapter Module.

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.

...

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 location parameters used in FEWS can be coupled to HEC-RAS DSS path names through ID-mapping. The configuration files for ID-mapping should be created separately for each HEC-RAS model. Please consult 08 Mapping Id's flags and units for more information on how to configure id mapping in FEWS system.

Directory structure

The data directories and configuration files that are required for operating the FEWS Adapter for HEC-RAS have been shown below.

...

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
|       
\---region1connecticu
    +---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
            |       libmtsk.so.1
            |       
            \---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

...