Cold module instance state groups file
This page is the generated field list for ModuleInstanceStateGroups.xml —
named cold-state options a forecaster can pick from in the state-selection
dialog when a module instance has no
usable warm state (first run, gap after downtime, or a deliberate reset).
At a glance
Section titled “At a glance”Purpose
: Declares one defaultGroup (always available), any number of
additionalGroups, and — since 2017.02 — seasonalGroups that are only
offered within a configured month/day window (e.g. a snowmelt-season cold
state).
Folder
: Config/RegionConfigFiles/
Root element
: <coldModuleInstanceStateGroups> (version="1.0", required)
Concept : See The forecasting lifecycle for cold vs. warm state in general.
Minimal example
Section titled “Minimal example”<?xml version="1.0" encoding="UTF-8"?><coldModuleInstanceStateGroups xmlns="http://www.wldelft.nl/fews" version="1.0"> <defaultGroup id="Default" name="Default cold state"> <description>Standard cold start with no prior state</description> </defaultGroup> <seasonalGroup id="SnowmeltStart" name="Snowmelt season start"> <description>Cold state tuned for the start of the snowmelt season</description> <season> <startMonthDay>--03-01</startMonthDay> <endMonthDay>--04-15</endMonthDay> </season> </seasonalGroup></coldModuleInstanceStateGroups>Field reference
Section titled “Field reference”Auto-generated from coldModuleInstanceStateGroups.xsd. Descriptions are the schema's own annotations.
Element <coldModuleInstanceStateGroups>
Attributes
| Attribute | Use | Notes |
|---|---|---|
version | required | fixed: 1.0. |
Elements
| Element | Type | Cardinality | Description |
|---|---|---|---|
defaultGroup | ColdModuleInstanceStateGroupComplexType | required | |
seasonalGroup | SeasonalColdModuleInstanceStateGroupComplexType | optional · repeats | |
additionalGroup | ColdModuleInstanceStateGroupComplexType | optional · repeats |
ColdModuleInstanceStateGroupComplexType
Attributes
| Attribute | Use | Notes |
|---|---|---|
id | required | |
name | optional |
Elements
| Element | Type | Cardinality | Description |
|---|---|---|---|
description | string | optional |
SeasonalColdModuleInstanceStateGroupComplexType
Attributes
| Attribute | Use | Notes |
|---|---|---|
id | required | |
name | optional |
Elements
| Element | Type | Cardinality | Description |
|---|---|---|---|
description | string | optional | |
season | SeasonConditionComplexType | required | Since 2017.02 Season this cold state is valid for |
SeasonConditionComplexType
| Element | Type | Cardinality | Description |
|---|---|---|---|
startMonthDay | monthDayType | required | Start month and day of this season. |
endMonthDay | monthDayType | required | End month and day of this season. |
Gotchas
Section titled “Gotchas”startMonthDay/endMonthDayuse XML’sgMonthDayform:--MM-DD(note the leading--), not a plainMM-DDstring.defaultGroupis required and singular — it’s the fallback whenever no seasonal group matches the run’s time zero.additionalGroupandseasonalGroupare both optional and repeatable on top of it.- A
seasonalGroup’s window (startMonthDay/endMonthDay) is evaluated against run time zero, not the state’s own timestamp — configure the window around when you want the option offered, not when the underlying state data is representative of.
See also
Section titled “See also”- Concept: The forecasting lifecycle
- Reference: Module instance descriptors file
- Schema:
coldModuleInstanceStateGroups.xsd