Bernese GPS Software Version 5.0 - Bernese GNSS Software

19.11 Error Handling
The standard output and error output of the BPE client and user scripts may be re-directed
into a log file (e.g., by specifying “--stdout= --stderr=” in the CPU file –
see Section 19.4). In this case the file will contain debug output from programs and scripts
as well as system messages in case of a hard crash of a program or script. The name and
default location of the log file is the same as the name of the corresponding protocol file
but the default extension is LOG.
19.11 Error Handling
19.11.1 Checks when Preparing a BPE
The chance of errors (particularly during the preparation of a new BPE run) is relatively
high due to the complexity of the system. However, if one follows a few basic recommendations
it should not be too difficult to eliminate the errors rapidly:
(1) Before trying to work with the BPE make sure that the Bernese GPS Software is
behaving correctly in non-BPE mode.
(2) Make sure that the CPU-file (see Section 19.4) is correct. If remote-shell or secure-shell
commands are used in the CPU-file, test these commands outside the BPE. Make sure
that the commands run in background on UNIX. The submission of a command must
be possible without interaction (e.g., without entering a password when using ssh).
(3) Before preparing your own BPE runs, check that the examples delivered with the
Bernese GPS Software work properly.
(4) Before running any new BPE in non-interactive mode, try the interactive mode first.
The error messages in both modes are the same but in non-interactive mode one has
to know where to find them. In interactive mode the menu program tries to display
the error messages automatically. Already before actually starting the BPE server the
menu program checks several things (particularly the process control file) for logical
errors (e.g., required waiting for a non-existing script etc.). A number of checks are
already performed when editing a PCF file using ”Menu>BPE>Edit process control file (PCF)”.
(5) Test new user scripts outside the BPE as far as possible before incorporating them
into the BPE. The syntax of a Perl script may, e.g., be checked using the command
perl -c script.
(6) Use the die- instead of exit-command for handling errors in scripts.
(7) Check carefully that the program output files generated by the BPE are unique so
that they are not mutually overwritten by other scripts running in parallel. Make sure
that the output file names specified in the program input files correspond to the names
of input files needed by successive programs.
(8) Make sure that each BPE option directory contains the menu input files MENU*.INP.
Remember that the BPE uses the files from the option directories and not those from
the user environment ${U}/PAN. This is particularly important if you add, e.g., a drive
variable to MENU VAR.INP.
Bernese GPS Software Version 5.0 Page 417