The secondary validation module also takes into account the time dependency of the locations.
<seriesComparisonCheck id="timeDependentSeriesComparisonCheck"> <expression>output - A1 >@A@</expression> <validatingVariableId>output</validatingVariableId> <outputFlag>unreliable</outputFlag> <logLevel>DEBUG</logLevel> <logEventCode>SecondaryValidation.locationSeriesComparisonCheckUnreliable</logEventCode> <logMessage>%AMOUNT_CHANGED_FLAGS% flags set to %OUTPUT_FLAG% by [%CHECK_ID%, %EXPRESSION%].</logMessage> </seriesComparisonCheck>
However it is important to explain how the time dependency of locations influences the resolving of the location attributes.
In the example above the expression contains one location attribute A. But which location should be used to resolve this location? Both variable output and variable A1 provide a location which could be used
to resolve the attribute. In addition it is possible to have several validating variables. In that case the expression is being used to validate several variables.
The secondary validation always uses the location of the time series for which it is validating. In the case that there are more than 1 validating variables the validation is done for each validation variable seperatly.
Because there will always be only one validating variable it is always determined which location should be used to resolve the location attributes used in the expression. The value of the variable can be time depedent.