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.

14. Clock Estimation<br />

to zero. All computed clock corrections are the differences to this reference clock which can<br />

be convenient in some cases. The pre-requirement for this approach is that the reference<br />

clock values are close enough to the <strong>GPS</strong> time (so that the receiver clock synchronization<br />

with program CODSPP is not required) and the observation file contains measurements for<br />

all epochs because the estimation of clock corrections gets singular for epochs without a<br />

reference clock.<br />

In general it is preferable to choose a zero-mean condition for the clock correction estimates<br />

of an ensemble of reference station clocks. If an epoch is missing for a station the clock<br />

corrections for all other receivers can be computed. If, e.g., all receiver clocks are synchronized<br />

to the <strong>GPS</strong> time scale with program CODSPP you may select all receiver clocks as<br />

reference independently from the performance of the receiver clocks. An alignment of the<br />

resulting clock corrections to an optionally selected reference clock can be done later using<br />

program CCRNXC (see Section 14.3.4). The advantage is that no station fulfilling special<br />

requirements needs to be selected for the processing.<br />

Instead of an ensemble of receiver clocks you may choose also the satellite clocks as reference.<br />

Be careful in this case when a satellite clock maintenance event takes place. You may use<br />

the program CODXTR to remove such satellites from the <strong>Bernese</strong> satellite clock files (see<br />

Section 6.3.4).<br />

If parts in your network are not connected to the reference clock by observations to common<br />

satellites, the clock parameters in these parts are singular and no solution is available for<br />

these clocks. For applying the zero-mean condition in program <strong>GPS</strong>EST it is required, too,<br />

that no isolated parts exist in the network.<br />

14.2.3 Program Output and Result Files<br />

The program output of <strong>GPS</strong>EST has two sections for reporting the results of the estimation of<br />

clock corrections: A first section is dedicated to receiver clocks, a second section to satellite<br />

clocks. If the clocks are computed using the epoch-wise pre-elimination/backsubstitution<br />

algorithm the clock values are ordered by time, otherwise the list is sorted by the clock<br />

names. Figure 14.3 shows the results in the program output for the processing example<br />

described in Section 20.4.4 for session 1390 in year 2003. Because this part of the program<br />

output may get very large you can enable the option “Suppression of output concerning epoch<br />

parameters” in panel “<strong>GPS</strong>EST 3.3: Extended Printing Options” to skip this part of the program<br />

output.<br />

The first part reports the receiver clock corrections. For each parameter one line is printed<br />

containing the following information:<br />

TYPE and STAT: Internal numbering in <strong>GPS</strong>EST.<br />

EPOCH (MJD) : Epoch of the clock parameter in modified Julian date.<br />

STATION CLOCK VALUES (USEC):<br />

A PRIORI : A priori value of the clock from the observation file in microseconds.<br />

CORRECTION : Estimated correction of the clock value in microseconds.<br />

TOTAL : Total estimated clock correction in microseconds.<br />

RMS (NSEC) : Formal error for the estimated parameter in nanoseconds.<br />

Page 294 AIUB

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

Saved successfully!

Ooh no, something went wrong!