Bernese GPS Software Version 5.0 - Bernese GNSS Software

3. Campaign Setup
variable to the file ${X}/EXE/LOADGPS.setvar (and reload this file) 2 . Windows-users must
define the corresponding environment variable in their user-environment. To run a BPE
they also have to add the new variable to the existing BERNESE VARIABLES environment
variable (see Section 19.3.3). Windows 9x-users have to adapt the file C:\BSW50env.bat in
a corresponding way and reboot the computer to make the new variables active. All users
also have to add this new environment variable to the list in the ${U}/PAN/MENU VAR.INP
file (use (”Menu>Configure>Menu variables”). The new environment variable must be provided to
each BPE option directory, too (${U}/OPT/*/MENU VAR.INP).
Select the campaign${P}/MYCAMP as the active campaign using the ”Menu>Campaign>Select active
campaign”. You may get a message that no session table is available in your actual campaign.
Do not worry about it at that time: The session table will be provided in a further step.
The active campaign is now displayed in the status line of the menu.
Now the campaign-specific directories for the active campaign have to be created. This is
done in ”Menu>Campaign>Create new campaign”. Users on multiuser systems have to take care of
the write protections especially in the top-level directory where the campaign directory will
be created. By default the following directories will be created:
${P}/MYCAMP/ATM location of campaign specific atmosphere files (e.g., ION, TRP)
${P}/MYCAMP/BPE area for output from BPE runs
${P}/MYCAMP/OBS location of Bernese observation files
${P}/MYCAMP/ORB location of orbit related files (orbit files, ERP-files, satellite clock files,
DCB, etc.)
${P}/MYCAMP/ORX original RINEX files
${P}/MYCAMP/OUT output files
${P}/MYCAMP/RAW RINEX files ready to import into the processing
${P}/MYCAMP/SOL solution files (e.g., normal equations, SINEX)
${P}/MYCAMP/STA campaign specific station files (STA, FIX, CRD, etc.), the campaign’s
session table (SES) is here, too
In addition a default session table will be copied into the campaign
(${P}/MYCAMP/STA/SESSIONS.SES). Check the entry for the option “Session Table” in
the dialogue ”Menu>Configure>Set session/compute date”. We refer to Section 3.3 for more details
on the setup of the session table.
3.2 File Naming Convention
The user is responsible for the naming of the output and result files in the campaign directory.
We recommend to use the default directories and extensions for all file types. The
filenames may be specified by the user in the program input panels. Filenames (as well
as the path) may not contain blanks or any other special characters (dots, slashes, etc.).
The complete string of the filename (starting from the campaign path to the extension
2 In any case if you need to modify this file manually take care to keep its syntax because the BPE reads
this file to install the Bernese environment on a remote host (see Section 19.3.3).
Page 44 AIUB