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.4 Forming Baselines<br />

Furthermore the CODXTR summary output shows one line for each station–satellite combination<br />

where more than 50 epochs are considered as outliers or marked for any other reason.<br />

The first two numbers of these lines reflect the internal CODSPP numbering and are not<br />

important. Station name, outlier identification, and satellite PRN number follow. The outlier<br />

identification is most commonly OUT. Other possible entries are listed in Section 6.3.2.<br />

The line terminates with the start and end epochs of the outlier interval and the number of<br />

observations in this interval.<br />

2 1 ALBH 40129M003 OUT 31 03-12-05 06:47:00 03-12-05 10:18:00 423<br />

7 1 ALBH 40129M003 OUT 31 03-12-05 16:00:00 03-12-05 16:59:30 120<br />

9 2 ALGO 40104M002 OUT 31 03-12-05 15:30:30 03-12-05 15:58:30 57<br />

10 3 ALIC 50137M001 OUT 31 03-12-05 01:26:00 03-12-05 05:02:00 433<br />

11 3 ALIC 50137M001 OUT 31 03-12-05 05:07:30 03-12-05 05:54:30 95<br />

103 4 AMC2 40472S004 OUT 31 03-12-05 07:27:00 03-12-05 10:03:00 313<br />

108 4 AMC2 40472S004 OUT 31 03-12-05 15:13:00 03-12-05 16:59:30 214<br />

.....<br />

116 8 ZAMB 34601M001 OUT 31 03-12-05 00:00:00 03-12-05 03:14:30 390<br />

117 8 ZAMB 34601M001 OUT 31 03-12-05 03:21:00 03-12-05 04:00:00 79<br />

### SATELLITE REPOSITIONING OR CLOCK RESET DETECTED!<br />

# SATELLITES : 1<br />

SATELLITE NUMBER: 31<br />

If the same station is listed for many satellites, something is probably wrong with its data.<br />

If the same satellite is listed for many stations there is something wrong with the satellite.<br />

In the above example satellite 31 was marked for many sites. As the marked time intervals<br />

are distributed over the day and do not concentrate towards the end of the day the outliers<br />

are not caused by a maneuver. In fact, on this particular day satellite 31 was scheduled<br />

for maintenance. Usually the satellite clock is reset in such cases. The outlier detection of<br />

CODSPP handles such problems and no action is required by the program user.<br />

If such an event is detected the clock values for the corresponding satellite may be removed<br />

from the satellite clock file containing, e.g., broadcast clock. This action is reported in the<br />

summary by the line:<br />

1 SATELLITE(S) REMOVED FROM BROADCAST CLOCK FILE.<br />

SATELLITE NUMBER(S): 31<br />

6.4 Forming Baselines (SNGDIF)<br />

The <strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> uses double-differences as basic observables. The singledifferences<br />

(between receivers, see Section 2.3.4) are stored in files, the double-differences are<br />

created in program <strong>GPS</strong>EST. Program SNGDIF (”Menu>Processing>Baseline file creation”) creates<br />

the single-differences and stores them in files. The program may create single-differences<br />

for both, phase and code measurements. Usually, only the phase single-differences are used<br />

for further computations. An important exception is the ambiguity resolution using the<br />

Melbourne-Wübbena linear combination. In that case the code single-differences have to be<br />

formed, too.<br />

<strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> <strong>Version</strong> <strong>5.0</strong> Page 113

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

Saved successfully!

Ooh no, something went wrong!