...
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 historical moduleinstances should also belong to the same group.
- The ModuleInstancegroup for Historical and Forecast should match i.e. each module instance defined in historical (updatestates) module instance group should match on one-to-one basis with the forecast modules instance group. This means that no modulesintances such as export, import should be added to module instance group.
A correct configuration example is shown as below. The total number of modulesinstances in update (historical) and forcast matches. Also the referenced simulated historical modules instances in LMBM5_Forecast modules instance group also belongs to a one same module instance group i.e. LBNM5_UpdateStates".
- An incorrect configuration example is shown as below. Here the Forecast modulesinstancegroup contains 10 moduleInstancegroup while (historical) update moduleinstancegroup contains 9. It is strongly recommended to avoid this.
- Module Instance group is used to mainly to optimize the way the data is written to the database. This lead leads to compact databases. Otherwise Modules Instance groups cannot be referred to retrieve data from database.
...