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.

Remarks:<br />

22.7 Orbit Related Files<br />

SATELLITE CLOCKS FROM BROADCAST FILE 07-JAN-04 06:21<br />

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

SAT WEEK TOC #PAR A0 (SEC) A1 (SEC/SEC) A2 (SEC/SEC**2)<br />

2 1252 172800. 3 -0.251892023D-03 -0.670752343D-11 0.000000000D+00<br />

2 1252 180000. 3 -0.251940452D-03 -0.670752343D-11 0.000000000D+00<br />

...<br />

2 1252 252000. 3 -0.252443366D-03 -0.682121026D-11 0.000000000D+00<br />

5 1252 172800. 3 0.122361816D-04 0.147792889D-11 0.000000000D+00<br />

...<br />

124 1252 241200. 2 0.152935050D-04 -0.326291729D-11<br />

Figure 22.26: Satellite clock (CLK) file.<br />

• In CODSPP a satellite clock file has to be specified if standard orbits are used as orbit<br />

information (no clock information stored in standard orbits).<br />

• In MAUPRP and <strong>GPS</strong>EST this file is used to take into account the satellite clock<br />

corrections in the time interval between the measurements of the two receivers of a<br />

baseline. It is of importance only if different receiver types are combined that measure<br />

at significantly different epochs (> 20 millisec).<br />

• Precise high rate clocks are required if MAUPRP is used in the zero-difference mode.<br />

• It is also possible to store the clocks of several sessions in one file.<br />

• If the number of polynomial coefficients is one (#PAR=1) the clock reading routine<br />

does not interpolate for epochs with missing clock values.<br />

• Clock RINEX files may contain also receiver clock corrections. This file type is stored<br />

in the OUT directory of the campaign (see Section 22.10.1).<br />

See Section 5.5 for more information.<br />

22.7.11 Differential Code Biases for Satellites and Receivers<br />

Type: ASCII<br />

Directory: Campaign-specific directory ORB.<br />

Extension: DCB<br />

Content: Differential P1-P2 and P1-C1 code bias (DCB) values for <strong>GPS</strong>/GLONASS<br />

satellites and receivers.<br />

Created by: <strong>GPS</strong>EST (”Menu>Processing>Parameter estimation”) and ADDNEQ2 (”Menu>Processing<br />

>Normal equation stacking”).<br />

Used by: CODSPP (”Menu>Processing>Code-based clock synchronization”), <strong>GPS</strong>EST, ADDNEQ2,<br />

<strong>GPS</strong>SIM (”Menu>Service>Generate simulated observation data”).<br />

Example: Figure 22.27 and ${X}/DOC/EXAMPLE.DCB.<br />

<strong>GPS</strong>-related DCB values are indicated by a leading “G”, GLONASS-related values by a<br />

leading “R”. If such an indicator is missing (e. g., in old CODE P1-P2 DCB files), the<br />

DCB information is assumed to be <strong>GPS</strong>-related. In case of <strong>GPS</strong>/GLONASS-combined receivers,<br />

two receiver-specific bias values are provided, one related to <strong>GPS</strong> and one related to<br />

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

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

Saved successfully!

Ooh no, something went wrong!