The GNSS integer ambiguities: estimation and validation
The GNSS integer ambiguities: estimation and validation
The GNSS integer ambiguities: estimation and validation
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
2<br />
1.5<br />
1<br />
0.5<br />
0<br />
−0.5<br />
−1<br />
−1.5<br />
−2<br />
−2 −1.5 −1 −0.5 0 0.5 1 1.5 2<br />
Figure 3.3: Two-dimensional pull-in regions in the case of rounding.<br />
Examples of <strong>integer</strong> estimators that belong to the class of admissible <strong>integer</strong> estimators<br />
are <strong>integer</strong> rounding (R), <strong>integer</strong> bootstrapping (B), <strong>and</strong> <strong>integer</strong> least-squares (ILS).<br />
Each of these estimators will be described briefly in the following sections.<br />
3.1.1 Integer rounding<br />
<strong>The</strong> simplest way to obtain an <strong>integer</strong> vector from the real-valued float solution is to<br />
round each entry of â to its nearest <strong>integer</strong>. <strong>The</strong> corresponding <strong>integer</strong> estimator, ǎR,<br />
reads then:<br />
ǎR =<br />
⎛ ⎞<br />
[â1]<br />
⎜<br />
⎝ .<br />
⎟<br />
. ⎠ (3.8)<br />
[ân]<br />
where [·] denotes rounding to the nearest <strong>integer</strong>. It can be easily shown that this<br />
estimator is admissible, see Teunissen (1999a).<br />
Since each component of the real-valued ambiguity vector is rounded to the nearest<br />
<strong>integer</strong>, the absolute value of the maximum difference between the float <strong>and</strong> fixed ambi-<br />
guities is 1<br />
2 . <strong>The</strong> pull-in region Sz,R that corresponds to this <strong>integer</strong> estimator is therefore<br />
given as:<br />
Sz,R =<br />
n<br />
i=1<br />
<br />
x ∈ R n | |xi − zi| ≤ 1<br />
<br />
, ∀z ∈ Z<br />
2<br />
n<br />
(3.9)<br />
So, the pull-in regions are the n-dimensional unit cubes centered at z ∈ Z n . For the<br />
two-dimensional case this is visualized in figure 3.3.<br />
30 Integer ambiguity resolution