Since 2024.01. Definition of a time series to be used for storing logged messages. Log level for the log message that is logged by the check. If level is error or fatal, then the module will stop running after logging the first log message. Event code for the log message that is generated by this check. This event code has to contain a dot, e.g. "TimeSeries.Check", because the log message is only visible to the master controller if the event code contains a dot. Log message that is logged by the check. It is possible to use the following tags: %HEADER% and %LOCATION_NAME%. The %HEADER% tag will be replaced with the header of the time series. The %LOCATION_NAME% tag will be replaced with the name of the location of the time series. For minNumberOfValuesCheck, minNonMissingValuesCheck, minReliableOrDoubtfulValuesCheck and minReliableValuesCheck it is also possible to use additional tags between "@" signs, e.g. "@ID@", that refer to location attributes that are defined in the locationSets config file. The values of the location attributes can be different for different locations. The location attributes are evaluated first, then the other tags (between % signs) are evaluated. Checks that update the flags can use %AMOUNT_CHANGED_FLAGS% to display the number of flags that have been altered. The tag %CHECK_ID% puts in the id of the check that caused the flags to be altered. The SeriesComparisonCheck can use %EXPRESSION%, which is the expression that caused the flags to be altered. The tag %LOCATION_ID% displays the locationId where the alterations took place. The tag %OUTPUT_FLAG% contains the flag that has been set. The tag %PARAMETER_ID% contains the parameterId where the alterations took place. The tag %PARAMETER_NAME% contains the name of the parameter where the alterations took place. The tag %PERIOD% contains the period in which flags were changed. The tag %NONE% hides the autogenerated location and parameter in the log message. The SeriesComparisonCheck also may contain the tag %VALUE%, which will be replaced with the latest value for the validating timeseries. If true, the validation check will continue logging after the first error. NB. Be aware that lots of event-codes might be generated using this option and that these may trigger a lot of emails being sent automatically by the master-controller. Contains a list of checks on timeSeries. These checks are different from transformations in that they do not have impact on the data, merely on the reliability flags or the generation of log events. Also different from primary validation as the tests using LogEventGroup can be added to a workflow for monitoring missing data values over time, generating log-messages, whereas primary validation is only run when the data is imported. Definitions of variable that can be used as input for checks. Alternatively, variable definitions can be embedded in the checks. Checks whether there are enough values within a configured period. If not, then a log message with the configured event code and level is logged. The log event code can be used to trigger a certain action in the master controller, e.g. sending warning emails. In this context a value can be reliable, doubtful, unreliable or missing. This check is useful for non-equidistant time series where the number of values per period (including missing values) is not fixed. Checks whether there are enough non-missing values within a configured period. If not, then a log message with the configured event code and level is logged. The log event code can be used to trigger a certain action in the master controller, e.g. sending warning emails. A non-missing value is a value that is reliable, doubtful or unreliable. Checks whether there are enough values that are reliable or doubtful within a configured period. If not, then a log message with the configured event code and level is logged. The log event code can be used to trigger a certain action in the master controller, e.g. sending warning emails. Checks whether there are enough reliable values within a configured period. If not, then a log message with the configured event code and level is logged. The log event code can be used to trigger a certain action in the master controller, e.g. sending warning emails. Checks the specified expression for the available variables and alters the flags for the time steps where the expression succeeds. For instance, a check can compare the water flow before and after a river junction. It is required that all referenced variables in the expression have the same size. Either all variables are regular with the same timestep, or all variables are non-equidistant with the same times. The comparison can be for different parameters at one location or per location of a locationSet, or for one parameter at two locations or at one location and the locations of a location set, or between multiple equal location sets. Overwrites the flag of the output timeseries with one of the flags of the input variables according to the following rules: Input flag 'missing' or 'unreliable' turns output flag 'doubtful' and 'reliable' into unreliable. Input flag 'doubtful' turns output flag 'reliable' into 'doubtful'. The comparison can be for different parameters at one location or per location of a locationSet, or for one parameter at two locations or at one location and the locations of a location set, or between multiple equal location sets. Overwrites the flag of the timeseries with unreliable or doubtful when the estimation of the value based on neighbouring values differs too much from the observed value. The criteria for that can be specified to be a maximum threshold or relative (i.e. percentage of the standard deviation) or both. The estimation is based upon a maximum number of closest by other locations within a maximum search radius. Overwrites the flag of the timeseries with unreliable or doubtful when there are at least ten observations and the Mann-Kendall detects a trend but the value does not follow the trend for the specified confidence balance. This check uses tiedValues and sameYearValues for the calculation. 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. Identifier for this variable. Use this identifier to reference the time series set within the expression. A time series set that can be used as input or output for a check. Choose between a reference to a time series or an embedded definition of a time series. Identifier of a variable to use. Refers to a time series set defined at top level. A time series set that can be used as input for a check. One or more items that describe the data that need to be checked. If the specified data contains multiple time series (e.g. for multiple locations), then each time series is checked individually. The check will only consider data in this time period. This time period is relative to the timeZero of the task run in which this module instance runs. The start and end of the period are included. The minimum required number of values. Optional element to define the name of the class that should be executed to perform this secondary validation. Normally this element can be left out of the xml configuration, and the default class name will be used. This default class name is defined as the default value for this element in the xsd schema for this transformation. Only use this element if you need to use a custom class that is present in the program code. Identifier of this check. This is only used in log messages and exception messages. One or more items that describe the data that need to be checked. If the specified data contains multiple time series (e.g. for multiple locations), then each time series is checked individually. The check will only consider data in this time period. This time period is relative to the timeZero of the task run in which this module instance runs. The start and end of the period are included. The minimum required number of values. Optional element to define the name of the class that should be executed to perform this secondary validation. Normally this element can be left out of the xml configuration, and the default class name will be used. This default class name is defined as the default value for this element in the xsd schema for this secondary validation. Only use this element if you need to use a custom class that is present in the program code. Identifier of this check. This is only used in log messages and exception messages. One or more items that describe the data that need to be checked. If the specified data contains multiple time series (e.g. for multiple locations), then each time series is checked individually. The check will only consider data in this time period. This time period is relative to the timeZero of the task run in which this module instance runs. The start and end of the period are included. The minimum required number of values. Optional element to define the name of the class that should be executed to perform this secondary validation. Normally this element can be left out of the xml configuration, and the default class name will be used. This default class name is defined as the default value for this element in the xsd schema for this secondary validation. Only use this element if you need to use a custom class that is present in the program code. Identifier of this check. This is only used in log messages and exception messages. One or more items that describe the data that need to be checked. If the specified data contains multiple time series (e.g. for multiple locations), then each time series is checked individually. The check will only consider data in this time period. This time period is relative to the timeZero of the task run in which this module instance runs. The start and end of the period are included. The minimum required number of values. Optional element to define the name of the class that should be executed to perform this secondary validation. Normally this element can be left out of the xml configuration, and the default class name will be used. This default class name is defined as the default value for this element in the xsd schema for this secondary validation. Only use this element if you need to use a custom class that is present in the program code. Identifier of this check. This is only used in log messages and exception messages. Defines a series of variables and an expression. Variable definitions are first searched for locally, if the variable is not found here it has to be available at the global level. Definition of a variable to be used in the expression. Formula stating the constraint to test, must be a comparison. Comparators have to be in Fortran 77: .le. .eq. .ne. .gt. .ge. Logical expressions such as .and. or .or. and bracelets are allowed as well. For instance, (abs(a - b - c) .ge. abs(0.05*a) +abs(0.05*b) +abs(0.05*c)) .or. a .gt. 100 says that the difference between flow variables 'a' and the sum of variables 'b' and 'c' should be smaller than the sum of the instrument errors, eg. 5% and that variable 'a' should be smaller than 100. If the condition holds, the flag will be updated to the specified output flag. NB: Variable names should not overlap with mathematical constants or functions such as 'e' , 'pi' or 'sin'. Identifier of a variable for which the outputFlag has to be updated in case the expression tests positive. Refers to a time series set defined in the variableDefinitions. Flag that will be set for all data values for which the expression succeeds. When this option is set to 'logs_only', only log messages are generated, the flags will not be updated. Optional element to define the name of the class that should be executed to perform this secondary validation. Normally this element can be left out of the xml configuration, and the default class name will be used. This default class name is defined as the default value for this element in the xsd schema for this secondary validation. Only use this element if you need to use a custom class that is present in the program code. Identifier of this check. Defines a series of input and output variables. Definition of a variable to be used in the input and/or output variables. Identifier of a variable of which the flags will be used. Refers to a time series set defined in the variableDefinitions. Identifier of a variable for which the outputFlag has to be updated in case the input flag was more unreliable. Refers to a time series set defined in the variableDefinitions. By default the flags that need updating are updated and log events are generated for the updated flags. When this option is set to 'logs_only', the log events are generated but the flags will not be updated. Since 2014.02. Optional element to define the name of the class that should be executed to perform this secondary validation. Normally this element can be left out of the xml configuration, and the default class name will be used. This default class name is defined as the default value for this element in the xsd schema for this secondary validation. Only use this element if you need to use a custom class that is present in the program code. Identifier of this check. The output flag is applied when the difference between observed and estimated exceeds this value. The output flag is applied when the difference between observed and estimated is bigger than this factor times the standard deviation of the neighbouring values. Specify whether the threshold applies when the neighbors have higher and or lower values. Flag that will be set for all timesteps for which the check is to alter flags, unreliable or doubtful. By default the flags that need updating are updated and log events are generated for the updated flags. When this option is set to 'logs_only', the log events are generated but the flags will not be updated. Configurable flag source that will be set for all timesteps for which the check alters the flags. This will override the standard flag source for this check. Refers to the identifier in the CustomFlagSources schema in the RegionConfig. Since 2014.02. Optional element to define the name of the class that should be executed to perform this secondary validation. Normally this element can be left out of the xml configuration, and the default class name will be used. This default class name is defined as the default value for this element in the xsd schema for this secondary validation. Only use this element if you need to use a custom class that is present in the program code. Defines a series of input and output variables. variable of which timeseries the flags will be used as input (neighbouring locations). Specifies the search radius in meters for the support locations (in meters). Default = Infinity. Specifying the search radius increases the performance since it limits the candidate points to be evaluated. Otherwise all possible points are considered. The searchRadius criterion is applied before the normalization with xMultiplier, yMultiplier and zMultiplier. Geo Datum used to calculate the distances in meters between the points. When the input geometry is not in meters calculation of distances will be very slow and a search all is required when there is no exact match Number of points used in SpatialHomogeneityCheck. The maximum number of neighbouring locations to base the estimation on. The neighbouring locations are established once per check. Missings are ignored. Default is 8 points. since 2012.02. Extra stations that are further away and are used in case of one or more missings in the base points. For every missing support point another neighbouring non-missing backup point is used. since 2012.02. Determine whether to search per quadrant which may lead to a more balanced set of neighbouring stations. Number of points used in SpatialHomogeneityCheck. The maximum number of neighbouring locations to base the estimation on. The neighbouring locations are established once per check. Missings are ignored. since 2012.02. Extra stations that are further away and are used in case of one or more missings in the base points. For every missing support point another neighbouring non-missing backup point is used. Specifies whether all backup points are included in the stDev calculation, default is true. When false only the backup points that are used to replace the closest points are used in the standard deviation calculation Power of inverse distance, default is 2. since 2012.02. Factor applied to the x-component of the distance function. Default 1. since 2012.02. Factor applied to the y-component of the distance function. Default 1. since 2012.02. Factor applied to the z-component of the distance function. Default 0. Specifies the thresholds for the difference between observed and estimated. When exceeded, the worst of the applicable flags will be applied. Identifier of a variable for which timeseries the outputFlag has to be updated in case the thresholds are exceeded (observed values). Refers to a time series set defined in the variableDefinitions. Specify this for writing the spatially weighted mean of the neighbouring locations to the datastore, which is the estimation that is used in this check. Specify this for writing the weighted standard deviation of the neighbouring locations, which is used when using a relative threshold condition. Specify this for writing the relative difference that is used to reject the values Specify this for writing the absolute difference that is used to reject the values Since 2014.02. Optional element to define the name of the class that should be executed to perform this secondary validation. Normally this element can be left out of the xml configuration, and the default class name will be used. This default class name is defined as the default value for this element in the xsd schema for this secondary validation. Only use this element if you need to use a custom class that is present in the program code. Identifier of this check. Selects a two-tailed, upward or downward trend. The confidence coefficient, also known as alpha, which is typically between 0 and 0.5, i.e. 0.05 (one-tailed) and 0.025 (two-tailed) correspond to a confidence level of 95%. This is the classical MannKendall test that uses the inverse cumulative distance function (inverseCDF). Instead of using the classical MannKendall test using the inverseCDF, this option will alter the flags and generate the logs when the maximum absolute drift is exceeded. Drift is the length of the checkRelativePeriod times the slope. Flag that will be set for all data values for which the expression succeeds, unreliable or doubtful. By default the flags that need updating are updated and log events are generated for the updated flags. When this option is set to 'logs_only', the log events are generated but the flags will not be updated. Identifier of the timeseries the flags will be used as input (neighbouring locations). Refers to a time series set defined in the variableDefinitions. Includes Sen's slope in the logging (default true). Since for large number of steps and the algorithm is O(n^2) this can be switched of in order to speed up the calculation. In the latter case, not the median of the slopes but the average of the slopes is used for the estimation of the slope and drift. The check will only consider data in this time period. This time period is relative to the timeZero of the task run in which this module instance runs. The start and end of the period are included. Specifies one or more trend tests. If multiple thresholds are specified, the thresholds are ordered by log level and confidence level, Only the severest log message will be generated. Identifier of a variable for which timeseries the outputFlag has to be updated in case the thresholds are exceeded (observed values). Refers to a time series set defined in the variableDefinitions. Since 2014.02 Optional element to define the name of the class that should be executed to perform this secondary validation. Normally this element can be left out of the xml configuration, and the default class name will be used. This default class name is defined as the default value for this element in the xsd schema for this secondary validation. Only use this element if you need to use a custom class that is present in the program code. Identifier of this check. This is only used in log messages and exception messages. timeseries for which the flags should be persisted Since 2014.02 Optional element to define the name of the class that should be executed to perform this secondary validation. Normally this element can be left out of the xml configuration, and the default class name will be used. This default class name is defined as the default value for this element in the xsd schema for this secondary validation. Only use this element if you need to use a custom class that is present in the program code. Identifier of this check. This is only used in log messages and exception messages.