The Delft3D-FEWS model adapter is intended to work which each of the Delft3D modules listed in the General section. Since these modules can differ significantly in:

  • Model input file format
  • Model output file format
  • Relationships between different Delft3D modules

A number of high-level design choices have been made during development of this model adapter. These choices were made to:

  • Provide consistency between the adapters for the different Delft3D packages
  • Make the adapter fully compliant with "the FEWS standard"
  • Keep the effort required for adapter configuration to a minimum
  • Keep the adapter largely unaware of the different types of native model input file format, thus making it less prone to errors due to changes in these formats.

For the Delft3D-FEWS model adapter user, these choices amount to the following practical issues, which should be taken into account during adapter configuration:

  1. The adapter assumes that a fully calibrated and setup model is provided for configuration in the FEWS system. Additional changes to the model schematisation may require additional changes in the configuration of the model adapter (though not necessarily).

  2. The adapter works using templates for native model input files. In each of these template files, keywords serve as placeholders for dynamic time series data to be obtained from FEWS. The model adapter subsequently replaces these placeholder keywords with the appropriate data, exported from FEWS in PI XML format from the generalAdapter module. The template files have to be prepared during configuration of the model adapter, following pre-defined naming convention described in this manual. By using this approach, the adapter is (almost) independent of the structure of the Delft3D input files. Also, this approach is adequate for all Delft3D modules.

  3. The model adapter is subdivided over three sub-modules. These sub-modules can also be run independently of one another, which is relevant for specific Delft3D applications, line coupled Delft3D-Sobek models, or coupled FLOW-WAQ simulations. The sub-modules are:
    • The pre-adapter, which prepares the native model input data based on data exported to PI XML by FEWS from the generalAdapter.
    • The adapter, which executes the model simulation.
    • The post-adapter, which converts selected model output to the appropriate PI XML data types to be imported by FEWS.

  4. The adapter and template files allow for combining dynamic data provided by FEWS with static data included in the template files. This is relevant in case, for example, a significant number of constant discharges are included in a FLOW or WAQ model (can be up to 50+). In that case, these constant discharges do not have to included in (governed from) the FEWS configuration.

  5. The adapter assumes that dynamic data is provided by FEWS at all times. Error checking of this data should be done in FEWS primarily (based on available FEWS functionalities). If inappropriate data is provided by FEWS, the error checking done by the model adapter is limited. Instead, the adapter will log and display error messages as provided by the model in such a situation.

  6. The adapter applies a specific configuration file, used to define some adapter specific settings. The contents of this file is described in this manual.

  7. Delft3D-FEWS was originally setup to work with 1D and 2D models (river system and catchments modelling). The Published Interface (PI) XML file format, used for data transfer between FEWS and model systems, was setup to accomodate this. This implies that the PI XML format supportes both 1D and 2D data types. For 3D data, however, no specific PI XML data type is available. This implies that in FEWS, a 3D dataset should be seen as a stack of 2D or 1D grids and timeseries. The user should take this into account during configuration by, for example, assigning each layer of a 3D grid with a unique parameter/location combination in FEWS.
  • No labels