Bernese GNSS Software Version 5.2 Tutorial

3.3 Session GoalsThe similar file may be generated using the orbit products from IGS (including the EOPinformation) following the procedure described in Section 7.1 . As you can notice the RMSerrors are slightly higher. It does not mean that the orbits from CODE are better thanthe IGS orbits. The orbit model in ORBGEN is only more consistent with the orbit modelused at CODE:EXAMPLE: Session 102070: Standard orbit generation 10-JAN-14 18:28TIME FROM DAY : 1 GPS WEEK: 1594TO DAY : 2 GPS WEEK: 1594-------------------------------------------------------------------------------ORBIT REPEATABILITY FROM A 1-DAY FIT THROUGH DAILY ORBIT SOLUTIONS (MM)# ECLIPSING SATELLITES: 5 E / 0 M ( 0 EM)----------------------------- ... ---------------------- ... ----ECL .. .. .. .. .. .. .. E. E. E. .. ..DOY 1 2 3 4 5 6 ... 12 13 14 15 16 ... 32----------------------------- ... ---------------------- ... ----207 2 1 4 1 2 3 ... 3 3 3 2 3 ... 2----------------------------- ... ---------------------- ... ----ALL 2 1 4 1 2 3 ... 3 3 3 2 3 ... 2----------------------------- ... ---------------------- ... ----(Note the missing GLONASS satellites in the IGS orbit product.)In the example for day 208 of year 2010 a satellite 75 appears. The GPS–satellite 25 hada repositioning event at 2010–07–27 16:08:03 (see ${X}/GEN/SAT_2010.CRX). The satelliteis introduced in the processing with two independent arcs: one before (number 25) andone after (number 75) the event (you may verify this by the number of epochs availablefor each of these two satellite arcs).3.3 Session GoalsAt the end of this session, you should have created the following files:1. Bernese pole file in the campaign’s ORB directory: COD10207.ERP,2. Bernese standard orbit file in the ORB directory: COD10207.STD,3. Bernese satellite clock file in the ORB directory: COD10207.CLK.Bernese GNSS Software, Version 5.2 Page 25