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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

19.5 Process Control File (PCF)<br />

Option “List of Suspended Process Control Files” in “BPE 2: Suspend processes” allows to prevent<br />

a specific PCF from starting new jobs. The full PCF file name (e.g., RNX2SNX.PCF) must<br />

be specified to stop the corresponding BPE. This may be useful to halt a BPE in order to<br />

make the CPU resources available for a higher priority BPE run.<br />

19.5 Process Control File (PCF)<br />

The Process Control File (PCF) defines which scripts should run and in what order they<br />

should be executed. In addition to listing the scripts to run, the PCF defines which scripts<br />

must wait for other scripts before they can run and defines parameters that are to be passed<br />

into the scripts, the CPU to be used by the client, and the option panels to be used by the<br />

<strong>Bernese</strong> programs executed in the scripts.<br />

The process control files are ASCII files in a format compatible with the previous version<br />

of the BPE. Figure 19.4 shows one of the four example PCFs delivered with the <strong>Bernese</strong><br />

<strong>GPS</strong> <strong>Software</strong> <strong>Version</strong> <strong>5.0</strong> . The file consists of three sections:<br />

(1) Section defining the sequence of the scripts, option directories and CPUs to be used,<br />

and wait conditions (starting with header string PID SCRIPT, see description below).<br />

(2) Section defining parameters and special actions (starting with header stringPID USER,<br />

see Section 19.5.2).<br />

(3) Section defining values for variables passed to the scripts (starting with header string<br />

VARIABLE).<br />

As you can see in the example of Figure 19.4 comments may be added to the PCF in any<br />

place, even between a sequence of scripts. Comment lines have to start with a hash-character<br />

(#).<br />

As for <strong>Version</strong> 4 the PCF files may be edited in any ASCII editor. Alternatively you may<br />

edit them using the edit facility provided by the menu under ”Menu>BPE>Edit process control file<br />

(PCF)”. Note, that you have in the second case no possibility to add comment lines.<br />

19.5.1 General Definition of the Scripts<br />

Figure 19.5 shows the first panel that appears when the user starts to edit a PCF (same<br />

PCF as displayed in Figure 19.4):<br />

• The user has to specify the names of the scripts in column “Script” and has to assign<br />

a unique PID (Process Identifier) number to each script.<br />

• The column “Opt dir” contains the name of the option directory that will be used to<br />

get input files from. The option directories must reside in ${U}/OPT.<br />

• Column “Campaign” contains the name of the campaign to process. Normally this field<br />

is left blank to run the script in the active campaign of the BPE. This allows to process<br />

any campaign using the same PCF. The field is intended to execute individual scripts<br />

in different campaigns.<br />

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

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

Saved successfully!

Ooh no, something went wrong!