FlagPersistencyCheck
This check operates with the manual persistency marker that can be set by the user in the TimeSeriesDialog. This check will copy a persistent flag to the next timestep and will mark this next timestep as persistent. This is repeated until a different manual flag source is found.The purpose of the FlagPersistencyCheck is to automatically mark series unreliable, also for new imports. This is useful for when it is known from an import that the data is not correct, for instance when a remote sensor instrument is not functioning correctly.
...
Configuration example
| Code Block |
|---|
|
<secondaryValidation xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/secondaryValidation.xsd"
<!-- variableDefinitions can be global or nested -->
<variableDefinition>
<variableId>flagPersistencyInput1</variableId>
<timeSeriesSet>
<moduleInstanceId>FlagPersistencyCheckTest</moduleInstanceId>
<valueType>scalar</valueType>
<parameterId>H.obs</parameterId>
<locationId>location1</locationId>
<timeSeriesType>external historical</timeSeriesType>
<timeStep unit="hour" multiplier="1"/>
<readWriteMode>read complete forecast</readWriteMode>
</timeSeriesSet>
</variableDefinition>
<flagPersistencyCheck id="FlagPersistencyCheck">
<input><variableId>flagPersistencyInput1</variableId></input>
<logLevel>WARN</logLevel>
<logEventCode>SecondaryValidation.flagPersistency</logEventCode>
<logMessage>%AMOUNT_CHANGED_FLAGS% flags set to unreliable persistence for location=%LOCATION_NAME%</logMessage>
</flagPersistencyCheck>
</secondaryValidation>
|