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 />

(e.g., from CODE, see Section 4.12.1). Due to the rapidly changing <strong>GPS</strong> satellite geometry<br />

as seen by the LEO several time interval options may have to be reduced with respect to the<br />

default values (e.g., “Minimum time interval accepted for continuous observations” and “Maximum<br />

gap accepted within continuous observations” in panel “MAUPRP 4: Marking of Observations” and<br />

“Mark consecutive outliers up to a time interval”, “After an observation gap larger than” and “Minimum<br />

observed time interval per ambiguity” in panel “MAUPRP 9: Outlier Rejection / Ambiguity Setting”).<br />

You may divide the recommended values given in the on-line help by about a factor of 2.<br />

As a priori information either a kinematic coordinate file or a standard orbit file may be<br />

introduced. The screening may be iterated when an improved orbit from <strong>GPS</strong>EST gets<br />

available. Unless the a priori information is very reliable the estimation of kinematic coordinates<br />

should be enabled (option “Kinematic coordinate estimation” in panel “MAUPRP 6:<br />

Epoch-Difference Solution”). Adapt the constraints to be assigned to the estimated coordinates<br />

to the accuracy of the a priori information (option “RMS limit for epoch solution”). If no reliable<br />

a priori information is available you may have to relax or disable the screening option<br />

“Maximum observed-computed value”.<br />

6.5.7 Program Output Examples<br />

Example 1<br />

The first example stems from the preprocessing of the baseline Brussels–Zimmerwald<br />

(BRUS−ZIMM; day of year 144 in 2002) formed from the data in the example campaign<br />

(see Chapter 20). The baseline length is about 490 km. The options have been set according<br />

to the recommendations in the help panels. The strategy COMBINED has been used.<br />

The beginning of the MAUPRP output file reports the marked measurements. Three reasons<br />

may be responsible for the rejection of an observation: low elevation of the satellite, unpaired<br />

observations, and small pieces of measurements (options from panel “MAUPRP 4: Marking of<br />

Observations”).<br />

------------------------------------------------------------------------<br />

MARK UNPAIRED L1/L2 OBSERVATIONS: SUMMARY<br />

------------------------------------------------------------------------<br />

SATELLITE #L1 MARKED #L2 MARKED<br />

------------------------------------------------------------------------<br />

5 1 8<br />

30 0 0<br />

18 10 0<br />

29 3 5<br />

21 8 1<br />

9 3 0<br />

...<br />

------------------------------------------------------------------------<br />

TOTAL 113 67<br />

------------------------------------------------------------------------<br />

Page 122 AIUB

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

Saved successfully!

Ooh no, something went wrong!