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.

23.2 Installation Guide for UNIX Platforms<br />

23.2.5.3 Icons of the <strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> for a X-Windows Environment<br />

After the installation of the software you can find a directory ICONS in ${X}/DOC. With the<br />

files in this directory you have the possibility to add an icon for the <strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong><br />

on your desktop. Please consult the file ${X}/DOC/ICONS/README.icons.<br />

23.2.5.4 Load the <strong>Bernese</strong> Environment<br />

Before starting the <strong>Bernese</strong> menu system after login by typing G at the command line,<br />

you have to load the <strong>Bernese</strong> environment by sourcing the LOAD<strong>GPS</strong>.setvar file located in<br />

...BERN50/<strong>GPS</strong>/EXE. You may add the source command to your login procedure.<br />

23.2.5.5 Manually Editing LOAD<strong>GPS</strong>.setvar<br />

While it is possible to manually edit this file, be aware, that this file is analyzed using regular<br />

expressions by the BPE client. Therefore, try to adhere to the given format as closely as<br />

possible. If you want to comment an existing entry before replacing it by a new one make<br />

sure that the valid entry is the last one.<br />

23.2.5.6 Add a new Campaign Directory<br />

For adding another campaign directory you have to define an additional variable (e.g., ${Q})<br />

in the <strong>Bernese</strong> environment file ${X}/EXE/LOAD<strong>GPS</strong>.setvar. In addition each user has to<br />

add this variable in his list of “ENVIRONMENT VARIABLES” in the first panel of ”Menu>Configure<br />

>Menu variables”. To process data from this new campaign directory with a BPE you have to<br />

add this variable to the MENU VAR.INP files in all ${U}/OPT directories.<br />

23.2.6 Compilation of Individual Modules<br />

If you would like to change the memory model after the installation you have to run again<br />

${X}/EXE/configure.pm steps 1 and 4 or you have to change the variable MEMSIZE in<br />

${X}/EXE/LOAD<strong>GPS</strong>.setvar. Source this file and run the Perl script COMPLINK.<br />

If you make other changes in the source files of the software after the installation procedure<br />

you have to distinguish three cases:<br />

(1) Change in an include or module file (directory ${I}):<br />

You have to recompile the full source code using the command COMPLINK, because the<br />

modules and include files are used by several subroutines and programs.<br />

(2) Change in one of the subroutines (directory ${LG}):<br />

• If you have changed the parameter list for a subroutine you have to check whether<br />

an interface definition exists in ${I}/I <strong>GPS</strong>LIB.f90. Adapt the interface and<br />

recompile the full source code using the command COMPLINK.<br />

• Otherwise it is only necessary to recompile the subroutine using CLIB and after that to link all main programs that are calling the<br />

subroutine, using the command CMAIN .<br />

(3) Change in one of the programs (directory ${FG}):<br />

If something was changed in a main program it is sufficient to compile and link this<br />

program using the command CMAIN .<br />

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

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

Saved successfully!

Ooh no, something went wrong!