What | nameofinstance.xml |
---|---|
Description | Configuration for the Secondary Validation module |
schema location |
SecondaryValidation
...
SecondaryValidation (since 2010_01)
The SecondaryValidation module can be used to perform certain checks on time series data and generate log messages when the specified criteria are met.
Children Display |
---|
General overview of this page
Table of Contents |
---|
Configuration
An XML file for configuring an instance of the SecondaryValidation module called for example CheckImportedData would be the following:
CheckImportedData 1.00 default.xml
CheckImportedData | File name for the CheckImportedData configuration. |
1.00 | Version number |
default | Flag to indicate the version is the default configuration (otherwise omitted). |
A SecondaryValidation configuration file is typically located in the ModuleConfigFiles folder and can be used to configure one or more checks. The configured checks will be processed one by one in the specified order. The checks can generate log messages, which can trigger actions in the master controller, like e.g. sending warning e-mails. A special type of check is available for automatically modifying flags to 'doubtful' or 'unreliable' per time step when a condition on multiple time series becomes true.
...
Warning | ||
---|---|---|
| ||
Since 2019.02 #92895 there have been fixes in the writing of output time series in the Secondary Validation module. These fixes improved consistency in writing behaviour making sure repeated runs will result in the same outcome. This, however, resulted in significant different outcome for some very specific use cases involving simulated time series. In case simulated time series were being validated as output time series in a workflow that did not create them, it results in the original data being hidden since the new write action creates a newer module run instance for the data. Changing simulated data in a different workflow than it was created should not have been allowed, but because of the previous inconsistencies in writing behaviour it was possible to use this data as output for the secondary validation module. In order to still support validation of simulated data in a different workflow than it was created, a "logs only" mode has been introduced. This mode can be considered as "read only" and will be described below. |
...