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.

20.4 Description of the Processing Examples<br />

starting from broadcast clocks. The result file is a clock RINEX file including both station<br />

and satellite clock corrections. A processing summary file CLKyyssss.PRC is written at the<br />

end of the BPE.<br />

Some important features of this BPE are:<br />

• Observation files with significant gaps or unexpectedly big residuals are automatically<br />

rejected.<br />

• All clock solutions are computed with a zero-mean condition for all estimates of the<br />

receiver clock corrections (<strong>GPS</strong>EST in PID 301, 302, and 401). The reference clock for<br />

the final clock RINEX file is selected automatically (CCRNXC in PID 411).<br />

• Coordinates with a flag I (IGS00) in the a priori coordinate file are constrained<br />

when clock corrections are estimated together with the station positions (<strong>GPS</strong>EST<br />

in PID 301). The following runs of <strong>GPS</strong>EST (PID 302 and 401) improve the remaining<br />

station positions from the previous run because these coordinates are assumed to be<br />

unknown.<br />

If you already have well determined coordinates (e.g., from a double-difference solution<br />

based on phase observations), you may also fix or constrain them when estimating<br />

the clock corrections in <strong>GPS</strong>EST. This may be done by selecting all non-blank flags in<br />

the a priori coordinate file (select WITH FLAG in panel “<strong>GPS</strong>EST 4.1: Datum Definition<br />

for Station Coordinates” and # in the subsequent panel in the <strong>GPS</strong>EST.INP files of the<br />

PIDs 301, 302, and 401).<br />

Note when processing your own data: If you do not have precise coordinates, make<br />

sure that you have at least two or three reference sites (flag I in the a priori coordinate<br />

file) included in your processing.<br />

20.4.4.1 Copy Required Files<br />

Before any program is started, all necessary files must be copied to the respective campaign<br />

directories. In addition the a priori coordinates must be prepared.<br />

#<br />

# Copy required files<br />

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

001 CLK_COP CLK_GEN ANY 1<br />

002 COOVEL CLK_GEN ANY 1 001<br />

PID 001 CLK COP: This script copies all needed files into the respective campaign directories.<br />

If appropriate, file names will be changed according to the BPE variable V B<br />

(which holds the prefix for input files) and/or a session-specific date. The files dealt<br />

with in this script are:<br />

File type Source directory Destination directory Renaming<br />

RINEX observation files ORX RAW no<br />

IGS precise orbit file ORB ORB yes<br />

IGS pole file ORB ORB yes<br />

DCB files ORB ORB yes<br />

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

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

Saved successfully!

Ooh no, something went wrong!