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.

20. Processing Examples<br />

PID 313 MPRXTR: Program MPRXTR creates a summary of the previous preprocessing<br />

step. This file is included in the processing summary. An rms value larger than 20 mm<br />

and/or baseline corrections much larger than 0.5 m, as well as a lot of ambiguities<br />

may point out a possible data problem.<br />

PID 321 <strong>GPS</strong>EDTAP: Prepares the parallel run of the <strong>GPS</strong>EDT P script.<br />

PID 322 <strong>GPS</strong>EDT P: This script performs a double-difference phase residual screening. Altogether<br />

four <strong>Bernese</strong> programs are started in sequence:<br />

(1) <strong>GPS</strong>EST to create residual files,<br />

(2) RESRMS to screen these files for outliers,<br />

(3) SATMRK to mark identified outliers, and<br />

(4) <strong>GPS</strong>EST to create final (clean) residual files and store normal equation files.<br />

In both <strong>GPS</strong>EST runs all coordinates are loosely constrained to their a priori values. If<br />

an elevation-dependent observation weighting scheme is applied, normalized residuals<br />

should be stored. RESRMS checks the residual files for outliers based on the options<br />

in panel “RESRMS 2: Options”. Detected outliers are listed in an edit information file<br />

(EDTssssxxx.EDT). SATMRK accordingly marks the corresponding observations.<br />

PID 331 <strong>GPS</strong>CHK: Checks the screening results from the previous step and rejects data of<br />

misbehaving stations if necessary. Two programs are used:<br />

(1) RESRMS to create summaries from the first (unscreened) and final residual files.<br />

(2) RESCHK to create residual screening statistics and detect bad stations based on<br />

their overall performance.<br />

The summaries created by RESRMS and RESCHK are included in the processing summary.<br />

Problematic stations or satellites are indicated by large residuals and/or a very<br />

high percentage of deleted data.<br />

If program RESCHK detects a misbehaving station (depending on the options in panel<br />

“RESCHK 2.1: Detection of Bad Stations”) the corresponding observation file is listed in a<br />

deletion file (EDTyyssss.DEL). The <strong>GPS</strong>CHK script then deletes the rejected file and jumps<br />

back to PID 301 (baseline creation) to create a new network of baselines without the deficient<br />

station and to repeat the preprocessing. This screening loop (PIDs 301–331) is continued<br />

until all stations are accepted. As single-difference files are screened, other (actually good)<br />

stations may be afflicted with errors propagated from the misbehaving station. That’s why<br />

program RESCHK is only allowed to delete one (the worst) station per iteration step to<br />

prevent these stations from being dragged along and being deleted, too.<br />

Further reading: Section 6.4: Forming Baselines (page 113), Section 6.5: Preprocessing Phase<br />

Observations (page 115), Chapter 7: Parameter Estimation (page 139), Section 7.4.4: Real<br />

and Normalized Residuals (page 144), Section 6.6: Screening of Post-Fit Residuals (page<br />

130), Section 6.7: Marking of Observations (page 136), Section 6.6.3: Detect Misbehaving<br />

Stations and Satellites (page 134), Section 19.5.2: Parallel Processing (page 391), Section<br />

19.5.3: Special Actions SKIP and NEXTJOB (page 392).<br />

Page 442 AIUB

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

Saved successfully!

Ooh no, something went wrong!