Bernese GPS Software Version 5.0 - Bernese GNSS Software

20.5 Processing own Data With Example BPEs
Note that in the example, we use the campaign directories as location for the input files.
Instead of "$dirPre" you should type in the location of the precise orbit files in your
local data pool. If necessary you may also change the filename – use time variable to keep
the script session independent (see Sections 18.5.1 and 19.6). The ORX directory contains
in this example the original RINEX observation files. This ensures, that you will always
have a copy of these files available (keywords: RINEX screening, cleaning up scripts). After
these preparatory steps, you are ready to run a PCF from the examples with your own
campaign/data. Furthermore, you could also adapt the save and deletion scripts to your
preferences. It’s as simple as that.
You may need more changes in program options or user scripts depending on your application
(e.g., another troposphere setup according to the recommendations in Section 11.6 if
you analyze a local instead of regional network). Be sure to keep the program input panels
in the OPT directories consistent with your changes! Surely, by now, you also have realized
the value of using menu or BPE variables as much as possible to keep modifications in
scripts and panels simple.
If you have changed some of the user scripts or program input options and you want to
go back to the original examples you can copy them from the ${X}/PCF, ${X}/OPT, and
${X}/USERSCPT into your user environment ${U}/PCF, ${U}/OPT, and ${U}/SCRIPT.
20.5.2 GNSS Processing
The double-difference example is designed for the analysis of GNSS data (GPS and
GLONASS). If you carefully check the results, you will see that in the initial setup of
the example only GPS data are used. The reason is, that IGS precise files contain only GPS
orbit information.
If you have data files from combined receivers you can use the orbits and Earth orientation
parameters from CODE containing consistent GPS and GLONASS orbits. To implement
this you have to change the filename for the orbit and pole files in the R2S COP script
from $filDat = "IGS${wwwwd}.PRE"; to $filDat = "COD${wwwwd}.PRE"; and
from $filDat = "IGS${wwww}7.IEP"; to $filDat = "COD${wwww}7.IEP";
You may change the content of the BPE variable V B to indicate the use of CODE orbits in
filenames.
Alternativly you have to merge the combined GPS and GLONASS final orbit files from
the IGS. They are not as consistent as the CODE product because they are (apart from
the CODE contribution) generated in individual procedures by a different set of analysis
centers which are futhermore combined in two independent procedures.
20.5.3 Change of the Reference Frame
The examples use the IGS00 realization of the ITRF2000 reference frame. The IGS realization
has been updated to IGS00b and is used since GPS-week 1253 (January, 2004;
IGS Mail 4666). To change this reference frame, you have to download the corresponding
files from http://www.aiub.unibe.ch/download/BSWUSER50/STA: IGS 00B R.CRD,
IGS 00B R.VEL, andIGS 00B.FIX. You can generate a new a priori coordinate set by running
the PPP example using IGS 00B R for the “Master/reference CRD/VEL file name” (V CRDREF)
Bernese GPS Software Version 5.0 Page 457