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

is set to 2. All observations considered as good have a signal to noise ratio of 9. From this<br />

convention you can derive the options in panel “RXOBV3 4: Input Options 2” for converting<br />

smoothed RINEX files into <strong>Bernese</strong> observation file format using the program RXOBV3 (see<br />

Figure 6.4). All other settings and checks in the program RXOBV3 are identical for original<br />

and smoothed RINEX files. They are described in Section 4.2.3.<br />

6.3 Receiver Clock Synchronization and<br />

Preprocessing of Code Observations (CODSPP)<br />

6.3.1 Receiver Clock Synchronization<br />

In Section 2.3.5 we have seen that the receiver clock has to be synchronized with <strong>GPS</strong> time<br />

even for a double-difference analysis. The receiver clock error δk has to be known with an<br />

accuracy better than 1 µs. It would be possible to introduce δk as unknown parameters<br />

during the final least-squares adjustment in program <strong>GPS</strong>EST, but this would increase<br />

the number of parameters considerably. Fortunately, it is possible to compute δk a priori<br />

with sufficient accuracy (< 1 µs) using zero-difference code measurements. This is the<br />

main task of program CODSPP (”Menu>Processing>Code-based clock synchronization”), the second<br />

important result from this program are the receiver coordinates. Looking at Eqn. (2.29) we<br />

conclude that if we want to reach an accuracy of 1 µs in δk it is necessary to have the code<br />

measurements available with an RMS error smaller than<br />

c (δk)max = c (1 µs) ≈ 300 m<br />

(c is the velocity of light). Obviously, even C/A-code measurements are sufficient for this<br />

purpose. CODSPP will process P-code or smoothed code, of course, if available.<br />

For the zero-difference analysis of the data in the parameter estimation program <strong>GPS</strong>EST<br />

the results of the receiver clock synchronization are introduced as a priori values for the<br />

station clock estimation. Because the dependency of the observation on the clock parameters<br />

is almost linear, the clock a priori value is not very important. On the other hand the<br />

receiver clock synchronization on the 1 µs level is necessary in the zero-difference case, too.<br />

In addition, the numerical stability in program <strong>GPS</strong>EST is improved when the estimates for<br />

the clocks are not too big.<br />

Program CODSPP uses the standard least-squares adjustment to compute the unknown<br />

parameters. The observables are the zero-difference code measurements. Usually, the L3<br />

(ionosphere-free) linear combination is used. The most important parameters computed by<br />

CODSPP are the receiver clock corrections δk. These parameters will be estimated in any<br />

case. The resulting receiver clock corrections are written directly into the <strong>Bernese</strong> observation<br />

files. This may be suppressed if the option “Save clock estimates” in panel “CODSPP 2:<br />

Input Options” is disabled. This may be useful for test purposes. In the normal processing<br />

this options has to be BOTH which is indicated in the program output file by the line:<br />

CLOCK OFFSETS STORED IN CODE+PHASE OBSERVATION FILES<br />

for each station. Otherwise a warning message is issued.<br />

Page 108 AIUB

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

Saved successfully!

Ooh no, something went wrong!