Traitement et analyse de séries chronologiques continues de ...

Traitement et analyse de séries chronologiques continues de ... Traitement et analyse de séries chronologiques continues de ...

theses.insa.lyon.fr
from theses.insa.lyon.fr More from this publisher
14.09.2014 Views

Annexes type and number of sensors (see Figure 1). The following paragraphs briefly describe the parametric tests with an indication of the required parameters. Test 1a checks if data have been recorded or not. No parameter is required for this test. Test 1b checks if data have been recorded during a maintenance operation by comparing their dates with dates of maintenance provided in a specific file entered by the operator in charge of the maintenance. Test 2 detects any data outside the sensor measurement range. Its two parameters are the minimum and maximum measurable values. Test 3 checks if recorded data are within the interval defined by two parameters corresponding to the 2.5 percentile and 97.5 percentile of previously validated values measured with a given sensor in a given location. The two parameters may change with time when more values are observed under various dry and wet weather conditions. Test 4 requires two parameters which compare measurement dates to the last maintenance date and classifies data as either correct, doubtful or even non valid if the duration elapsed since the last maintenance is too long. Test 5 detects sudden, abnormal or erratic increases or decreases of values by comparing the difference between instantaneous values (raw signal) and the mobile mean or median (filtered signal). The required parameters are the number of time steps for the mobile mean or median calculation and minimum and maximum threshold values. Test 6 compares the values and the signal dynamics of two redundant sensors in order to detect unusual trends or abnormal gaps. Test 7 is similar to Test 6 in its principle but compares values and the signal dynamics of any correlated variables (e.g. water level and flow velocity, upstream and downstream values, measured and simulated discharges, etc.). Test 8 qualifies data for a given sensor (the influenced sensor) depending on values delivered by another sensor. The test requires threshold values for the influencing sensors and classifies the data of the influenced sensor as either correct or doubtful. For example, in the case of water level and velocity sensors, if the water level is too low, velocity measurements are considered as doubtful. As for Test 3, influenced and influencing sensors and threshold values are based on previous validated data and may change with time and experience of the operator. Data pre-validation Pre-validation tests are applied to corrected data in order to assign validation marks. It should be noted that all tests are not applicable to all data series. Only Tests 1a to 5 can be applied to all sensors. Tests 2, 3 and 5 are sensor specific. Tests 6, 7 and 8 can only be applied if redundant or correlated information is available. For Tests 2, 3 and 5, specific threshold values can be specified for both dry and wet weather conditions. The distinction between the two conditions is defined by the operator and can be based on any sensor and corresponding threshold value or on any combination of values. The pre-validation procedure is shown in Figure 1. For each value, Tests 1a and 1b are run first. If the value is identified as not valid, its validation mark is set to 3 and the pre-validation procedure is

Annexes terminated. Else Test 2 is run. If the value is out of the sensor physical range, validation mark is set to 3 and the pre-validation procedure is terminated. If Test 2 is run successfully, then Tests 3 to 8 are performed when they are applicable for the times series which is processed. They are run independently one from another, i.e. the validation mark given by any Test 3 to 8 does not condition the run of the other ones. At the end of the pre-validation run, a global pre-validation mark is attributed to each sensor, and to each value at each time step. This global mark results from the concatenation of the elementary marks attributed by each test. If a test is not applied, the corresponding mark is 9. A pre-validated data file is created with the same format as the corrected data file, i.e. date and time, and, for each sensor, values, uncertainties and pre-validation marks. This allows the tracing of pre-validation information. Data validation The final validation is carried out manually by an operator and should end with only two validation marks: 1 for valid data or 3 for non valid data. A specific Matlab graphical user interface has been developed for both data visualisation and processing of pre-validated data. The aim is to carry out the final manual validation without requiring time consuming and manual changes of numerical values in the pre-validated data files which can be prone to errors. A four colour code is applied: (i) black for correct data, (ii) orange for doubtful data, (iii) red for non valid data and (iv) green for data marked as doubtful by Test 4 related to time since last maintenance. Red data can be either deleted or classified as correct in some rare cases. In all cases, the operator has to make the final decision. Values classified as non valid are then deleted in the final data file. Pre-validation tests are calibrated in such a way that a fully manual validation would have lead to the same results. Calculation of discharge and concentrations of TSS and COD Various methods can be used to calculate discharge including: (i) Manning-Strickler applied to water level, (ii) a water level-velocity relationship in cases where it is locally known, (iii) a locally established rating curve or (iv) a combination of water level and flow velocity measurements. In all cases, standard uncertainties in discharge are calculated by means of the law of propagation of uncertainties (LPU). TSS and COD concentrations are calculated from correlation functions for turbidity, for both dry and wet weather periods. Correlation functions are determined either by the ordinary least squares regression or the Williamson regression, preferably. Details are given in Bertrand-Krajewski et al. (2007) and Torres (2008).

