...
If time zero changes the cold state selection should also change to keep the relative period the same.
Forecast length
To set the forecast length at a fixed length the option forecastLength can be used.
It is possible to force the end time of the forecast (time zero plus forecast length) to match a certain time step by using the option initialForecastLengthCardinalTimeStep.
The end time of a node is only forced to the match this time step at the moment the user selects the node for the first time.
To force the end time of a node to match a certain time step in the cases the forecaster tries the edit the default forecast length the option cardinalTimeStepForecastLength can be used.
By default the end time of a node changes when the system time changes so that the forecast length stays the same.
However if for a node the option initialForecastLengthCardinalTimeStep is configured then the end time of the node stays the same if time zero changes.
Below a configuration example of a node for which a forecast length, an initialForecastLengthCardinalTimeStep and a cardinalTimeStepForecastLength is configured.
| Code Block |
|---|
<node id="B10_Main_RTC" name="Run model">
<workflowId>Big10_RTCTools_RT</workflowId>
<forecastLength unit="hour" multiplier="24"/>
<cardinalTimeStepForecastLength unit="hour"/>
<initialForecastLengthCardinalTimeStep id="HE6"/>
<displayGroupId>Main_RT-RTC</displayGroupId>
<timeSeriesButtonsPanelId>RT_buttons_Main</timeSeriesButtonsPanelId>
<viewPermission>execute</viewPermission>
<visibleModifierGroup>RT</visibleModifierGroup>
<graceTime unit="hour" multiplier="1"/>
<localRun>true</localRun>
<saveLocalRunEnabled>true</saveLocalRunEnabled>
<showRunApprovedForecastButton>true</showRunApprovedForecastButton>
</node> |
Below a screenshot of this node after it is selected for the first time.
The end time of the run (forecast length) was first set to time zero plus 24 hours. Because this time wasn't a valid time for the configured
initialForecastLengthCardinalTimeStep the end time was set to first valid time prior to the end time.
Below a screenshot of the same node after the sytem time was changed. The time zero is changed but the end time of the node is still fixed at the same time.
Overview of all the configuration options
...