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.

22.4 General Files<br />

• The satellite problem file invokes the handling of the following problems:<br />

(1) maneuver epochs (problem 0)<br />

(2) satellite modeling (problem 4)<br />

(3) time intervals with bad phase/code data for specific satellites (problems 1, 2, 3)<br />

• The first problem type (problem 0) is used to indicate satellite maneuvers. The processing<br />

programs read this file and use the orbit of satellite with number PRN before<br />

and PRN+50 after the maneuver epoch. The satellite with number PRN+50 is only<br />

present in the orbit files, but not in the observation files. ORBGEN treats the “new”<br />

satellite as any other satellite. For maneuvers the action number is always 0.<br />

• If the maneuver epoch is accurately determined, the data before and after the maneuver<br />

are usable without problems. Only a few observations around the maneuver<br />

epoch (a few to several minutes) may have to be deleted using problem type 3 (the<br />

residuals of MAUPRP may be used for a refinement of this time interval).<br />

• The problem type satellite modeling (problem 4) is used for long-arc computations<br />

using program ADDNEQ2 (”Menu>Processing>Normal equation stacking”). This problem type<br />

indicates to set up a new arc (action 0) for the specified satellite at the specified time<br />

(only NEQ boundaries are allowed).<br />

• The problem type bad satellite data (problems 1, 2, 3) is used to exclude data of a<br />

particular satellite from the processing. If you specify this file in RXOBV3 (”Menu>RINEX<br />

>Import RINEX to <strong>Bernese</strong> format>Observation files”) you have the possibility to transfer them<br />

to the <strong>Bernese</strong> formats as marked observations (action item 1) or to remove them<br />

(action item 2; not transferred to the <strong>Bernese</strong>-specific format). The remove action is<br />

supported only in program RXOBV3. If observations for a satellite are not removed,<br />

orbit information has to be available for the processing.<br />

• For program CODSPP (”Menu>Processing>Code-based clock synchronization”) the presence of this<br />

file means not to use the pseudorange data (problem 2 or 3, action 1) for the estimation<br />

of the receiver clock corrections. In some cases the pseudorange observations of a<br />

certain satellite are bad, but the corresponding phase observations are good. However,<br />

it may be better to mark both, pseudorange and phase observations, to avoid problems<br />

in the next processing steps.<br />

• Using this file in the program MAUPRP (”Menu>Processing>Phase preprocessing”) means that<br />

the phase data are marked (problem 1 or 3, action 1).<br />

• If you use the file in the program <strong>GPS</strong>EST (”Menu>Processing>Parameter estimation”) you<br />

exclude the corresponding observations from the parameter estimation automatically.<br />

The satellite problem file thus represents an easy way to exclude (and include again)<br />

observations of individual satellites from the processing without marking them in the<br />

observation files with program SATMRK (”Menu>Service><strong>Bernese</strong> observation files>Mark/delete<br />

observations”).<br />

• The file may be updated by DEFXTR (inserting arc splittings) and RESCHK (adding<br />

intervals for bad satellite data).<br />

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

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

Saved successfully!

Ooh no, something went wrong!