08.06.2013 Views

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

6. Data Preprocessing<br />

result in large RMS errors of the other parameters estimated in <strong>GPS</strong>EST. There is still the<br />

chance that the problem is actually not a cycle slip, but an outlier, and that only one or<br />

a few observations are corrupted. If the cycle slip problem appears in the epoch-difference<br />

between the epochs t1 and t2, the first corrective action is usually to mark (i.e., not use) the<br />

observation stemming from epoch t2 (“Enable outlier rejection” in panel “MAUPRP 9: Outlier<br />

Rejection / Ambiguity Setting”) and to try the same tests using the epoch-difference between<br />

the epochs t1 and t3 and possibly t1 and t4 etc. Of course, there is a parameter which limits<br />

the length of the interval [t1,tx]. It is specified by option “Mark consecutive outliers up to a time<br />

interval”.<br />

Small cycle slips in the data (up to about 10 cycles) might not be real but due to a high<br />

noise level (e.g., for low elevation data). To reduces the probability that such cycle slips are<br />

corrected the user may specify a minimum slip size in option “Minimum size of accepted cycle<br />

slip correction”. If b1p, b2pq, and b5q are all smaller than this value the cycle slip is considered as<br />

an outlier and is marked. With the option “Do not accept cycle slip corrections” the correction<br />

of cycle slips may generally be suppressed. This is recommended when processing zerodifference<br />

files because the introduction of the satellite clocks adds additional noise.<br />

If you have to rerun MAUPRP for a set of observation files and you had cycle slip correction<br />

enabled, you have to rebuilt the observation files first using SNGDIF for single-difference<br />

files or RXOBV3, CODSPP for zero-difference files.<br />

Cycle Slip Detection: Single Band Algorithm<br />

If the screening mode L1, L2, or BOTH is selected in option “Screening mode, frequency to check”<br />

of input panel “MAUPRP 3: General Options”, MAUPRP does not create any linear combination<br />

of the measurements. The value m is computed as<br />

m = r1 or m = f2 2<br />

f 2 1<br />

and only the condition (6.8) is tested (and not the condition (6.6)).<br />

r2<br />

(6.11)<br />

For short baselines (< 10 km) the method BOTH is preferable because of the higher noise<br />

level of the ionosphere-free linear combination L3 used in the COMBINED mode for the cycle<br />

slip detection. For longer baselines the COMBINED mode is mandatory as only there the<br />

ionosphere-free linear combination L3 of the L1 and L2 observations is used. The BOTH mode<br />

actually consists only of the single frequency preprocessing for L1 and L2 independently.<br />

Zero-difference files and observation files from kinematic stations can only be screened in<br />

the COMBINED mode.<br />

6.5.4 Clock Events in Preprocessing of Zero-Difference Files<br />

In principle jumps in the receiver clock are uncritical. This is true if such events are treated<br />

in a consistent way in the RINEX files. They affect the observation epoch, the code, and the<br />

phase measurements in a similar way. To synchronize the receiver clocks program CODSPP<br />

needs to run before MAUPRP is executed.<br />

Page 120 AIUB

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

Saved successfully!

Ooh no, something went wrong!