Bernese GPS Software Version 5.0 - Bernese GNSS Software

20. Processing Examples
appears in the processing summary and may help to identify possible data tracking
problems of observing sites.
Note for processing your own data: Stations showing large data gaps are detected by
RNXGRA and listed in a deletion file (GRAyyssss.DEL in directory OUT), used by the
script to delete the corresponding RINEX observation files from theRAW directory. The
criteria defining an improper station may be changed in panel “RNXGRA 3: Options for
RINEX File Selection”. All deleted stations are reported in the processing summary.
PID 211 RXOBV3AP: This script does not start any programs. It deletes already existing
Bernese zero-difference observation files for the current session and prepares the parallel
execution of the next script.
The degree of parallelization is controlled by the BPE variable V CLU. If it is not
present or unset, one RXOBV3 will be started for each RINEX file to convert (stationwise
processing). Setting V CLU to a positive number leads to one RXOBV3 for each
batch of V CLU stations (clustering). Attuning the cluster size (and thus the number of
parallel running programs) to the available processing power (e.g., number of CPUs)
may improve the computing time of the subsequent RXOBV3 step.
PID 212 RXOBV3 P: Runs RXOBV3 in parallel based on the preparations from the previous
script to convert RINEX to Bernese observation files. The program compares the
data records in the RINEX header with the entries in the station information file.
Any detected header inconsistency is reported in the processing summary. Using the
default settings, the BPE stops with an error if the station name is not in the abbreviation
file or if an antenna type is not listed in the phase center offsets file (default:
${X}/GEN/PHAS COD.I01).
Note for processing your own data: In case of inconsistencies no Bernese observation
files are written because the options for “ACTIONS IN CASE OF INCONSISTENCIES” are
set to SKIP. This is the robust setting to generate a result without manual interactions,
however, stations may be missing in the solution. Alternatively, you may set
the options to ERROR causing the BPE to stop in case of inconsistencies.
PID 221 CODSPPAP: Prepares the parallelization of CODSPP. Please note that this script
waits for altogether three scripts (PIDs 002, 112, 212) to be finished before starting.
In this way it is guaranteed that all necessary input files exist, namely the a priori
coordinates (PID 002), the pole and orbit information (PID 112), and observation files
in Bernese format (PID 212).
PID 222 CODSPP P: CODSPP performs a code-based zero-difference point positioning,
mainly to synchronize the receiver clocks to GPS time on a sub-microsecond level.
A basic outlier detection is included, as well. Epoch-wise clock corrections are estimated
because receiver clocks may not be stable enough to be modeled as polynomials
(at least not at the required accuracy level). Depending on the value of V CLU, program
CODSPP runs in parallel.
Note for processing your own data: CODSPP stops if a priori station coordinates
are missing. Run the example PPP.PCF to update the coordinate and velocity files
(IGS 00.CRD and IGS 00.VEL) or add the entries manually, provided you have coordinates
and velocities for this station on the cm–level.
Page 440 AIUB