Page History

...

• poolRoutingScheme
• dynamicInterpolation
• elevationInterpolationMethod
• elevationInterval
• storageCharacteristics

poolRoutingScheme

for the poolRoutingScheme element, one can choose the following options:

...

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.n  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:

...

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.In the workflow

The workflow definition for a parallel model run:

    <activity>
        <runIndependent>true</runIndependent>
        <workflowId>Reservoir_Forecast</workflowId>
        <ensemble>
            <ensembleId>ENSEMBLE</ensembleId>
            <runInLoop>false</runInLoop>
        </ensemble>
    </activity>

The general section of the General Adapter configuration:

<general>
  <rootDir>%TEMP_DIR%</rootDir>
  <workDir>%ROOT_DIR%/work</workDir>
  ...
</general>

In Entry in the global properties:

# to use 4 cores/cpu's:
runInLoopParallelProcessorCount=4

...

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.