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. Processing Examples<br />

PID 321 <strong>GPS</strong>EDTAP: It is preferable to have all baselines containing one kinematic station<br />

in the same cluster. Otherwise the kinematic positions are independently estimated<br />

in <strong>GPS</strong>EST.<br />

PID 322 <strong>GPS</strong>EDT P:<br />

• Introduce the a priori kinematic coordinates file from PPP.<br />

• Adapt the “Sampling interval”.<br />

• Enable the estimation of “Kinematic coordinates” and set the “Pre-Elimination” to<br />

EVERY EPOCH.<br />

• Kinematic coordinate estimation is not necessary in the first <strong>GPS</strong>EST run if<br />

the a priori values from the PPP analysis are already very good. But kinematic<br />

positioning must be enabled at least in the second run (using the $bpe->putKey();<br />

mechanism).<br />

• Set the “Type of computed residuals” in panel to NORM APRIORI.<br />

(Var-covar information for non-epoch parameters is not available when preeliminating<br />

kinematic positions every epoch since the “Var-covar wrt epoch parameters”<br />

is computed SIMPLIFIED)<br />

• Select the kinematic station in panel “<strong>GPS</strong>EST 6.5: Kinematic Coordinates”<br />

• Constrain the solution to the a priori kinematic coordinates according to the<br />

already achieved accuracy by specifying “A PRIORI SIGMAS” in panel “<strong>GPS</strong>EST 6.5:<br />

Kinematic Coordinates”.<br />

PID 401 ADDNEQ2:<br />

• The normal equation files written by the second run of the program <strong>GPS</strong>EST<br />

contain no kinematic position parameters (because of the huge number) but the<br />

static coordinate parameters for all remaining sites. In addition the troposphere<br />

parameters for all stations are included. ADDNEQ2 will generate coordinate and<br />

troposphere result files but cannot update the kinematic coordinates file.<br />

• Add another <strong>GPS</strong>EST (e.g., as PID 403) to update the kinematic coordinates file.<br />

Introduce the coordinate and troposphere result files from ADDNEQ2. Set option<br />

“Coordinates fixed” in panel “<strong>GPS</strong>EST 4: Datum Definition for Station Coordinates” to<br />

WITH FLAG. In the next panel, select # (any non–blank flag) for “Stations with specific<br />

flags in CRD file”. Now all static stations are fixed on their a priori coordinates.<br />

Setup troposphere as in PID 322, and set option “STATIONS TO BE EXCLUDED<br />

FROM TROPOSPHERE ESTIMATION” “Station selection” to WITH TROPO.<br />

• Adapt the “Sampling interval”.<br />

• Enable the estimation of “Kinematic coordinates” and set the “Pre-Elimination” to<br />

EVERY EPOCH.<br />

• Select the kinematic station in panel “<strong>GPS</strong>EST 6.5: Kinematic Coordinates”<br />

• Constrain the solution to the a priori kinematic coordinates according to the<br />

already achieved accuracy by specifying corresponding “A PRIORI SIGMAS”.<br />

• Save the results in a kinematic coordinates file.<br />

Page 462 AIUB

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

Saved successfully!

Ooh no, something went wrong!