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.

20.4 Description of the Processing Examples<br />

20.4.2.5 Compute Ambiguity-Float Network Solution, Resolve Phase Ambiguities<br />

The next processing steps are dedicated to ambiguity resolution. After computing a solution<br />

with real valued ambiguities the QIF (quasi-ionosphere-free) strategy is used to resolve<br />

ambiguities to their integer numbers.<br />

#<br />

# Compute ambiguity-float network solution, resolve phase ambiguities<br />

# -------------------------------------------------------------------<br />

401 ADDNEQ2 R2S_GEN ANY 1 331<br />

402 <strong>GPS</strong>XTR R2S_GEN ANY 1 401<br />

411 <strong>GPS</strong>QIFAP R2S_QIF ANY 1 402<br />

412 <strong>GPS</strong>QIF_P R2S_QIF ANY 1 411<br />

413 <strong>GPS</strong>XTR R2S_QIF ANY 1 412<br />

PID 401 ADDNEQ2: A network solution with real valued ambiguities is computed baed<br />

on normal equations stored in the <strong>GPS</strong>EST after the residual screening (PID 322).<br />

Coordinates and troposphere estimates are saved for further use in the ambiguity<br />

resolution step.<br />

PID 402 <strong>GPS</strong>XTR: Creates a short overview of the float solution. It is included in the processing<br />

summary (solution name P1 yyssss). The a posteriori rms error should be<br />

not higher than about 1.4 mm.<br />

PID 411 <strong>GPS</strong>QIFAP: Prepares the parallel execution of the ambiguity resolution steps. Program<br />

BASLST is used to select baselines up to a maximum length of 2000 km. Only for<br />

these baselines ambiguity resolution is attempted. This restriction is imposed because<br />

for very long baselines the QIF resolution success rate drops and the probability of<br />

wrongly resolved ambiguities rises. Please note that there are no baselines longer than<br />

2000 km in this example campaign, however.<br />

PID 412 <strong>GPS</strong>QIF P: One <strong>GPS</strong>EST is started for each baseline to be processed. Troposphere<br />

estimates and coordinates from the float solution (PID 401) are introduced and fixed.<br />

L1&L2 ambiguities are resolved simultaneously using the QIF strategy and are stored<br />

in the observation header files.<br />

PID 413 <strong>GPS</strong>XTR: Creates a summary of the previous step, listing, e.g., the percentage of<br />

successfully resolved ambiguities. On the average, about 70% of ambiguities are resolved.<br />

Note when processing your own data: On long baselines, large rms values for the<br />

ambiguity float and fixed solutions do not necessarily indicate a problem, see Section<br />

8.3.4.2.<br />

Please note that the ambiguity resolution (<strong>GPS</strong>EST) runs baseline by baseline, independent<br />

from the settings in variable V CLU . This is necessary due to the vast amount of stochastic<br />

ionosphere parameters needed for the QIF strategy. Otherwise memory problems may arise.<br />

Of course it is possible to use a different strategy or to include additional steps to resolve<br />

remaining ambiguities based on other resolution strategies. Selection of the proper strategy<br />

mainly depends on available observation data and network layout.<br />

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

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

Saved successfully!

Ooh no, something went wrong!