Bernese GPS Software Version 5.0 - Bernese GNSS Software

19. Bernese Processing Engine (BPE)
37: unlink $lstFil if $startcount == 1;
38:
39: # Run program
40: # -----------
41: my $PGMNAM = "HELMR1";
42: $bpe->RUN_PGMS($PGMNAM);
43:
44: # Check whether datum definition accepted or not
45: # ----------------------------------------------
46: if (-s $lstFil and $startcount == 1) {
47: prtMess($bpe,"Inconsistent fiducial station(s) detected");
48: prtGoto($bpe,$param2);
49: }
50:
51: }
The program HELMR1 is started in lines 41–42. A useful method is called on line 31:
$bpe–>getKeys takes a list of keywords and assigns their values to user script variables
(see Section 19.6.5.1). Any variable that is available in the menu may be obtained in this
way. In lines 47 and 48 two BPE utility functions are called (see Section 19.6.5.4). The
corresponding module is loaded in lines 21–22. The first function writes a message into the
BPE protocol file and the second function initiates a jump of the BPE processing sequence
with the action NEXTJOB to the PID specified by PARAM2.
19.6.4 Parallel User Scripts
The examples in this section show a master and slave user script for parallel processing of
individual files. In the first example the relevant lines of the script GPSQIFAP are shown that
prepares the baseline-wise processing of GPSEST for ambiguity resolution:
01: my ( $dirPSH, $extPSH, $sess, ) =
02: $bpe->getKeys(’DIR_PSH’,’EXT_PSH’,’$S+0’ );
03: ...
04:
05: # Get the list of files to be processed
06: # -------------------------------------
07: my @pshLst = glob("${dirPSH}????${sess}.${extPSH}");
08:
09: # Put the files in the parallelization file
10: # -----------------------------------------
11: open(TMP," > $$bpe{CONTROL_FILE}");
12: foreach my $file (@pshLst) {
13: $file = File::Basename::basename($file}); # remove the path
14: $file = substr($file,0,4); # get the baseline ID
15: print TMP "$file\n";
16: }
17: close TMP;
In line 7 the script gets the list of all phase baseline files for the current session in the
campaign directory. In line 11 the control file is opened whose name is available through the
variable $$bpe{CONTROL FILE}. In the loop 12–16 the first four characters of each filename
are written as separate lines into the control file. After termination of the script the control
file contains the following lines based on the files available in the BPE processing example:
01: BRFF
02: BRON
Page 400 AIUB