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.6.3 Detect Misbehaving Stations and Satellites (RESCHK)<br />

For a robust automated processing it is essential to have a tool at hand to detect and exclude<br />

misbehaving stations, e.g., stations with strange data that cannot be handled properly in<br />

the preprocessing programs of <strong>Version</strong> <strong>5.0</strong> of the <strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> – at least not with<br />

the default settings used in an automated processing. Also satellites whose orbits are not<br />

modeled sufficiently well (e.g., due to a repositioning event) should be detected and excluded<br />

from the processing.<br />

The <strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> <strong>Version</strong> <strong>5.0</strong> provides such a tool with program RESCHK (”Menu<br />

>Service>Automated processing>Detect misbehaving stations/satellites”). It is able to analyze the summary<br />

file of the program RESRMS and to detect events in the solution. The program handles only<br />

one problem type per run, following the priority<br />

(1) MANEUVER DETECTED FOR SATELLITE(s),<br />

(2) BAD STATION(S) DETECTED,<br />

(3) BAD SATELLITE(s) detected,<br />

(4) SATELLITE(s) W/O OBSERVATIONS detected, or<br />

(5) NO SPECIAL EVENTS FOUND IN THIS SOLUTION.<br />

The result is reported by the above strings in the program output.<br />

Keep in mind that the identification of “misbehaving” stations or satellites may also indicate<br />

that your settings of the preprocessing input options are not optimal!<br />

Bad Station Detection<br />

A station or baseline is assumed to be “bad” if the total RMS in the last column of the<br />

RESRMS residual summary file exceeds a user specified threshold (“Maximum allowed overall<br />

RMS error” in panel “RESCHK 2.1: Detection of Bad Stations”).<br />

In the case of baseline residuals the “bad” stations are extracted in the following way from<br />

the list of “bad” baselines:<br />

• If a station from a “bad” baseline is found in any “good” baseline, too, the station<br />

is assumed to be “good”. If both stations of a “bad” baseline are set back to “good”<br />

this may indicate a problem in preprocessing of the baseline (e.g., options for program<br />

MAUPRP).<br />

• If a station is found in only one baseline the other station of the baseline is checked.<br />

If this other station is found in “bad” baselines only, the first station is marked as<br />

“good”. If the second station is “good”, the first station is marked as “bad” (it is<br />

assumed that a “bad” baseline contains only one “bad” station).<br />

The option “Maximum number of stations to delete” provides a limit for the number of stations<br />

to be deleted per program run. If more “bad” stations are found the stations with the<br />

biggest total RMS errors are selected. If you analyze baseline residuals the total RMS of a<br />

station is computed as the mean RMS over all baselines containing the station. If the total<br />

RMS of at least one station in the zero-difference case exceeds the limit specified in option<br />

Page 134 AIUB

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

Saved successfully!

Ooh no, something went wrong!