| scrollbar |
|---|
What | Required | Description | schema location |
|---|---|---|---|
coldModuleInstanceStateGroups.xml | no |
definition of threshold values for all locations and data types
Definition of groups of cold module states | https:// |
| fewsdocs. |
| deltares.nl/schemas/version1.0/coldModuleInstanceStateGroups.xsd |
Many forecasting models use an initial state as initial condition. When used in real time, DELFT-FEWS can be used to manage these states, such that models are run from a warm state. Long Waiting on long run times in initiating models is thus avoided.
...
A default initial condition must be available for models requiring state management. Additional groups of cold module states may also be defined. These can be selected in for example scenario runs. While a default state is required for every model, additional states need only be defined where available. When the state indicated is not found for a particular situation, DELFT-FEWS will revert to the default state. Where it is found, it will be used as selected.
...
Figure 43 Elements of the ColdModuleInstanceStateGroups configuration
defaultGroup
Definition of the default group of module states. This is a required item, and only a single definition is allowdallowed.
Attributes;
- id: Id of the state group (e.g. Default)
- name: name of the state group.
additionalGroup
Definition of the additional group of module states. One or more items may exist.
...
- id: id of the state group (e.g. Wet)
- name: name of the state group.
description
Optional description of the state group. Used for reference purposes only.
| Info |
|---|
The name of the ZIP file containing the state follows a strict convention. This name is constructed using the moduleId of the module using this cold state and writing the warm state, appended by the Id of the state group. e.g ISIS_Eden_Historical default.zip |