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) If the total RMS of a satellite in the RESRMS residual summary table exceeds a<br />

specified RMS threshold value (option “RMS threshold level for a bad solution”) it is<br />

considered that it is the only one (really) “bad” satellite affecting the entire solution.<br />

If more than one satellite exceed this limit only that one with the largest RMS is<br />

considered. If a maneuver hypothesis holds for this satellite it is assumed that a<br />

repositioning occurred. Otherwise the satellite is marked as “bad”.<br />

If a repositioning or a misbehaving satellite was detected an existing satellite problem file<br />

may be updated. If the updated file is used in <strong>GPS</strong>EST (and all other processing programs<br />

in the further steps) the observations of this satellite will be excluded (see Section 6.7.2).<br />

6.7 Marking of Observations<br />

Individual observations may be flagged with a so-called marking flag (the other flag used is<br />

the so-called cycle slip flag) in the <strong>Bernese</strong> binary observation files (code or phase observations,<br />

zero- or single-differences). The marking flags are used to mark outliers, observations<br />

at low elevation, small pieces of observations, etc. If this marking flag is set no program<br />

will use the corresponding observation. It is also possible to reset the marking flags again.<br />

There are several preprocessing programs in the software which mark observations:<br />

RNXSMT marks the code and phase measurements of both frequencies in RINEX files using<br />

the signal to noise ratio as flag (see Section 6.2.5).<br />

CODSPP marks both, phase and code observations for which no receiver clock corrections<br />

could be estimated. Outliers may be marked on request in the <strong>Bernese</strong> code and/or<br />

phase observation files.<br />

MAUPRP marks the observations with low elevations, small pieces of observations, and the<br />

observations suspected to be corrupted by a cycle slip (see Section 6.5).<br />

Note, that the program SNGDIF does not use marked zero-difference observations at all.<br />

6.7.1 Manipulation of Observation Files (SATMRK)<br />

The program SATMRK (”Menu>Service><strong>Bernese</strong> observation files>Mark/delete observations”) may be used<br />

to manipulate flags in <strong>Bernese</strong> observation files, i.e., to set and reset marking flags or to<br />

remove observations. Possible actions are:<br />

EDIT FILE: The entries of an edit information file (description in Section 22.10.7) will be<br />

applied to the <strong>Bernese</strong> observation files. This edit file is usually an output of program<br />

RESRMS.<br />

MARK MANUAL: Mark (set marking flags), reset (remove marking flags), or eliminate<br />

(delete) observations of a satellite for a user specified time window.<br />

SYNCHRONIZATION: The observations in the corresponding code and phase observation<br />

files are synchronized. If an observation is available in one of the files only it will be<br />

removed. If an observation is marked in one file it will be marked in the other file,<br />

Page 136 AIUB

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

Saved successfully!

Ooh no, something went wrong!