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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

6. Data Preprocessing<br />

RMS of kin. solution” in panel “CODSPP 4: Screening Options”) a search for the worst satellite<br />

is initiated. Each satellite is excluded in turn and that satellite is identified for which the<br />

maximum improvement of the solution is realized if its observation is not contributing. This<br />

procedure is repeated until an acceptable solution is found or the redundancy becomes too<br />

small (option “Min. degree of freedom”). In the latter case no epoch-solution is computed and<br />

all observations of the corresponding epoch are marked. These observations are indicated<br />

by the flag KIN in the summary of the bad observations in the CODSPP program output.<br />

If kinematic coordinates are introduced for a station these positions are used as a priori<br />

information for the epoch solutions. All positions in the kinematic coordinate file are<br />

used if epoch-wise kinematic coordinates are estimated in the program run. If a kinematic<br />

coordinate file is introduced and no kinematic positions are estimated (e.g., accuracy of<br />

the introduced kinematic coordinates is better than expected from the estimation in program<br />

CODSPP) then only those epochs are used as a priori which have the flag K (indicating<br />

a good kinematic position) in the input kinematic coordinate file. For other flags all observations<br />

of the epoch are marked.<br />

In the case of LEO processing alternatively a standard orbit can be introduced instead of a<br />

kinematic coordinate file. A receiver on board of a LEO must be labeled in any case with<br />

the marker type SPACEBORNE in the station information file.<br />

6.3.4 Extraction (CODXTR)<br />

CODXTR (”Menu>Processing>Program output extraction>Code-based clock synchronization”) is the extraction<br />

program for the CODSPP program output. It produces a short summary of all CODSPP<br />

output of the following form:<br />

### PG CODXTR: RMS LARGER THAN 999. M FOR STATION: BRMU 42501S004<br />

FILE: ${P}/IGSRAPID/OBS/BRMU3390.CZO<br />

RMS : 1629.07 M<br />

69 FILES, MAX. RMS: 1629.07 M FOR STATION: BRMU 42501S004<br />

MAX. BAD: 7.21 % FOR STATION: OHI3 66008M006<br />

The summary file contains at least two lines. They give the number of code files that were<br />

processed, the maximum RMS, and the station for which this maximum occurred. The RMS<br />

value should be around 25 meters under SA conditions. With SA off the maximum RMS<br />

value is expected to be about 2.5 meters. Using smoothed code obtained with RNXSMT we<br />

can expect a RNS value below 1 meter.Values up to 300 meters are still acceptable although<br />

they deserve special attention. The next line indicates the station with the largest number<br />

of bad code observations. The percentage is usually below 10%.<br />

In the above example the RMS of the station BRMU 42501S004 exceeds the user specified<br />

option “RMS limit for a good station” in panel “CODXTR 2: Options”. The big RMS indicates<br />

that the receiver clock synchronization failed and that the successful further processing of<br />

the data is not guaranteed. The observation filenames of such stations may be listed in a<br />

deletion file which may be used for removing the files in an automatic processing.<br />

Page 112 AIUB

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

Saved successfully!

Ooh no, something went wrong!