You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Issues related to the development of the Kisters Hydstra adapter (Deltares internal access only):

https://issuetracker.deltares.nl/browse/FEWS-16402

https://issuetracker.deltares.nl/browse/FEWS-20429

Contents

Introduction

The HYDSTRA modelling suite provides a flexible modelling framework for running operational hydrological forecasting models. Originally developed in Australia, the modelling suite has since been acquired and integrated into the WISKI system by Kisters AG (http://kisters.com.au/hydstra-modules.html). Due to support of the modelling suite being discontinued as a part of WISKI, the modelling suite can also be run from as a stand alone executable. The adapter that is described here is used to run the stand alone HYDSTRA modelling engine from the Delft FEWS system. This documentation focuses on the configuration and set-up of the adapter to provide the required inputs to run the model engine, to provide the required run parameters, and to read model results. 

Applications

The HYDSTRA modelling engine that this adapter describes is implemented in the following Delft FEWS configurations: 

  • Alberta River Forecasting System (ARFS), used by Alberta Environment and Parks (AEP), Edmonton, Canada (Deltares contacts: Dave Casson & Micha Werner). Note that AEP owns the IPR of the HYDSTRA Model engine code.

Download

Download of the model adapter is not available here: please e-mail to Delft-FEWS Product Management for more information.

Interface between FEWS and Hydstra

The adapter described here provides the following tasks in running Hydstra model engine from FEWS. The Hydstra adapter is developed in Java and is configured to run from the Delft FEWS configuration through a suitably configured General Adapter run. The tasks supported by the adapter include:

  • Reading of the input time series required for the Hydstra model run (e.g. precipitation, temperatur, discharge) as provided through from the general adapter through the FEWS Published Interface XML format (PI-XML), and transforming these to the input format required by the Hydsra model engine (Hysdstra Time Series Format, TSF).
  • Amending the Hydstra model definition file (TSO file) with the appropriate run-time parameters (e.g. model start time, run length etc). These data are provided from the FEWS General Adapter through the PI-XML formatted run file.
  • Amending the value of model parameters and states within the TSO file to allow influencing the behaviour of the Hydstra model. These parameters can be set either using the PI-XML parameters file exported from the FEWS General adapter (typically used for setting the value of model parameters, or through an PI-XML time series (typically used for setting the value of a model state at the start of the run).
  • Reading the output time series provided by the Hydstra model engine. These outputs are provided by the model engine using two formats; TSF formatted files and free format text files (format specified in the TSO file).


Hydstra model definition file

Each of the basin models that can be run through the Hydstra adapter is defined in the Hydstra Model Definition File (Model TSO file). This defines all model inputs and outputs, model structure and model parameters. While the Hydstra adapter does not interpret the full file, there are specific sections that are important. The model structure is made up of a series of nodes and links,, where each node is a modelling element of a defined type (this refers to a specific modelling algorithm such as the Synthetic Streamflow and Reservoir Routing - SSARR, or Unit Hydrograph - UH, algorithms). Links are important in this context to identify the inputs to the model as external time series are connected to the algorithms defined in the nodes though these links.

When setting up the Hydstra model to run from FEWS, it is important to identify all expected input time series. These are identified through the key word Source=TimeSeries. An example is provided below:

Source=TimeSeries(59.233,28.893,Text(C:\fews_systems\FEWS-Alberta\FEWS_ARFS\FEWS_ARFS\Modules\hydstra\Work\05DB006_QR.tsf),Agg)








  • No labels

Disclaimer