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.

7.4 Weighting and Correlations<br />

The normalized residuals (option “Type of computed residuals” in panel “<strong>GPS</strong>EST 3.1”) are<br />

residuals divided by the square root of the diagonal element of the cofactor matrix of the<br />

residuals<br />

vnorm(i) = v(i)<br />

. (7.15)<br />

Dii(v)<br />

The cofactor matrix of the residuals is the difference between the inverse weighting matrix<br />

of the actual observations and the cofactor matrix of the adjusted observations<br />

with<br />

D(v) = P −1 − D(y) (7.16)<br />

D(y) = A(A ⊤ P A) −1 A ⊤ . (7.17)<br />

In contrast to real residuals, normalized (phase as well as code) residuals are always converted<br />

to one-way L1 carrier phase residuals, i.e., if you divide these residuals by the a<br />

posteriori sigma of unit weight, you should get random variables with a standard deviation<br />

of 1. For reliable outlier detection using program RESRMS when analyzing low-elevation<br />

data, applying an elevation-dependent observation weighting model or introducing stationspecific<br />

weights, it is recommended to save normalized residuals. Be aware that, e.g., a real<br />

double-difference L3 carrier phase residual of 36 mm corresponds to a normalized (one-way<br />

L1-)residual of 6 mm – assuming that no elevation- or station-specific weighting took place.<br />

A special option NORM APRIORI is available for conversion of real residuals into normalized<br />

residuals using the a priori variance of observations<br />

D(v) ≃ P −1<br />

. (7.18)<br />

This option may be useful if epoch parameters are present which are pre-eliminated epochwise<br />

and back-substituted in a final step (see Sections 7.5.5 and 7.5.6). If the option “Varcovar<br />

wrt epoch parameters” is set to SIMPLIFIED to speed up the back-substitution the matrix<br />

A ⊤ P A in Eqn. (7.17) only refers to the epoch parameters. As a consequence, residuals of<br />

observations not contributing to epoch parameters are normalized differently than those of<br />

observations that do contribute if option NORMALIZED is used and the residuals would not<br />

be comparable.<br />

If residuals are requested by specifying a residual output file in panel “<strong>GPS</strong>EST 2.1: Output<br />

Files 1” the observation equations, i.e., the design matrix A and the observation vector<br />

y are saved to a binary scratch file while processing each observation and accumulating<br />

the normal equation matrix A ⊤ PA. After solving the normal equation the scratch file is<br />

read and the adjusted residuals are computed according to Eqn. (7.2). As a matter of fact,<br />

residuals can only be computed if all parameters are solved for. No parameter, not even<br />

ambiguity parameters may be pre-eliminated before residuals are computed. The exception<br />

are epoch parameters such as clock corrections or kinematic coordinates which are handled<br />

in a special way (see Section 7.5.3). Parameters may, however, be pre-eliminated using the<br />

option PRIOR TO NEQ SAVING (see Section 7.5.5) if they should not appear in the normal<br />

equation saved for later use in ADDNEQ2 (see Chapter 9). This is particularly important<br />

for ambiguity parameters which are not supported by ADDNEQ2: Saving a residual file<br />

and a normal equation file in the same run is only possible if ambiguity parameters are<br />

pre-eliminated with option PRIOR TO NEQ SAVING.<br />

<strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> <strong>Version</strong> <strong>5.0</strong> Page 145

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

Saved successfully!

Ooh no, something went wrong!