...
Figure : Root elements of the ModuleInstanceDescriptors configuration
ModuleInstanceDescriptors
ModuleInstanceDescriptors contains two elements,
...
Each of these two elements can be repeated and can be in any order.
ModuleInstanceDescriptor
...
simulatedHistoricalModuleInstanceId
When given the relation is made between the module and (simulated historical) Module Instance given here.
The simulated historical update run, current at the moment the forecast is created, will be used for data before the start of the forecast.
When different parameters are used for the forecast and historical period it is also required to specify the historical parameter for the forecast parameter
When configured this module instance can only be used for simulated forecast time series.
ModuleInstancegroup
...
Attributes;
- Id: Id of the Module Instance group. This Id must be unique. Normally a string is used that gives some understanding of the role of the module (e.g. SpatialInterpolationPrecipitation).
- name: Optional name for the module group. Used for reference purposes only.
moduleinstanceDescriptor
One of the element is the ModuleInstanceDescriptors, as defined earlier. All instances of Modules defined here need not be defined again as individual moduleInstance. Each group can have multiple modules instances.
However following points to be taken into considerations when defining moduleInstances under a single group.
If one module instance in a group has a reference to a simulated historical, all module instances in the group should have a reference to a simulated historical module.
All referenced simulated historicals from one group should also belong to the same group
- The ModuleInstancegroup for Historical and Forecast should match . i.e. each moduleinstance defined in historical moduleinstancegroup should match on one-to-one basis with the forecast modulesinstancegroup. For example: