Bernese GPS Software Version 5.0 - Bernese GNSS Software

20. Processing Examples
PID 903 CLK DEL: This script deletes all files which are no longer needed after the end of
the BPE. This prevents unimportant files from accumulating.
PID 904 BPE CLN: Deletes files from the campaign’s BPE-subdirectory with a delay of
30 sessions. Thus, all BPE protocol and log files of the last 30 sessions will remain in
the directory.
PID 999 DUMMY: Does nothing.
The result saving step (PID 902) is skipped in this example. This can easily be changed by
removing the SKIP keyword in the PCF for this PID.
The deletion script (PID 903) can be forced to delete all files not only from previous but
also from the current session (except of some important result and summary files) by setting
PARAM1 for that script to ALL.
The DUMMY-script may seem useless at a first glance. But if you have such a script running
at a well defined PID (e.g., PID 999) in all your PCFs the successful execution of a BPE can
be tested in a generic way by checking the existence of the DUMMY-script’s LOG- or PRT-file.
In this way a script starting a BPE can check the successful completion of the BPE and
react in case of errors (e.g., send an error mail).
Further Reading: Section 19.10: BPE Output and Protocol Files (page 415), Section 19.11:
Error Handling (page 417).
20.5 Processing own Data With Example BPEs
The example PCFs provided in Version 5.0 of the Bernese GPS Software are designed to be
used in real life applications. The options are set for a daily analysis of a regional network.
Depending on your requirements, some steps may be left out, but the intention of these
examples is to provide an optimal processing tool for the given applications. This section
describes how to use these PCFs on your own campaign data and how to process kinematic
stations.
20.5.1 Preliminaries
It is assumed, that your campaign has been set up, basic files are located in the correct
directories, and that the session is correctly defined. For further information, see Chapter 3.
Now, you have to adapt the location of the original RINEX observation and other input
files. This needs to be done in the copy scripts of the PCF in question (PPP COP, R2S COP,
resp., CLK COP in the ${U}/SCRIPT directory). If you inspect the copy BPE scripts you will
see that this modification is already well prepared:
# - Orbit file
$dirDat = "$dirPre";
$filDat = "IGS${wwwwd}.PRE";
copy("${dirDat}${filDat}","${dirPre}${b}${yyssss}.${extPre}") or
die "${dirDat}${filDat} not found";
Page 456 AIUB