...
DELFT-FEWS supports checking of time series against thresholds. When thresholds are crossed, appropriate messages may be issued. Thresholds are defined in two type of files: thresholds.xml (described here) and thresholdValueSets.xml (described described here). The first file contains definitions of threshold groups with thresholds and the types of threshold. There are three types of thresholds: level crossing thresholds, rate of rise and fall thresholds and max value thresholds. For a given threshold the options that are independent of location and parameter are defined. Additional threshold options for specific locations and parameters are defined in the thresholdValueSets configuration file. It is possible to configure one or more threshold groups. It is possible to configure threshold groups through several files. Note that the general configuration options should be either defined only once, or defined exactly in the same way in each file.
Contents
| Table of Contents | ||
|---|---|---|
|
...
Once a threshold crossing check has been triggered the threshold event is logged . The in the database. Depending on issue status and event coupling, a message will appear in the log panel at a certain log level. The logging process works as follows:
...
At the end of this action we have a list of all currently active Action Events. Threshold crossings for which no Action Event is configured in a 'LocationThresholds.csv' will not appear at WARN level in the log panel.
5) Go over the list of currently active Action Events and check if they have exceeded their max action duration time. This is the maximum time that an action event can be active. This value is configured in the Thresholds file with element 'maxActionEventDuration'. Default value is 1 Day. If an up action has expired then a corresponding down Action Event needs to be created and added to the issue list. Action Events of none approved forecast timeseries are skipped.
...