...
loopTimeStep
When specified, all activities are run in a loop to ensure that a state is produced on every cardinal time step between the time of the exported state and T0. This has two advantages:
...
writeIntermediateState
When specified, an extra state is written at the end of the state search period. Note that the run is than split in two. E.g my state search period is -10 to -4 days, then there are two update runs, one from the time where a state was found to -4 and one from -4 to T0. A state is written at the end of both runs (T0 and T0 - 4days). You can additionally define a minimum run length. This is necessary for some run runs that need a minimum run length for e.g. PT updating. The run is then only split in two if both runs can be run over the minimum run length. If not, there is only one run and the state is written to the end of this run (T0), no intermediate state is written.
see example configuration below and this figure
<exportStateActivity>
<moduleInstanceId>HBV_AareBrugg_Hist</moduleInstanceId>
<stateExportDir>%ROOT_DIR%/FEWS/states</stateExportDir>
<stateConfigFile>%ROOT_DIR%/FEWS/states/states.xml</stateConfigFile>
<stateLocations type="file">
<stateLocation>
<readLocation>HBV_States.zip</readLocation>
<writeLocation>HBV_States.zip</writeLocation>
</stateLocation>
</stateLocations>
<stateSelection>
<warmState>
<stateSearchPeriod unit="hour" start="-240" end="-96"/>
</warmState>
</stateSelection>
<writeIntermediateState>true</writeIntermediateState>
<minimumRunLength unit="day" multiplier="4"/>
</exportStateActivity>
...