Bernese GPS Software Version 5.0 - Bernese GNSS Software

20. Processing Examples
20.4.1.7 Create Summary File and Delete Files, end of BPE
This block wraps up the PPP.PCF example. No processing program is called. It will in one
form or the other also be part of your own PCFs.
#
# Create summary file and delete files
# ------------------------------------
901 PPP_SUM PPP_GEN ANY 1 322 331 421 431 511 522
902 PPP_DEL PPP_GEN ANY 1 901
903 BPE_CLN PPP_GEN ANY 1 902
#
# End of BPE
# ----------
999 DUMMY NO_OPT ANY 1 903
PID 901 PPP SUM: This step produces a comprehensive summary of the previous processing
steps allowing to check the quality of the obtained results. The provided information
includes:
• Error messages, warnings, and pseudo-graphics concerning RINEX conversions
• Stations without ocean loading coefficients
• Orbit generation, single-point-positioning, preprocessing, and screening summaries
• Station information (as extracted from SINEX file)
• Analysis results (e.g., coordinates, ionosphere parameters, DCBs, station clock
corrections, and geocenter parameters)
PID 902 PPP DEL: This script is responsible for deleting unused files generated during this
and previous PCFs (e.g., intermediary results, program output files, auxiliary files,
etc.). This script is set up to prevent the accumulation of files in the campaign. It is
recommended to inspect and modify this script to keep files of interest.
PID 903 BPE CLN: This step is responsible for cleaning up BPE-specific files (LOG and PRT
files in the campaign’s BPE directory) with a delay of 30 sessions.
PID 999 DUMMY: Does nothing. This script provides a well defined PID as end point,
useful, e.g., as jump address, or to check for the completion of the BPE.
The deletion script (PID 902) 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 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 in all your PCFs the successful execution of a BPE can be tested in
a generic way by checking the existence of this script’s LOG- or PRT-file. In this way a script
starting a BPE can 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).
Page 436 AIUB