The Integrated Reservoir Model is a General Adapter module written in Java, developed by Deltares. The model class is part of the Delft-FEWS code base.
The Reservoir model is developed and designed as a relatively straightforward reservoir routing model, that simulates flow through a reservoir with a level-release table defined. Specifically, the model is able to precisely replicate the uncontrolled outlet reservoir behaviour of the legacy Deltares RTC-Tools 1 codebase, which is no longer developed and supported. Because the adapter model is based on Java, it can run on Windows/Linux systems.
The model is introduced in the 2021.01 BoM Delft-FEWS version. The model adapter will be part of the Delft-FEWS code base of Delft-FEWS versions 2023.01 and onwards with in-memory options, to be set in the General Adapter configuration.
The data directories and configuration files that are required for operating the FEWS Reservoir Model Adapter are shown below.
General Adapter configuration
The General Adapter defines forms the interface between the Delft-FEWS system and the Reservoir model.
The data is provided in a standardized XML interface format, the FEWS Published Interface. For more details about general structure of the General Adapter please check 05 General Adapter Module.
Configuring a pi-version 1.8 is required for the diagnostics of the model. The model will write diagnostics to the filename that is configured in the General Adapter (the model reads it from the outputDiagnosticFile field in the run_info file). The logging will be to the level that is configured in Delft-FEWS (typically debug/info/warn/error).
The location/parameters used in Delft-FEWS can be transformed to model variableId locations/parameters by ID-mapping. The configuration files for ID-mapping can be of a general form, as long as the reservoir model have been set up with identical variables for the inputs/outputs. The model will look for the required variables (as configured in the IRM model file) in the parameter field of the PI timeseries.
IdMapping is dependent on how the variables have been defined in the model. The Reservoir Model code will try to parse the configured model variables (like IIn, QOut, etc) from the parameterId of the PI timeseries, the locationId is not used. This means that the parameterId's of all the input timeseries need to be unique (and identical to the model variables). When writing the output timeseries, the locationId used in the import PI xml files will be used as the locationId in the output PI xml files.
The Reservoir model can work with a stateConfigFile, exported from Delft-FEWS. This file should follow the conventions and list the read/write locations. When defined, the model will write an output state timeseries file for the complete run period, for all model export variables.
The reservoir model requires at a minimum the following timeseries:
- level or storage state value (at model start time)
- inflow timeseries (complete run period)
- release timeseries (optional)
A run_info file is required input for the Reservoir model, so an exportRunFileActivity needs to be configured in the General Adapter. The Reservoir Model expects a model property in the run_info file, that specifies the name of the actual Reservoir model to be run.
A typical run_info.xml file will contain the following information:
The executeActivity runs the model. The model runs of the Delft-FEWS JRE, so the ReservoirModelAdapter binaries can be specified within the binDir element. The Reservoir Model class itself is called nl.deltares.fews.reservoirmodel.ReservoirModelAdapter. It is required to provide the path of the run_info file as an argument to the model.
The model results (typically consisting of level, storage, inflow and release timeseries) can be imported using the importActivities. The importFile name configured will be written to the run_info file and consequently be created by the Reservoir model. Note that specific idImport configuration is required.
The model definition for the reservoir can be configured in a model file that follows the Integrated Reservoir Model schema. The model options are described below.
For reference, an example Integrated Reservoir Model file is attached.
In the general section of the reservoir model, a missingValue element needs to be configured. It is important to match the missingValue as defined in the Delft-FEWS General Adapter configuration for the model run.
The reservoir element contains the following sections:
The general section of the reservoir element contains the follwing fields:
for the poolRoutingScheme element, one can choose the following options:
The Level Pool method is a well known method for reservoir routing. Level Pool routing is a procedure for calculating the outflow hydrograph form a reservoir with a horizontal water surface, given its inflow hydrograph and storage-release characteristics. The level pool routing method is sometimes also referred to as Storage routing, the Storage-Indication method, or the Modified Puls method. For this reservoir model, the method described in Applied Hydrology from V.T.Chow (1988) is used.
The reservoir routing procedure in the Level Pool method is as follows:
We define the value G is a function of Storage and Outflow, defined as G[S] = 2*S/Δt + O
- S represents the reservoir storage
- O represents the reservoir release
- Δt represents the time step
For each row in the the uncontrolledOutlet capacityCharacteristics outletTable, we can now precompute a G[S] value. This allows the model to look up the release O for a given G.
The level pool method makes use of the following relations, that follow from the water balance equations (details in the handbook):
K[t] = G[t-1] - 2*O[t-1]
G[t]= ( I[t-1] + I[t] )+K[t]
For the computation, we loop over all time intervals from t=0 to t=tend.
- If t=0
- Use the state values as provided in the input files. If either a level, or a storage are provided, look up the equivalent value.
- In case both level and storage are provided, use the lookup value to determine any inconsistencies. If found, the level is used as the basis and the storage at t=0 is recalculated
- no computation takes place at t=0
- If t=1 then
- K = 2*S/Δt - O (inital storage and release values are known)
- G is computed with G= ( I + I )+K
- Compute outlet O by linearly interpolating the precomputed table using O(S) and G(S).
- In case an outlet O_input timeseries is provided as part of the inputs, set O = O_input
- Compute storage S = S + Δt* ( I - O )
- If t>1 then
- K[t] = G[t-1] - 2*O[t-1]
- G[t] is computed with G[t]= ( I[t-1] + I[t] )+K[t]
- Compute outlet O[t] by linearly interpolating the precomputed table using O(S) and G(S).
- In case an outlet O_input[t] timeseries is provided as part of the inputs, set O[t] = O_input[t]
- Compute storage S[t] = S[t-1] + Δt* ( I[t] - O[t] )
A model that is configured to use the level-pool method will write the values for G and K for each timestep in the the diagnostics when run in debug mode.
The Backward Euler reservoir routing scheme is an implicit scheme that uses the backward difference approximation for the derivative. The equation for the backward Euler reservoir routing scheme can be written as follows:
S[t+1] = S[t] + Δt* ( I[t+1] - O[t+1,S[t]] )
- S[t+1] represents the reservoir storage at the next time step (n+1)
- S[t] represents the reservoir storage at the current time step (n).
- Δt represents the time step.
- I[t+1] is the inflow into the reservoir at the next time step (n+1).
- O[ t+1, S[t] ] is the reservoir release at the next time step (n+1), based on the storage-release relation using S[t] for the lookup input.
When the dynamicInterpolation element is set to true, the level/storage and level/outlet tables are inteprolated dynamically (every timestep), to the precise value, using the elevationInterpolationMethod. In this case, the elevationInterval element is ignored.
When the dynamicInterpolation element is set to false, the level/storage and level/outlet tables are precalculated (only once) using the elevationInterpolationMethod, to the specified elevationInterval.
Linear interpolation is the only available interpolation method
The elevationInterval is the elevation resolution at which the configured level/storage and level/outlet tables need to be recalculated to achieve a higher granularity. Note that the level output at each timestep is processed to that specific elevationInterval. When the model looks up a value from the table, the largest precalculated table elements smaller than the lookup value will be used (i.e. the model always rounds down). The consequence is that reservoir inflows/releases at a timestep that result in level/storage changes smaller than the interval/resolution will not be taken into account. The model does not perform any shadow accounting to keep track of these volumes. This means that the model will generally underestimate the flow when dynamicInterpolation element is set to false, and water balance will not be closed for that run type. For larger reservoirs (more volume per unit water disk) the elevationInterval needs to be set to higher resolutions to account for this.
The storageCharacteristic storageTable contains a storage-level lookup table that is strictly increasing. Note that this table should have the identical storage inputs as the capacityCharacteristics outletTable from the uncontrolledOutlet.
The uncontrolledOutlet element contains capacityCharacteristics outletTable which relates storage-release. Note that this table should have the identical storage inputs as the storageCharacteristic storageTable.
The <input><release> element can be set to the timeseries variable that can overwrite (take precedence) the lookup value for the outlet. This means that for a given timestep, if the outlet input timeseries (e.g. QIn) contains a value, this release is applied.
The <output><release> element determines where the resulting release timeseries is saved to.
input / output variables and files
In the input section, the model input variables will be configured. The model will look for the required variables in the parameter field of the PI timeseries (see idMapping). The Reservoir Model code will try to parse the configured model variables (like IIn, QOut, etc) from the parameterId of the PI timeseries, the locationId is not used. In the output section, the model output variables will be configured. When writing the output timeseries, the locationId used in the import PI xml files will be used as the locationId in the output PI xml files. The output model variableId's will be used as the parameter in the timeseries.
The naming convention of the input and output timeseries filenames are free, the model will determine which files to read for the input based on the inputTimeSeriesFile filed in the run_info file. The following two input timeseries files are suggested:
- level values, or (HIn)
- storage values (SIn)
- inflow (IIn)
- outlet (optional) (QIn)
Note that for the suggested variableId's in the provided example, the postfix In and Out are used to denote if the series are Inputs for, or Outputs from the model.
The startDateTime and endDateTime in the run_info file are used by the model to determine the start (startDateTime) and end (endDateTime) of the model run. The model will pick the starting (state) value for level/storage (level has precedent in case of an inconsistency), inflow, outlet from the inputTimeSeriesFiles at the specific datetime. The model will first check for a state level value. If a starting level value is missing in the input, the model will use the starting storage value. If both starting level/storage cannot be determined from the input files, the model will use the first level element as defined in the storage table as the starting level. A Warning message will be generated to notify the operator of this situation.
Inflow and outlet values at the starting time are not required at the first timestep and these values will not be used for storage calculations (no calculation at the first timestep). When these values are not provided as inputs, a value of 0 is assumed (and written to the output).
When no inflows into the reservoir are defined at all, the model will not calculate, but also it will not error out. It will produce and export.xml with missings (except for the initial values). When some intermediate inflow values are missing, the model will stop calculating at the point. It will not error out (and not throw a warning), it will produces an export.xml with calculated values up until the point an inflow value was missing and it will have missings for all outputs from that moment in time.
The following output timeseries file is suggested:
- inflow (IOut)
- release (QOut)
- storage (SOut)
- level (HOut)
In case state functionality is configured in the run_info file (inputStateDescriptionFile is defined), the model will also write (all) the outputs to the write location as defined in the stateLocation file (e.g. exportState.xml)
Reservoir Model specifics
- The Integrated Reservoir Model can be considered "timestep ending", similar the the timestep definition of Delft-FEWS.
- No calculations/processing is performed at the first timestep (t=0, startDateTime as set in the run_info.xml file)
The Reservoir Model can be run in parallel from Delft-FEWS. The runInLoop element of the workflow should be set to false. The general section of the General Adapter configuration should contain the %TEMP_DIR% property as the model rootDir. And lastly, to enable the parallel running of ensemble members the runInLoopParallelProcessorCount entry must be set in the global properties file. Here you either specify the number of cores to use or specify 100 to use all available cores.
The workflow definition for a parallel model run:
The general section of the General Adapter configuration:
Entry in the global properties:
See the following page for more details.
From Delft-FEWS version 2023.01 onwards, it will be porssible to run the Reservoir Model adapter "in-memory" from Delft-FEWS, using the inMemoryFileTransfer element of the general section set to True. In that case, all exported and imported files are transferred in memory between Delft-FEWS and the executed Reservoir Model.