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.

6. Data Preprocessing<br />

GAR small pieces of observations (garbage),<br />

O-C observations marked due to large observed–computed values during the epoch difference<br />

solution (see option “Maximum observed-computed value” in panel “MAUPRP 6:<br />

Epoch-Difference Solution”), and<br />

CLK observations marked because no satellite clock value was available when preprocessing<br />

zero-difference files, or<br />

observations marked because of a clock event, see Section 6.5.4.<br />

MAUPRP also gives information on the ambiguities set up. Each satellite has one initial<br />

ambiguity corresponding to the first epoch. All other ambiguities are called multiple. Only<br />

the multiple ambiguities are listed. The ambiguities which were introduced in the most<br />

recent run are marked by an asterisk.<br />

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

MULTIPLE AMBIGUITIES<br />

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

NUMB TYP SATELLITE EPOCH<br />

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

1 *GAP 5 2725<br />

2 *GAP 30 2869<br />

3 *GAP 18 794<br />

4 *GAP 18 2555<br />

5 *GAP 29 2388<br />

The following types of multiple ambiguities are defined:<br />

FIL ambiguity which was already set in the observation file header,<br />

CYC ambiguity which was introduced due to a cycle slip flag in the observation (see option<br />

“If a cycle slip flag in observation file” in panel “MAUPRP 9: Outlier Rejection / Ambiguity<br />

Setting”),<br />

GAP ambiguity which was introduced due to a gap in the observations,<br />

PRP ambiguity which was introduced due to the detection of a cycle slip that could not be<br />

corrected (and outlier rejection was not possible), and<br />

CLK ambiguity which was introduced due to a clock event, see Section 6.5.4.<br />

At the end MAUPRP writes the very important message<br />

FILE SAVED<br />

which means that all the changes were written into the observation file. If “FILE NOT SAVED”<br />

is printed, no changes were made to the original observation file(s) (see option “Save screened<br />

observation files” in panel “MAUPRP 3: General Options”).<br />

Page 126 AIUB

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

Saved successfully!

Ooh no, something went wrong!