You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Contents of check for SpatialHomogeneityCheck

The purpose of this check is to test for trends in the input timeseries and send log messages whenever a trend is detected. One of the strengths of the Mann-Kendall check is that it also be used when there are lots of missing values. Unfortunately there is a limit on the number of non-missings that can be processed reasonably, since the calculation of the slopes requires memory for n * (n + 1) / 2 values. It is therefore recommended to aggregate the values first.

During the check, the threshold criteria for the check are first sorted. The most severe log message is processed first and when the log message is generated the less serious log message will not be generated.

Configuration
  • id: identifier of the check.
  • checkRelativePeriod: The period to run the trend test for.
  • variableDefinition: embedded variable definition (see above).

For each threshold,

  • testTrend: either two-tailed, upward or downward
  • confidenceCoefficient: 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%.
  • logLevel: Log level for the log message that is logged if a trend is detected. Can be DEBUG, INFO, WARN, ERROR or FATAL. If level is error or fatal, then the module will stop running after logging the first log message. Fatal should never be used actually.
  • logEventCode: Event code for the log message that is logged if a trend is detected. 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.
  • logMessage: Log message that is logged if a trend is detected.

Tag

Replacement

%CHECK_ID%

The id of the check that caused the flags to be altered.

%HEADER%

The header names of the timeseries for which the flags were altered.

%LOCATION_ID%

The locationId where the alterations took place.

%LOCATION_NAME%

The name of the locations where the alterations took place.

%PARAMETER_ID%

The parameterId where the alterations took place.

%PARAMETER_NAME%

The name of the parameter where the alterations took place.

Configuration examples for MannKendallCheck

A configuration example for the MannKendallCheck is given below:

<secondaryValidation xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews 
file:///G:/fews/workspace/fews/xml-schemas/secondaryValidation.xsd">

	<mannKendallCheck id="MannKendallCheck1">
		<variable>
			<timeSeriesSet>
				<moduleInstanceId>MannKendallCheckTest</moduleInstanceId>
				<valueType>scalar</valueType>
				<parameterId>H.meting</parameterId>
				<locationId>Nue_0015_01_01</locationId>
				<timeSeriesType>simulated forecasting</timeSeriesType>
				<timeStep unit="minute" multiplier="1"/>
				<readWriteMode>read only</readWriteMode>
			</timeSeriesSet>
		</variable>
		<!-- test storage is set to 2009-1-1, data starts at 11-Dec-2011 -->
		<checkRelativePeriod unit="minute" start="1705491" end="1705501"/>
		<threshold>
			<testTrend>two-tailed</testTrend>
			<confidenceCoefficient>0.01</confidenceCoefficient>
			<logLevel>WARN</logLevel>
			<logEventCode>SecondaryValidation.MannKendallCheck</logEventCode>
			<logMessage>trend detected in %HEADER% by %CHECK_ID%.</logMessage>
		</threshold>
	</mannKendallCheck>

</secondaryValidation>
  • No labels

Disclaimer