Annexes<br />

type and number of sensors (see Figure 1). The following paragraphs briefly <strong>de</strong>scribe the param<strong>et</strong>ric<br />

tests with an indication of the required param<strong>et</strong>ers.<br />

Test 1a checks if data have been recor<strong>de</strong>d or not. No param<strong>et</strong>er is required for this test. Test 1b checks<br />

if data have been recor<strong>de</strong>d during a maintenance operation by comparing their dates with dates of<br />

maintenance provi<strong>de</strong>d in a specific file entered by the operator in charge of the maintenance.<br />

Test 2 d<strong>et</strong>ects any data outsi<strong>de</strong> the sensor measurement range. Its two param<strong>et</strong>ers are the minimum and<br />

maximum measurable values.<br />

Test 3 checks if recor<strong>de</strong>d data are within the interval <strong>de</strong>fined by two param<strong>et</strong>ers corresponding to the<br />

2.5 percentile and 97.5 percentile of previously validated values measured with a given sensor in a<br />

given location. The two param<strong>et</strong>ers may change with time when more values are observed un<strong>de</strong>r<br />

various dry and w<strong>et</strong> weather conditions.<br />

Test 4 requires two param<strong>et</strong>ers which compare measurement dates to the last maintenance date and<br />

classifies data as either correct, doubtful or even non valid if the duration elapsed since the last<br />

maintenance is too long.<br />

Test 5 d<strong>et</strong>ects sud<strong>de</strong>n, abnormal or erratic increases or <strong>de</strong>creases of values by comparing the<br />

difference b<strong>et</strong>ween instantaneous values (raw signal) and the mobile mean or median (filtered signal).<br />

The required param<strong>et</strong>ers are the number of time steps for the mobile mean or median calculation and<br />

minimum and maximum threshold values.<br />

Test 6 compares the values and the signal dynamics of two redundant sensors in or<strong>de</strong>r to d<strong>et</strong>ect<br />

unusual trends or abnormal gaps.<br />

Test 7 is similar to Test 6 in its principle but compares values and the signal dynamics of any<br />

correlated variables (e.g. water level and flow velocity, upstream and downstream values, measured<br />

and simulated discharges, <strong>et</strong>c.).<br />

Test 8 qualifies data for a given sensor (the influenced sensor) <strong>de</strong>pending on values <strong>de</strong>livered by<br />

another sensor. The test requires threshold values for the influencing sensors and classifies the data of<br />

the influenced sensor as either correct or doubtful. For example, in the case of water level and velocity<br />

sensors, if the water level is too low, velocity measurements are consi<strong>de</strong>red as doubtful. As for Test 3,<br />

influenced and influencing sensors and threshold values are based on previous validated data and may<br />

change with time and experience of the operator.<br />

Data pre-validation<br />

Pre-validation tests are applied to corrected data in or<strong>de</strong>r to assign validation marks. It should be noted<br />

that all tests are not applicable to all data series. Only Tests 1a to 5 can be applied to all sensors. Tests<br />

2, 3 and 5 are sensor specific. Tests 6, 7 and 8 can only be applied if redundant or correlated<br />

information is available. For Tests 2, 3 and 5, specific threshold values can be specified for both dry<br />

and w<strong>et</strong> weather conditions. The distinction b<strong>et</strong>ween the two conditions is <strong>de</strong>fined by the operator and<br />

can be based on any sensor and corresponding threshold value or on any combination of values.<br />

The pre-validation procedure is shown in Figure 1. For each value, Tests 1a and 1b are run first. If the<br />

value is i<strong>de</strong>ntified as not valid, its validation mark is s<strong>et</strong> to 3 and the pre-validation procedure is

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!