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.

24.3 Adapt the BPE for <strong>Version</strong> <strong>5.0</strong><br />

24.3 Adapt the BPE for <strong>Version</strong> <strong>5.0</strong><br />

This section focuses on the necessary steps to get a BPE from <strong>Version</strong> 4.2 running in<br />

<strong>Version</strong> <strong>5.0</strong> .<br />

• Your Process Control Files (PCF) from <strong>Version</strong> 4.2 can still be used in <strong>Version</strong> <strong>5.0</strong> .<br />

Using it the other way is not guaranteed in all cases (e.g., after editing the PCF<br />

using the ”Menu>BPE>Edit process control file (PCF)”). Make sure that the header lines of the<br />

individual sections in the file are correct (see examples in Section 19.5).<br />

• The CPU control file in <strong>Version</strong> <strong>5.0</strong> is located in directory ${U}/PAN and has the<br />

default extension CPU. It is not compatible to the CPU control file from <strong>Version</strong> 4.2 .<br />

Make sure that your new CPU control file (”Menu>BPE>Edit CPU file”) supports all CPUs<br />

and SPEED-keywords you address in your PCF files. See Section 19.4 and the onlinehelp<br />

for more details.<br />

• Put new program input files into the option directories ${U}/OPT, review and adapt<br />

the program options. The software package does not provide an automatic tool for this<br />

step. Go through all panels and check the settings to benefit from the new data analysis<br />

features of <strong>Version</strong> <strong>5.0</strong> using ”Menu>BPE>Edit PCF program input files”. Use the example BPEs,<br />

the online help, and the documentation as a reference.<br />

In addition you have to copy the menu configuration input files to each of these option<br />

directories. In particular these are<br />

– ${X}/PAN/MENU.INP<br />

– ${X}/PAN/MENU EXT.INP<br />

– ${X}/PAN/MENU PGM.INP<br />

– ${X}/PAN/MENU VAR.INP<br />

• WINDOWS-users need new user scripts written in Perl. You can use the scripts provided<br />

in the example BPEs as modules in your PCF or at least as skeleton for the<br />

development of your own user scripts. See Section 19.6 for more details on writing<br />

user scripts and on available tools for the user scripts.<br />

• It is recommended to run user scripts in Perl on UNIX platforms, too, because of an<br />

increased performance. Nevertheless the old shell scripts may still be used after the<br />

following modifications:<br />

– Make sure that your scripts use only the environment variables: e.g., ${P}. The<br />

links P: in ${U}/WORK are not available and required anymore.<br />

– Adapt the PUTKEY-statements in the user scripts ${U}/SCRIPT:<br />

Example from an user script in <strong>Version</strong> 4.2 :<br />

pp1=$U/PAN/DAT563__.PAN<br />

export pp1<br />

pp2="JOBNUM"<br />

export pp2<br />

pp3=$JOBNUM<br />

export pp3<br />

. $X/SCRIPT/PUTKEYWE<br />

seterr<br />

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

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

Saved successfully!

Ooh no, something went wrong!