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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

10. Station Coordinates and Velocities<br />

fore, epoch-wise pre-elimination and resubstitution of epoch parameters (description see Section<br />

7.5.6) is preferable for most applications. It is enabled when the option “Pre-Elimination”<br />

in panel “<strong>GPS</strong>EST 5.1” is set to EVERY EPOCH for kinematic coordinates.<br />

The way formal errors of kinematic coordinates and normalized residuals are computed in<br />

the case of epoch-wise pre-elimination and resubstitution depends on the setting for option<br />

“Var-covar wrt epoch parameters” in panel “<strong>GPS</strong>EST 3.2: General Options 2”. If the option is set to<br />

SIMPLIFIED formal errors are computed based on the epoch solution only, with the non-epoch<br />

parameters introduced without error. With the option set to CORRECT the formal error is<br />

computed correctly but the processing time and memory consumption may become very<br />

large. For option SIMPLIFIED it is then preferable to scale normalized residuals with the a<br />

priori variance (NORM APRIORI instead of NORMALIZED in option “Type of computed residuals”<br />

in panel “<strong>GPS</strong>EST 3.1: General Options 1”). We refer to Section 7.5.6 for more information.<br />

10.4.3 Program Output and Result File<br />

The results of the kinematic coordinate estimation are included in the <strong>GPS</strong>EST program<br />

output. An example is given in the left hand panel of Figure 10.6. The first line gives the<br />

a priori coordinates for the station (degrees, minutes, and seconds of arc for latitude and<br />

longitude, meters for height) as it is given in the input static coordinate file. For each epoch<br />

one line is printed containing the following information:<br />

EPO : Epoch number.<br />

EPOCH (MJD): Epoch of the kinematic position in modified Julian date.<br />

#OBS: Number of observations that contributed to the epoch parameter (observations<br />

from different baselines are counted separately).<br />

STA : First four characters of the station name.<br />

CORRECTION AND RMS IN METER:<br />

Estimated correction and formal error in north, east, and up components in meters.<br />

The corrections refer to the a priori coordinates used.<br />

ESTIMATED POSITION WRT. FIXED COORD.:<br />

Estimated trajectory in north, east, and up components in meters. The columns<br />

contain the difference between the position estimated for the particular epoch and<br />

the constant coordinate from the coordinate input file.<br />

The output for different kinematic stations is separated by a blank line.<br />

A minimum number of observations contributing to the kinematic position of an epoch can<br />

be defined in panel “<strong>GPS</strong>EST 6.5: Kinematic Coordinates”. If less observations are available the<br />

corresponding value is labeled with the flag S instead of flag K in the kinematic result file<br />

and is marked in the program output by an asterisk in the column containing the number<br />

of observations.<br />

The program output section looks slightly different for LEOs (see the right hand example<br />

in Figure 10.6). In that case only the estimated corrections in the X,Y,Z-components in the<br />

Earth-fixed system are printed together with their formal error.<br />

Page 228 AIUB

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

Saved successfully!

Ooh no, something went wrong!