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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6. Data Preprocessing<br />

6.3.2 Preprocessing of Code Observations<br />

If the option “Outlier detection” is enabled (see panel “CODSPP 4: Screening Options”) the<br />

program CODSPP fully replaces program CODCHK which was necessary in old versions of<br />

the <strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong>.<br />

The program CODSPP processes the observation files epoch by epoch. The term observed<br />

minus computed (O–C) is calculated for each observation of an epoch introducing the satellite<br />

orbits, satellite clocks, and the a priori position of the station (or the position that<br />

resulted from the previous iteration). Based on these O–C values the receiver clock correction<br />

for this particular epoch is obtained by a majority voting. After correcting the O–C<br />

values for all observations for the receiver clock correction the residuals are analyzed for<br />

outliers. If the outlier detection is disabled or the biggest residual is smaller than a user<br />

specified threshold (Option “Max. residual allowed”) all observations of this epoch are accepted<br />

and will contribute to the coordinates and/or the <strong>GPS</strong>/GLONASS time offset.<br />

If the residual of at least one observation of an epoch exceeds the threshold specified the<br />

outlier detection procedure starts. From all residuals of the epoch a noise level (RMS without<br />

the worst satellite) is then computed. Either this noise level or the RMS of unit weight from<br />

the previous iteration (the smaller value is selected) is scaled by the user defined “Confidence<br />

interval” to get a threshold for the biggest residual of the epoch. If the threshold is exceeded<br />

the observation corresponding to the biggest residual is flagged and the majority voting to<br />

compute the receiver clock correction is repeated without the flagged observations.<br />

When the receiver clock corrections are written to the observation files also the flagged<br />

observations may be marked in the code, phase, or both observation files (see option “Mark<br />

outliers in obs. files”). Usually only the code observations should be marked because the outlier<br />

detection is done for this observation type only. If you don’t use the code observation files<br />

in further processing, marking of bad observations is not necessary.<br />

Because the noise level of the raw code measurements may vary considerably between different<br />

receiver types, the use of station observation sigma factors (station weighting) is highly<br />

recommended to scale the outlier threshold. The threshold (option “Max. residual allowed”)<br />

is multiplied with the station specific sigma factor to obtain the effective outlier rejection<br />

threshold for the respective station. A sigma factor below 1.000 is set to 1.000. If you are<br />

using smoothed code from program RNXSMT the use of the sigma factors for the rescaling<br />

of the outlier rejection threshold is not required. See Section 22.8.14 for the definition and<br />

Section 6.6.3 for the creation of a station observation sigma file.<br />

If you use CODSPP to get receiver clock synchronization for a phase only based baseline<br />

processing you should choose a high outlier rejection threshold (e.g., 30 m). You have to<br />

keep in mind that an epoch where CODSPP could not compute a receiver clock value for<br />

the station will be lost for all further processing.<br />

Page 110 AIUB

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

Saved successfully!

Ooh no, something went wrong!