Difference between revisions of "GPS analysis system"
(→Cleaning Solutions) |
|||
Line 20: | Line 20: | ||
===Cleaning Solutions=== | ===Cleaning Solutions=== | ||
+ | |||
+ | Initial Explanation of terms | ||
+ | |||
+ | Expected residuals from a clean solution | ||
+ | |||
+ | Automated screening: postfit, the point file, postbreak | ||
+ | |||
+ | Checking for bad pseudorange data: badp, allbadp | ||
+ | |||
+ | Removing biased pseudorange data: del_pcode_arc | ||
+ | |||
+ | Automatically identified cycle slips: breaks | ||
+ | |||
+ | Quickly scanning through residuals: short_hand | ||
+ | |||
+ | Limitations of short_hand | ||
+ | |||
+ | Manually checking residuals and fixing problems (link) |
Revision as of 13:30, 20 May 2006
We use a GPS data analysis system based on the GIPSY software developed at JPL. Most of the GIPSY programs are called by shell scripts written by Jeff Freymueller. Using these scripts, we can analyze a large amount of data either as part of network solutions or in Precise Point Positioning (PPP) mode.
Contents
Where do you put RINEX files?
RINEX files should be put into the hopper, $RAWDATA/hopper
. What, you don't have RINEX files yet? See RINEXing. Once files are in the hopper, you can either let the first processing stages happen automatically overnight (see next section), or run the autofront
and autoclean
programs manually.
What happens automatically?
Autoftp
Autofront
Autoclean
Where do the data files go?
Data files from each station are stored in the QM format that is native to GIPSY. QM files (and all other) files are stored in directories by GPS week. For each week directory there are several subdirectories; qm files are stored in $ANALYSIS/wwww/qm
, where wwww
is the 4 character GPS week number (with a leading zero if needed).
Running Solutions
Cleaning Solutions
Initial Explanation of terms
Expected residuals from a clean solution
Automated screening: postfit, the point file, postbreak
Checking for bad pseudorange data: badp, allbadp
Removing biased pseudorange data: del_pcode_arc
Automatically identified cycle slips: breaks
Quickly scanning through residuals: short_hand
Limitations of short_hand
Manually checking residuals and fixing problems (link)