Bernese GPS Software Version 5.0 - Bernese GNSS Software

20.4 Description of the Processing Examples
PID 211 RNXSMTAP: This script and the following form a unit. The purpose is to clean
data on the RINEX level. It makes sense to parallelize this step. This first script
prepares the parallelization, the actual processing is done in the next PID. The script
deletes files that may be present from previous runs, and prepares a list of RINEX
files for parallel processing.
PID 212 RNXSMT P: Program RNXSMT is called to clean the RINEX data and identify
cycle slips. Processing is done in parallel, i.e., the program receives a list of RINEX
files to be cleaned in one run. The output consists of smoothed RINEX files (extension
SMT) containing smoothed instead of original code observations. Cycle slips and outliers
are marked.
PID 221 SMTBV3: This script calls program RXOBV3, which creates Bernese observation
files for code and phase from RINEX files. In addition, the station information file is
used to check the RINEX header content. The options set for this PCF are restrictive,
the BPE will stop in case of inconsistencies. If a new station is encountered,
the coordinate file is updated using the RINEX header information. Also, the station
name abbreviation table is updated for stations that are not yet listed. The processing
summary informs about these actions.
The results are zero-difference code and phase observation files for each station (extensions
CZH, CZO, PZH, PZO files in the campaign’s OBS directory).
PID 222 CRDMERGE: Program CRDMERGE sets the geodetic datum and coordinate reference
epoch to a common value for all stations involved.
PID 221 CODSPPAP: This script prepares the parallel run of CODSPP. This script waits
for completion of altogether three PIDs to ensure that all input files are available.
PID 232 CODSPP P: This script runs CODSPP. The receiver clock synchronization is the
main task of CODSPP. The program also determines approximate station coordinates
by a straightforward point positioning approach, using only smoothed code observations.
This is useful in case the a priori coordinates (e.g., from the RINEX header)
are of doubtful quality. Outliers in the observations can be detected in this step, also.
PID 233 CODXTR: This script runs the output extraction program for CODSPP. There
are several such extraction programs available for Bernese processing programs, and
they allow an efficient, quick overview of the results for quality control. In this case,
CODXTR produces a summary file informing on detected outliers, missing orbits,
excluded satellites due to satellite problems, and missing clocks. The file is listed in
the processing summary. A high rms error and/or a lot of outliers indicate a site with
bad code tracking performance.
Further reading: Section 4.2: RINEX Observation Files (page 53), Section 6.2: Preprocessing
on the RINEX Level (page 103), Section 4.2.3: Import to Bernese (page 54), Section 6.3:
Receiver Clock Synchronization and Preprocessing of Code Observations (page 108), Section
19.5.2: Parallel Processing (page 391).
Bernese GPS Software Version 5.0 Page 431