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.

9.3.9 Constraining of Parameters<br />

9.3 Manipulation of Normal Equations<br />

The old program ADDNEQ used the constraining technique rather extensively for almost<br />

every parameter manipulation. To avoid numerical problems inherent in this approach,<br />

ADDNEQ2 is based on parameter transformation instead of constraining technique wherever<br />

possible. However, there are still quite a few situations where the constraining technique<br />

has to be used or where a transformation is too complicated.<br />

In the <strong>Bernese</strong> <strong>GPS</strong> <strong>Software</strong> the constraining of parameters is performed by adding fictitious<br />

observations. The principles in ADDNEQ2 are the same as in <strong>GPS</strong>EST and are described<br />

in Section 7.5.4. Nearly all parameters supported by ADDNEQ2 can be constrained. Relative<br />

constraints (between successive parameters in time) may be applied for tropospheric zenith<br />

path delay and gradient parameters as well as for global ionosphere parameters. A time interval<br />

must be defined specifying the distance in time over which relative constraints shall act<br />

(usually the nominal parameter spacing). Furthermore, relative constraints may be put to<br />

pairs of station coordinates and/or velocities according to the entries in Section TYPE 004:<br />

STATION COORDINATES AND VELOCITIES (ADDNEQ) of the station information file (see Section<br />

10.3.5 for more details).<br />

Parameters are constrained after parameter transformations took place. Parameters that<br />

are pre-eliminated before stacking are constrained before pre-elimination. Parameters that<br />

explicitly appear in the resulting normal equation are stored to file without any constraints in<br />

order to avoid numerical problems. SINEX files generated by ADDNEQ2 have all constraints<br />

of explicit parameters booked in the MATRIX/APRIORI block.<br />

Station coordinates and velocities may be fixed (and deleted from the normal equation, not<br />

recommended if saving normal equations or estimating velocities) or constrained to their<br />

a priori values which are provided by input coordinate resp. velocity files. A free solution,<br />

without any constraint on the station coordinates resp. velocities may be generated (not<br />

recommended), or minimum network constraints may be imposed, see following section.<br />

Minimum Constraint Conditions<br />

<strong>GNSS</strong> is in principle an interferometric technique. Therefore it is in general not possible<br />

to estimate the absolute position of all stations. Some of them (at least one) have to be<br />

kept fixed on their a priori positions or so-called free network conditions have to be introduced.<br />

Free network conditions (or minimum constraint conditions) are optimal to define<br />

the geodetic datum with a minimum number of constraints, without fixing or constraining<br />

particular site coordinates. This option is well-suited to analyze inconsistencies in the<br />

reference site coordinates, see also Chapter 10.<br />

Free network conditions are based on the assumption that there are two reference frames<br />

(1) an a priori reference frame, and<br />

(2) the reference frame of the resulting coordinates.<br />

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

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

Saved successfully!

Ooh no, something went wrong!