08.06.2013 Views

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

Bernese GPS Software Version 5.0 - Bernese GNSS Software

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

BPE server BPE client<br />

starts the client script<br />

Arguments: server host, port number, PID, and<br />

SUB_PID<br />

sends all details concerning this job<br />

(e.g., script name, campaign, session, ...)<br />

sends the QUIT command<br />

19.3 BPE Components and Environment<br />

spawned at the remote host<br />

opens a TCP/IP connection to the server<br />

Message: ready to perform the task PID/SUB_PID<br />

runs the user script for the session in the campaign:<br />

− Load the <strong>Bernese</strong> enviroment variables<br />

− Generate a temporary <strong>GPS</strong>USER environment in the ${T}−area<br />

− Copy all input files from the option directory into the new environment<br />

− Redefine the variables for the temporary user environment<br />

− Write the header of the protocol file<br />

− Run the user part of the script<br />

− Complete the protocol file<br />

− Remove the directory tree in the temporary user environment<br />

Message: the task PID/SUB_PID has been finished<br />

(successfully or with an error)<br />

closes the TCP/IP connection<br />

exits<br />

Figure 19.2: Communications between BPE server and BPE client.<br />

19.3.3 The Environment of the Client<br />

The environment (i.e., the set of variables that are defined and may be used in various<br />

scripts) of the BPE stems from the standard environment defined in the file<br />

${X}/EXE/LOAD<strong>GPS</strong>.setvar (on Windows systems, this environment is stored in the registry<br />

at installation time under HKCU/Environment). However, in distinction to the standard<br />

environment there are two differences:<br />

(1) many additional variables are defined (see Section 19.6.2), and<br />

(2) the variable ${U} is re-defined by the BPE client in such a way that it points to a<br />

(newly created) client-specific directory.<br />

The environment variables for <strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> are handled differently under Windows<br />

and UNIX systems. On a Windows machine all the necessary variables are defined<br />

as system variables. A special variable BERNESE VARIABLES contains a list of those system<br />

variables that are made available for the <strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> client scripts. The field<br />

“Client’s environment file” in ”Menu>BPE>Start BPE process” is not used under Windows and may<br />

remain blank. The user may run the BPE server on a Windows computer and send the<br />

BPE clients to remote machines. However, we doubt that this would be a common option<br />

and we assume that under Windows the BPE server and the clients run on the same host.<br />

In that case it is automatically assured that server and clients have the same set of system<br />

variables (see the note in Section 19.6.2 about general variables available in user scripts).<br />

<strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> <strong>Version</strong> <strong>5.0</strong> Page 385

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!