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.

∆δ(PTBB)<br />

20 ps<br />

15 ps<br />

10 ps<br />

5 ps<br />

0 ps<br />

0 4 8 12 16 20 24<br />

Hours of doy 2003-139<br />

∆δ(PTBB)<br />

20 ps<br />

15 ps<br />

10 ps<br />

5 ps<br />

0 ps<br />

14.2 Precise Clock Estimation<br />

0 4 8 12 16 20 24<br />

Hours of doy 2003-139<br />

Figure 14.4: Comparison of the precise receiver clock synchronization with the clock estimation<br />

from the corresponding network solution for the station PTBB,<br />

session 1390 in year 2003 from the example in Section 20.4.4.<br />

In the left figure the coordinates and troposphere parameters are identical<br />

for the receiver clock synchronization and the network solution whereas in<br />

the right hand figure those parameters are recomputed independently for the<br />

receiver clock synchronization.<br />

14.2.4 Precise Receiver Clock Synchronization<br />

If you have a consistent set of satellite orbits, Earth orientation parameters, and satellite<br />

clocks, e.g., as a result from a clock estimation following the processing example in Section<br />

20.4.4, you can synchronize more station clocks to this set of clocks. This works in<br />

the same way as the precise point positioning described in the processing example (see<br />

Section 20.4.1).<br />

Figure 14.4 demonstrates the consistency between the clock results for the station PTBB<br />

for session 1390 in year 2003 from a network solution (result from the example campaign in<br />

Section 20.4.4, file ${P}/DOCU CLK/OUT/TT 03139.CLK) and a precise receiver clock synchronization.<br />

All input options are taken from the last <strong>GPS</strong>EST run in the clock determination<br />

example. The only difference is that the resulting satellite clock corrections<br />

${P}/DOCU CLK/ORB/TT 03139.CLK are introduced as fixed when performing the receiver<br />

clock synchronization for station PTBB (of course, only the observation files for PTBB<br />

are used instead of the entire network). Coordinates and troposphere parameters are introduced<br />

as known from a network solution (left) or recomputed together with the receiver<br />

clock corrections (right).<br />

The left hand diagram shows that the differences to the network solution are below<br />

one picosecond if the station coordinates and the troposphere parameters are fixed<br />

on the network results. In general, however, the station coordinates and the site troposphere<br />

parameters need to be estimated as in the usual PPP approach. The results<br />

of this PPP and the coordinate results from the corresponding network solution<br />

(file ${P}/DOCU CLK/STA/ED 03139.CRD) differ by (−3.1, −0.4, +0.5) mm in the up, north,<br />

and east components. This corresponds to an offset in the estimated receiver clock of about<br />

10 ps which is reflected by the right hand diagram in Figure 14.4. An extended study about<br />

error propagation for time transfer using the <strong>GPS</strong> can be found in [Dach et al., 2003].<br />

This procedure allows you to estimate precise receiver clocks, but it is not possible to<br />

include the results into the <strong>Bernese</strong> observation file. Therefore, this precise receiver clock<br />

synchronization cannot replace the synchronization based on the program CODSPP in the<br />

preprocessing step (see Section 6.3).<br />

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

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

Saved successfully!

Ooh no, something went wrong!