Bernese GNSS Software Version 5.2 Tutorial

1 Introduction to the Example CampaignThe last files to be mentioned in this directory are EXAMPLE.BLQ and EXAMPLE.ATL. Theyrespectively provide the coefficients for the ocean and atmospheric tidal loading of thestations. They should at least be applied in the final run of GPSEST.1.2.4 The SAVEDISK Directory Structure (${S})Motivation for the SAVEDISK areaWhen processing GNSS data, a lot of files from various processing steps will populateyour campaign directories. The main result files from the data analysis should be collectedin the SAVEDISK area. This area is intended as long–term archive for your resultfiles.Because the result files are stored in the SAVEDISK area, you can easily clean up your campaignarea without loosing important files. Please keep in mind that the computing performancedecreases if you have several thousands of files in a directory.Structure and content of the SAVEDISK areaWe propose to build subdirectories in the SAVEDISK area for each of your projects. If theseprojects collect data over several years, yearly subdirectories are recommended. It is alsopractical to use further subdirectories like ATM, ORB, OUT, SOL, STA to distribute the filesand to get shorter listings if you are looking for a file.The SAVEDISK area contains after its installation a directory structure according to thedescription above. Each example BPE is assumed as a project. Therefore, you will find onthe top level of the SAVEDISK the directories PPP, RNX2SNX, CLKDET, LEOPOD, and SLRVAL(related to the different example BPEs).In each of these directories you will find several files ending with _REF. They are generatedby running the example BPEs on the system at Astronomical Institute of theUniversity of Bern (AIUB). Even if the objectives of this tutorial and of the RNX2SNXexample BPE are in both cases to process data from a regional network, the resuls mustnot be identical since there are some differences in the processing strategies and selectedoptions.Page 10AIUB