Bernese GPS Software Version 5.0 - Bernese GNSS Software

19. Bernese Processing Engine (BPE)
On UNIX platforms the environment for Bernese GPS Software is prepared by reading the
file ${X}/EXE/LOADGPS.setvar which has to be available on each host on which clients are
started. There are two possible problems with this concept:
(1) The BPE server and the BPE client may generally source different files having thus
different environments.
(2) Typically, ${X}/EXE/LOADGPS.setvar is sourced during the startup of the login shell.
It is, e.g., executed with the file .bashrc (in case of Bourne-again shell) or with
.tcshrc (in case of tcsh). A BPE client started using the rsh or ssh command may,
however, not execute the startup files at all.
The user is fully responsible for solving the first problem. Possibly differentLOADGPS.setvar
files on different hosts must be compatible, i.e., they must create the same variables pointing
to the same directories. 1
The second problem is solved in the client script ${BPE}/RUNBPE.pm. The client receives the
name of the environment file from the server (from option “Client’s environment file” in ”Menu
>BPE>Start BPE process”, see Figure 19.12) and the file (usually ${X}/EXE/LOADGPS.setvar) is
read and interpreted by the client itself on each client host, see Section 19.6.2.
One remark concerning the temporary area ${T} and the re-definition of the variable ${U}
should be added. Bernese programs (the menu program and the Fortran programs) expect
to have their input files in the directory ${U}/PAN, some auxiliary files go into the directory
${U}/WORK, etc. The BPE must ensure that each user script has its corresponding input files
in directory ${U}/PAN and that there are no interferences between the files belonging to two
different scripts. Therefore the BPE client ${BPE}/RUNBPE.pm performs the following steps:
(1) A new subdirectory is created in the ${T} directory. It has the name
BPE pcfname port year session PID SUB PID that is sufficiently unique. Subsequently
three subdirectories are created in this new directory: PAN, INP, and WORK
(2) The input files are copied from the${U}/OPT/xxx directory (xxx is the option directory
specified in the PCF for each script) into the new PAN subdirectory.
(3) The ${U} variable is redefined in such a way that
${U} = ${T}/BPE pcfname port year session PID SUB PID
(4) The user script is started.
(5) Before the client terminates it deletes the (previously created) temporary directory
tree ${U} unless the “no clean” option is specified in ”Menu>BPE>Start BPE process”.
19.4 CPU Control File
The CPU control file defines which CPUs are available and how the clients are started on
different hosts. CPU files are located in the ${U}/PAN directory (with default extension
CPU). They may be edited through ”Menu>BPE>Edit CPU file”.
1 Actually using the same directories is not mandatory. However, using different directories for the server
and for the client would probably be very rare.
Page 386 AIUB