http://gps.alaska.edu/internal/api.php?action=feedcontributions&feedformat=atom&user=JeffGeodesyLab - User contributions [en]2026-04-18T14:15:01ZUser contributionsMediaWiki 1.25.1http://gps.alaska.edu/internal/index.php?title=Kinematic_Processing&diff=2896Kinematic Processing2013-10-24T17:30:06Z<p>Jeff: </p>
<hr />
<div>==Workflow==<br />
<ul><br />
<li>define subnet file (including clock site, a couple of non-kinematically estimated sites, at the ones you are really interested in)</li><br />
<li>define namelist (nml) file (RANDOM-WALK!), at best put them into /home/akda/Kinematic . That's also were examples live</li><br />
<li>adapt script that calls solve (check whether you need a rapid solution -- when orbits aren't in yet)</li><br />
<li>run solution</li><br />
<li>extract data from .trop files</li><br />
<li>plot results.</li><br />
</ul><br />
<br />
==Temporal Resolution below 5 min==<br />
The standard solutions run with a temporal solution of 5 minutes (6 minutes if older than 1995). This means the standard qm files do not contain enough information if you need a finer resolution. Here is what to do:<br />
<ul><br />
<li>create campaign directory: <code>newcamp /gps/data/CAMPAIGN_NAME-interval</code></li><br />
<li>create qm files for all rinex files from sites that go into that campaign for respective time:<br/><br />
<center><br />
<code><br />
rnx2qm RINEX-file -dir $procdir -interval 30<br />
<br />
or<br />
<br />
reprocess_rinex station-name start-day end-day rinexdir outdir interval<br />
</code><br />
</center><br />
where $procdir=/gps/data/CAMPAIGN_NAME-interval, i.e. the campaign directory you just created.<br />
</li><br />
<li>copy the orbits for the repective day(s) into /gps/data/CAMPAIGN_NAME-interval/orbit</li><br />
<li>add the <code>-nosvclkfile</code> flag to your <code>solve</code> call, to make sure the satellite clocks are not used ...</li><br />
<li>or get high resolution clocks for the respective days from [ftp://sideshow.jpl.nasa.gov/pub/gipsy_products/hrclocks/ ftp://sideshow.jpl.nasa.gov/pub/gipsy_products/hrclocks/] and copy those into /gps/data/CAMPAIGN_NAME-interval/orbit </li><br />
<li>if you got the high resolution orbits, make sure to rename them: mv *.tdp *.tdpc </li><br />
<li>make sure to update the $CAMP variable in the make-xxxxx file that you copy into your /gps/data/CAMPAIGN_NAME-interval/flt directory</li><br />
</ul><br />
<br />
==Standard/Automated Processing for Kinematic PPP Solutions==<br />
<br />
There are some new scripts available to make it quick and easy to do high rate static and kinematic<br />
solutions. These implement a standard solution using 1 sample per second data, and using the 3.0<br />
solution strategy otherwise.<br />
<br />
<ol><br />
<li>Create a new campaign directory using the <code>newcamp</code> script. Copy the orbit files<br />
you will need for whatever days you are processing. Also, collect the 1 sample per second rinex files<br />
in some directory (not in the campaign data structure).</li><br />
<li>Run the script <code>f-e.kinematic</code> to create 1 sample per second qm files. The full command line is<br />
<code>f-e.kinematic rinexdir [campdir]</code>. The first argument is the directory where your<br />
rinex files (compressed .Z or .gz files) are, and the optional second directory is the<br />
top-level campaign directory (default is <code>$CAMP</code>).</li><br />
<li>You will need to check the data for cycle slips and other problems using a high-rate static<br />
solution. Run the script <code>make_static_pppsolve_script</code> in <code>$CAMP/flt</code><br />
to make a script that will generate a script to run such a solution for all qm files. You may<br />
want to edit the resulting script <code>make-static</code> to add lines defining the $CAMP<br />
variable so that you can run it more automatically.</li><br />
<li>Check the residuals, add ambiguity parameters as needed. Same as a regular solution.</li><br />
<li>Run PPP solutions for all stations using the script <code>run_3.0_kinematic_solution</code>.<br />
Full syntax is <code>run_3.0_kinematic_solution -date yymmmdd [-update]</code>. The script<br />
will run all qm files for that date, putting the solutions in the sub-directory PPP3.0kin.<br />
The time-depenent parameter files (TDP files) are in the $CAMP/trop directory. With the -update flag,<br />
the script will only run qm files that have not been run before.</li><br />
<li>Extract the time-dependent solutions for each station and make SAC files using the script<br />
<trop2enu>. Give it the .trop file as an argument, and it will create corresponding .enu and .SAC files.</li><br />
</ol><br />
<br />
==Defining Custom Solution Parameters==<br />
Use an NML file to define the solution parameters. Here is an example to start with.<br />
<br />
$PREP !namelist input for preprefilter <br />
! reference clock is REQUIRED. you need to use one of <br />
! your sites, generally one with a stable clock. Mostly<br />
! it means anything except a trimble. If an external<br />
! oscillator is used, then it can be a reference clock.<br />
REFCLOCK = 'THU1' <br />
! just says whether the troposphere will be estimated stochastically.<br />
! except for very short baselines, this is always true.<br />
WETZTROP = .TRUE. <br />
! This is the white noise sigma applied to phase ambiguity parameters <br />
! whenever a new ambiguity needs to be estimated (.1 seems to work).<br />
yaddsg = 0.1<br />
! this is the random walk constraint for the troposphere, in km/sqrt(sec)<br />
TROPDRIFT = 1.70D-7 <br />
! if you want to estimate additional paraetmeters stochastically, you<br />
! put them here. You don't have to put clocks here, because GIPSY<br />
! assumes that all clocks will be estimated stochastically.<br />
SSTCH = 'STA E SCOB','STA N SCOB', 'STA V SCOB'<br />
! in this example they are the east, north, and vertical components <br />
! for station SCOB. Generally station locations are not<br />
! estimated stochastically<br />
! This tells you how to constrain the parameters you named above.<br />
SPSIG = 3*1.0D-6, ! random walk constraint<br />
SMTAU = 3*'RANDOMWALK', <br />
! how often do you want to estimate these stochastic parameters<br />
SDELT = 3*'/00:05', ! compute a position every 5 minutes <br />
<br />
<br />
$END <br />
<br />
<br />
$INIT !namelist input for filter <br />
YDEL(1) = 'STABIAS THU1' ! same for the reference clock<br />
! STABIAS is the GIPSY name for a station clock. SATBIAS is <br />
! for a satellite clock<br />
<br />
! this is if you are estimating station positions stochastically.<br />
! just do it.<br />
grounddelete = 'SCOB',<br />
STAINT = .FALSE. <br />
IDIGIT = 9 <br />
<br />
! this is a list of all the parameters you DO NOT <br />
! want GIPSY to estimate. look at the cartoon book<br />
! for more info. X, Y, Z, DX, DY, DZare the satellite orbits.<br />
! you don't want to estimate them if youare using someone<br />
! else's orbits, which I would assume you are all going to do<br />
YDEL(2) = 'UT1-UTC', 'UT1-UTC RATE', 'X POLE *', 'Y POLE *', <br />
'GEOCENTER*', 'V LOVE', 'H LOVE', 'DRYZTROP*', <br />
'LMPZTROP*', 'STA DRFT*', 'STA ACCL*', 'SAT DRFT*', <br />
'SAT ACCL*', 'BIASPSR*', 'SOLARSCLTOP*','Y_BIAS TOP*', <br />
'XPOLEMOTION','XPOLERATE','YPOLEMOTION','YPOLERATE', <br />
'X*', 'Y*', 'Z*', 'DX*', 'DY*', 'DZ*','TRPAZ*', <br />
'SOLSCL_X*', 'Y_BIAS*', 'SOLSCL_Z*', 'SOLARSCL*'<br />
<br />
SOLPRT = .TRUE. <br />
NOMEAS = .FALSE. <br />
SOLVE = .TRUE. <br />
DEBUG = 1 <br />
OUTNAME = 'OASIS' <br />
$END <br />
<br />
$APRIORI !namelist input for filter <br />
APALL = .TRUE. <br />
! The following are NOT currently estimated <br />
! <br />
! Parameters actually estimated start here <br />
! <br />
APNAMS( 1) = 'WETZTROP*', APSIGS( 1) = 10.0D-5 !10 cm <br />
APNAMS( 2) = 'STABIAS*', APSIGS( 2) = 3.0D5 !1 sec <br />
APNAMS( 3) = 'SATBIAS*', APSIGS( 3) = 3.0D5 !1 sec <br />
APNAMS( 4) = 'PHASE*', APSIGS( 4) = 1.0D-1 !1 micr<br />
! I am using ENV here, but you should set these for XYZ if you are doing<br />
! it in the Cartesian frame<br />
APNAMS( 5) = 'STAE*', APSIGS( 5) = 1. !1 km<br />
APNAMS( 6) = 'STAN*', APSIGS( 6) = 1. !1 km<br />
APNAMS( 7) = 'STAV*', APSIGS( 7) = 1. !1 km<br />
APNAMS( 8) = 'STA E KOKB', APSIGS( 8) = 10.0D-3 !10 m<br />
APNAMS( 9) = 'STA N KOKB', APSIGS( 9) = 10.0D-3 !10 m<br />
APNAMS(10) = 'STA V KOKB', APSIGS(10) = 10.0D-3 !10 m<br />
<br />
<br />
<br />
<br />
$END <br />
<br />
$DATAWGHT !namelist input for filter, edtpnt2, and post<br />
ELMINSTA = 15.0D0 ! elevation angle minimum <br />
! 110 is pseudorange, 120 is phase<br />
DATYPE = 110, 120, <br />
DATSIG = 1.0D-3, 1.0D-5, ! these are in km<br />
XRECNM(1) = 'HOLE' ! this is to delete a specific receiver<br />
XXMTNM(1) = 'GPS04' ! this is to delete a specific satellite<br />
$END <br />
<br />
$SMINPUT !namelist input for smapper <br />
SAVEUD = 'LAST' <br />
SAVESIGMA = .TRUE. <br />
IDIGIT = 9 <br />
MAPTYP = 'CARTESIAN'<br />
OUTNAME = 'OASIS' <br />
TDPFULLPRECISION = .TRUE.<br />
! write out these parameters for stochastic parameters<br />
! GIPSY only creates this file if asked for (it is a TDP<br />
! - time-dependent-parameter file). If you want to know<br />
! clock values, then you need to write their names here.<br />
WRTTDP = 'STA E SCOB', 'STA N SCOB', 'STA V SCOB',<br />
TDPTYP = 'TIMEVARY',<br />
TDPTOL = 1.0d00,<br />
STAINT = .FALSE. <br />
$END <br />
<br />
$APRIORINML !namelist input for smapper <br />
$END <br />
<br />
<br />
$LIMITS !namelist input for postfit <br />
! outlier criterion, i.e. flag all phase data greater than 5 cm.<br />
STAINT = .FALSE. <br />
DATYPE = 120 <br />
WINDOW = 5.0D-5, <br />
$END <br />
<br />
$EDTINIT !namelist input for edtpnt2 <br />
STAINT = .FALSE. <br />
DEBUG = .TRUE. <br />
$END</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=GPS_analysis_system&diff=2895GPS analysis system2013-10-24T17:07:07Z<p>Jeff: </p>
<hr />
<div>We use a GPS data analysis system based on the [http://sideshow.jpl.nasa.gov GIPSY] software developed at JPL. Most of the GIPSY programs are called by [[Special:Call/Include_info%2C/export/ftpweb/htdocs/sh2doc/index.html | 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.<br />
<br />
===Documentation of Solution Strategies (new)===<br />
The links below describe our solution strategy as it has evolved over time.<br />
{|<br />
|[[Solution_Strategy_1.0 | 1.0 1990s strategy.]]<br />
|-<br />
|[[Solution_Strategy_2.0 | 2.0 Network solutions used from ~2002 through 2008.]]<br />
|-<br />
|[[Solution_Strategy_2.5 | 2.5 PPP solutions but otherwise strategy 2.0]]<br />
|-<br />
|[[Solution_Strategy_3.0 | 3.0 2010 new solution strategy]]<br />
|}<br />
<br />
===Where do you put RINEX files?===<br />
RINEX files should be put into the hopper, <code>$RAWDATA/hopper</code>. 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 <code>autofront</code> and <code>autoclean</code> programs manually.<br />
<br />
===What happens automatically?===<br />
<br />
Quite a lot.<br />
<br />
Autoftp runs every night beginning at 6pm local time and fetches data files. These are placed into the '''hopper''' ($RAWDATA/hopper), a directory where all data files are put for entry into the system and processing. Autofront then runs at midnight to process all files in the hopper, including any placed there manually (from campaigns, for example). Finally, autoclean runs at 4am local to carry out automated screening for cycle slips and other bad data.<br />
<br />
====Autoftp====<br />
<br />
Autoftp is an efficient data-fetching tool that uses wget to automatically get data from any of several internet GPS data archives. It reads a list of desired sites from a ''request file'', which contains the date in the filename, and attempts to find and download data from as many sites as possible. It is intended to run automatically on a daily basis under cron, and when acccompanied by another simple program to generate a standard request file every day, it can easily fetch a standard set of sites on a daily basis for analysis. Because it keeps track in the request file of sites that it has found already, autoftp can be run multiple times with the same request file and it will not repeatedly fetch data. This is ideal for the real world, in which data from some sites are available rapidly while data from other sites may require many hours or days to become available.<br />
<br />
====Autofront====<br />
<br />
Autofront is a script intended to run under cron that carried out the initial "front end" processing on a set of GPS data files. When executed, it will process all files in the '''hopper''' directory, and will place each resulting qm file into the appropriate week directory.<br />
<br />
Autofront runs the following steps<br />
1. Checks on the validity of RINEX file and repair of some common problems.<br />
2. Depending on receiver type, clockprep -fixtags<br />
3. (optional, presently not default) PhasEdit<br />
4. ninja<br />
<br />
====Autoclean====<br />
<br />
Autoclean carries out automated cleaning of cycle slips, based on point positioning solutions. It is quite effective and at present it rarely misses cycle slips unless they are smaller than its minimum tolerance (10 cm). Autoclean operates on an ''edit-request'' file, which contains the name of the directory (week directory) and a list of qm files that need to be cleaned. It will clean all files on the list as long as orbits and clocks are available, and it marks off files that have been cleaned so that it can safely be run multiple times.<br />
<br />
Autoclean operates in an iterative mode. It's zeroth iteration is to do a pseudorange-only solution and identify and delete extremely bad pseudorange data. In this step it uses a tolerance that catches only grossly biased data. (Explain it). It then carries out 1 or more iterations of screening the phase data. In each iteration, it uses postbreak to identify discontinuities in the residuals of a point positioning solution. Postbreak is run with an adaptive tolerance (minimum 10 cm), and it is critical that my slightly modified version of postbreak be used. If any cycle slips are discovered, they are flagged and another iteration is run. Autoclean runs a maximum of 4 iterations on the phase data.<br />
<br />
===Where do the data files go?===<br />
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|week directory]] there are several [[subdirectories]]; qm files are stored in <code>$ANALYSIS/wwww/qm</code>, where <code>wwww</code> is the 4 character GPS week number (with a leading zero if needed).<br />
<br />
===Running Static Solutions===<br />
In the [[subdirectories|flt]] directory for each [[week directory|week]] there will (hopefully) be a UNIX script called<br><br />
''make-*''<br><br />
This script runs another script called<br><br />
''standard_*_solution''<br><br />
which again runs another script called<br><br />
''solve''<br><br />
for each [[subnets | network of stations]] (see each subnet with [[Subnets_GoogleEarth | Google Earth]]) for each day. The solve script runs solutions for each of these networks based on the data from sites in the network that are available in the qm directory.<br />
<br />
To run solutions, copy the ''make'' script to a file called ''make-flt'' (for example).<br />
<br />
Check that the ''make-flt'' script contains all the days that you want to run.<br />
<br />
Check which [[Linux Computer System | computer]] is free to run the script (to do so, type:)<br />
check-solves<br />
log on to a free computer and type<br />
submit make-flt<br />
<br />
As the script runs, files will appear in the [[subdirectories|flt]] directory for each [[subnets|network]] for each day. Usually<br />
this script will have been run once [[#What happens automatically? | automatically]], so there will often already be files in the [[subdirectories|flt]]<br />
directory ready to be cleaned and then re-run.<br />
<br />
<br />
Solve, a very flexible script. (link to detailed help)<br />
<br />
Philosophy of solve<br />
<br />
Subnet files and campaign files<br />
<br />
Standard solutions<br />
<br />
(text of standard_Alaska_solution)<br />
<br />
Running several days at once: make-make-flt and make-alaska<br />
<br />
(text of a standard make-alaska file and variant)<br />
<br />
Running several weeks at once<br />
<br />
(text of sample rerun-* file)<br />
<br />
===Cleaning Static Solutions===<br />
<br />
Sometimes bad data (outliers and cycle slips) make it past the automatic editors. When this<br />
happens the bad data are removed from the qm files by either deleting points or by inserting<br />
new phase ambiguities to deal with cycle slips. The steps, commands and scrips to use are somewhat explained [[How to clean a solution? | here]]. Once the data are cleaned, the files should be deleted from the [[subdirectories|flt]] directory and the solutions re-run (run <code>make-flt</code> again). Usually you will have to go through 2-3<br />
iterations of the cleaning-rerunning cycle. To be clean, the .point files for a solution do not<br />
exist or are small (below 1000 bytes). Once a solution is clean the files should remain in<br />
the [[subdirectories|flt]] directory and the lines to rerun that solution should be deleted from the <code>make-flt</code> file.<br />
<br />
Initial Explanation of terms<br />
<br />
Expected residuals from a clean solution<br />
<br />
Automated screening: postfit, the point file, postbreak<br />
<br />
Checking for bad pseudorange data: badp, [[How to clean a solution?|allbadp]]<br />
<br />
Removing biased pseudorange data: [[How to clean a solution?|del_pcode_arc]]<br />
<br />
Automatically identified cycle slips: breaks, [[How to clean a solution?|allbreaks]]<br />
<br />
Quickly scanning through residuals: short_hand<br><br />
The data problems can be identified and<br />
fixed using the program<br />
[[short_hand]] <br />
(follow the link to read about and ask for help to get started with this program).<br> <br />
Limitations of short_hand<br />
<br />
Manually checking residuals and fixing [[problem stations | problems]]<br />
<br />
===Procedure for Running Solutions for a week for the first time===<br />
<br />
A few special things need to be done the very first time solutions in a week are run. First, you need to make up a script to run all days of the week. This may need to be edited if the JPL final orbits are not available at the time. The <code>standard_Alaska_solution</code> uses the non-fiducial orbits and thus requires that the final JPL orbits be present. If they are not, you can run <code>rapid_Alaska_solution</code> instead. <br />
<br />
Then, the log files from autoclean should be moved away to a subdirectory, and any problem stations identified by autoclean should be checked. Then, you are ready to run the solutions.<br />
<br />
First, make a script to run solutions. For example, to make a script to run all days of the week for the Alaska solution:<br />
<pre><br />
cd $ANALYSIS<br />
make-make-flt 1381<br />
cd 1381/flt<br />
vi make-alaska<br />
# Edit the file if needed so that you are ready to run the rapid solutions.<br />
<br />
cat make-alaska<br />
#!/bin/csh -f<br />
#<br />
setenv CAMP $ANALYSIS/1381<br />
#<br />
#standard_Alaska_solution 06jul01<br />
#standard_Alaska_solution 06jun25<br />
#standard_Alaska_solution 06jun26<br />
#standard_Alaska_solution 06jun27<br />
#standard_Alaska_solution 06jun28<br />
#standard_Alaska_solution 06jun29<br />
#standard_Alaska_solution 06jun30<br />
#<br />
rapid_Alaska_solution 06jul01<br />
rapid_Alaska_solution 06jun25<br />
rapid_Alaska_solution 06jun26<br />
rapid_Alaska_solution 06jun27<br />
rapid_Alaska_solution 06jun28<br />
rapid_Alaska_solution 06jun29<br />
rapid_Alaska_solution 06jun30<br />
<br />
</pre><br />
<br />
The script <code>make-make-flt</code> finds all unique dates for qm files in that week's directory, and uses that to generate the script, so if you run it before the end of the week you will get a partial script. If the final JPL orbits are not yet present, you will need to edit the script to change "standard" ro "rapid". Or better yet, copy all the lines and comment one set out, then modify the others to read "rapid_Alaska_solution <date>".<br />
<br />
Next call <code>mv_logfiles</code> (being in the WEEK/flt directory!) which creates a subdirectory called <code>logfiles</code> and moves <br />
all of autoclean's logfiles of the format <code>*____*.i*</code> into this directory:<br />
<br />
<pre><br />
HOSTNAME WWWW/flt> mv_logfiles<br />
</pre><br />
<br />
Now look for a file called <code>make-problems</code>, which lists all files that autoclean had a problem with. Sometimes these files are almost clean, but sometimes they are full of junk or horribly mangled by the automated editing. There should be PPP solutions already run for these files, so they are ready to be checked.<br />
<br />
Set the <code>CAMP</code> variable (if not set): <br />
<pre><br />
setenv CAMP $ANALYSIS/wwww<br />
</pre><br />
Again, <code>wwww</code> is the 4-digit GPS-week.<br />
<br />
Now run the solutions. The first time you run the solutions, look at the residuals very carefully before trying <code>short_hand</code>. Uncompress the postlog, postfit and postbreak files, and then use <code>allbadp</code> to check the pseudorange and <code>allbreaks</code> to check for major cycle slips.<br />
<br />
A very common problem is that for several stations per week, there will be one satellite arc of pseudorange data that all have residuals of roughly 2000 cm. If you see these, don't delete the data, but instead run del_pcode_arc to remove only the pseudorange data. I am not sure why these show up, but it could be either a hardware channel bias or a pre-processing glitch. They happen much more often with Ashtechs than any others, and are particuarly common with the US Coast Guard CORS sites. In the <code>qm</code> directory,<br />
<br />
<pre><br />
del_pcode_arc *02gus2* GUS2 GPS41<br />
</pre><br />
<br />
If you just run <code>short_hand</code> without looking, it will probably either throw out all the pseudorange for one site, or delete a lot of data (phase and pseudorange) where only the pseudorange needs to be deleted. So don't do that. Then I delete a batch of bad pseudorange data to get the number of pseudorange outliers under control for the next run.<br />
<br />
<pre><br />
cd $ANALYSIS/1381/flt<br />
gunzip *alaska*post*<br />
allbadp<br />
allbreaks<br />
# Based on this, run del_pcode_arc as above, and add ambiguities manually if needed.<br />
#<br />
delete_allbadp 50<br />
# This creates a file called delete.<br />
vi delete<br />
# Remove lines for any points for which you have already run del_pocde_arc.<br />
cd ../qm<br />
sh ../flt/delete<br />
</pre><br />
<br />
At this point, don't worry too much about phase outliers. Basically we are trying to get the number of pseudorange outliers down into the range where <code>short_hand</code> will do the right thing when we run it later. Now may be a good time to run <code>Alaska_cleaning_solution $date</code>, which runs a smaller and much faster solution including the sites that most often need some cleaning.<br />
<br />
===Data Backup===<br />
<br />
RINEX file backups.<br />
There are either 1 or 2 separate backups of the raw rinex files. For data we collected<br />
ourselves, a copy of the original rinex files can be found in either the campaign<br />
directory (/gps/akda/Campaigns/Data.2007/<project>, where <project> is the project name,<br />
and Data.2007 will change with the year), or in the continuous site ftp area<br />
(/gps/akda/Permanent/2007/260/, where 2007 is the year and 160 is the day of year). Also,<br />
every rinex file put through the hopper is moved to a directory like $RAWDATA/2007/260/<br />
(again, year and day of year may change). However, the $RAWDATA/2007/260/ directories are<br />
not really archived and eventually they will be deleted. But in practice we have most of<br />
the last few years of rinex files online in case something goes wrong.<br />
<br />
QM file backups.<br />
Before autoclean makes any changes to a qm file, it copies the file to a subdirectory<br />
called "original" in the qm directory. so if you completely destroy a qm file by<br />
accident, you can still go back the original version. Of course, that loses all editing<br />
done to the file, but at least the original data can be recovered easily. In general, it<br />
is not a good idea to go back to the version in the original subdirectory unless you know<br />
what you are doing, because doing that can make a lot more work for everyone. Mostly we<br />
do that when files have been mangled by autoclean. It is actually hard to mangle data<br />
files using our usual editing procedures.<br />
<br />
<br />
<br />
===Customized Solutions===<br />
<br />
Sometimes customized solutions are required for various reasons. This link will provide some strategies that may improve your situation.<br />
<br>[[Kinematic Processing]]<br />
<br>[[Ambiguity Resolution]]<br />
<br />
===Products / file contents===<br />
<br />
Where to find certain information and what are the structure / content of output files? It is started to be summarized on the [[files | files]] page.<br />
<br />
=== Velocity solutions ===<br />
<pre><br />
/> su akda<br />
/> cd $ANALYZED<br />
/> mkdir <USEFUL NEW PROJECTNAME><br />
</pre><br />
<br />
Find another project and copy the following files into your new directory:<br />
<br />
<pre><br />
/> cp *.nml $ANALYZED/new_project<br />
/> cp make_vel* $ANALYZED/new_project<br />
</pre><br />
<br />
Rename the *.nml file to something reasonable for your project and edit this file, it needs to know the stations that you want to include<br />
into your velocity solution as well as the input file locations where the data comes from. To get the input files in the correct syntax you might wanna use:<br />
<br />
<pre><br />
/> grep_vel_infiles.pl --from-week=WWWW --to-week=WWWW --infile-index=x --sum-id=<alaska2.0_nfxigs03 | NEAsia2.0_nfxigs03 | ...><br />
</pre><br />
<br />
"WWWW" stands for the week you want to start / end with and "x" is the starting value for the id-counter. These id's are useful later to reference certain input files for additional editing purposes (see below). From-week, to-week, and infile-index are optional. "sum-id" is basically the solution name. Copy all lines of the format " infile(x) = '...'" into your namelist (nml) file (insert before the &amp;end). ([http://www.gps.alaska.edu/internal/index.php/Special:Call/Include_info%2C/export/ftpweb/htdocs/sh2doc/grep_vel_infiles.pl.html grep_vel_infiles.pl] documentation)<br />
<br />
Once the editing of the namelist file is finished:<br />
<br />
<pre><br />
/> refresh_zebu younamelist.nml outfile.ref<br />
</pre><br />
<br />
This is necessary to order and re-number the entries in your namelistfile which can contain comments. To not have you go through the namelist file whenever you want to try to throw out a station or some data and renumber everything, refresh_zebu does that for you.<br />
<br />
Once you have a nice reference file (.ref):<br />
<br />
<pre><br />
/> rzebu2 outfile.ref > & out<br />
</pre><br />
<br />
You should redirect the output to a file so you can look at it later :).<br />
<br />
For example right now. As soon as the solution is finished running, look at the total Chi_squared value at the bottom of the output in "out". It should be "1". If that's not the case which is likely if you run a solution for the first couple of times look for sites that cause the deviation from chi_squared=1. Note the site names with the larges chi squared values. Then you can do three things:<br />
<br />
<pre><br />
A) /> grep SITE outlier.inf<br />
B) /> grep SITE residual.inf<br />
C) /> vi $ANALYSIS/solution_timeseries/SITE.pfiles<br />
</pre><br />
<br />
In all three cases you want to find dates on which the sigmas for this site are rather large. Note down the date and find it in the namelist <br />
file (*.nml) and remove the respective site from the velocity solution for that day by adding a line:<br />
<br />
<pre><br />
removedat(a, infile_id) = 'SITENAME'<br />
</pre><br />
<br />
"a" is the id that simply counts how many removedats have been invoked on that one infile_id. "infile_id" is the counter I mentioned above. An example is probably best:<br />
<br />
<pre><br />
infile(161) = '/gps/analysis/1222/post/03jun10NEAsia2.0_nfxigs03.sum'<br />
removedat(1,161) = 'ELD '<br />
removedat(2,161) = 'PETP'<br />
</pre><br />
<br />
Here I assume that both sites, "ELD" and "PETP" misbehave on June 10, 2003 for the North East Asia solution. Hence I remove them from the velocity solution.<br />
<br />
Remove all the files created by <code>rzebu2</code>. Creating a Makefile of the form:<br />
<br />
<pre><br />
clean:<br />
rm *.ref ATWA ATY solution.* *.inf out nnr.* *.dat *.gmtvec *.vel fort.* gmt.format STACOV argus.weights<br />
</pre><br />
<br />
might be useful.<br />
<br />
Repeat the above until your reduced chi squared is <= 1.0. If you can't get there, change the fudge_factor as follows:<br />
<br />
<pre><br />
new_fudge = old_fudge * Chi_squared<br />
</pre><br />
<br />
and rerun the solution one last time. The reduced chi squared value should be 1.0 .<br />
<br />
Once you achieved that you can go to the next level and run one of the make_vel files you copied to your directory:<br />
<pre><br />
make_vel_Sella: velocities relative to a stable North America<br />
make_vel_ITRF: velocities in ITRF <br />
make_vel_EURA: velocities relative to a stable Eurasia <br />
make_vel_XXXX: velocities with reference station XXXX<br />
</pre><br />
<br />
There might be others, or you could go ahead and edit these files to adapt them to your needs. The make files create *.gmtvec output which you can use to with e.g., <code>psvelo</code> in a GMT script.</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=Solution_Strategy_2.0&diff=1895Solution Strategy 2.02010-01-13T07:42:46Z<p>Jeff: </p>
<hr />
<div>page not yet prepared.<br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]<br />
<br />
More stuff goes here.<br />
<br />
<table border="1"><br />
<tr><br />
<td width="200">Parameter</td><br />
<td width="800">Explanation</td><br />
</tr><br />
<br />
<tr><br />
<td width="200">Parameter</td><br />
<td width="800">Explanation</td><br />
</tr><br />
<br />
</table><br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=Solution_Strategy_2.0&diff=1894Solution Strategy 2.02010-01-13T07:42:20Z<p>Jeff: </p>
<hr />
<div>page not yet prepared.<br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]<br />
<br />
More stuff goes here.<br />
<br />
<table border="1"><br />
<tr><br />
<td width="100">Parameter</td><br />
<td width="500">Explanation</td><br />
</tr><br />
<br />
<tr><br />
<td width="100">Parameter</td><br />
<td width="500">Explanation</td><br />
</tr><br />
<br />
</table><br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=GPS_analysis_system&diff=1893GPS analysis system2010-01-13T07:38:50Z<p>Jeff: </p>
<hr />
<div>We use a GPS data analysis system based on the [http://sideshow.jpl.nasa.gov GIPSY] software developed at JPL. Most of the GIPSY programs are called by [[Special:Call/Include_info%2C/export/ftpweb/htdocs/sh2doc/index.html | 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.<br />
<br />
===Documentation of Solution Strategies (new)===<br />
The links below describe our solution strategy as it has evolved over time.<br />
{|<br />
|[[Solution_Strategy_1.0 | 1.0 1990s strategy.]]<br />
|-<br />
|[[Solution_Strategy_2.0 | 2.0 Network solutions used from ~2002 through 2008.]]<br />
|-<br />
|[[Solution_Strategy_2.5 | 2.5 PPP solutions but otherwise strategy 2.0]]<br />
|-<br />
|[[Solution_Strategy_3.0 | 3.0 2010 new solution strategy]]<br />
|}<br />
<br />
===Where do you put RINEX files?===<br />
RINEX files should be put into the hopper, <code>$RAWDATA/hopper</code>. 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 <code>autofront</code> and <code>autoclean</code> programs manually.<br />
<br />
===What happens automatically?===<br />
<br />
Quite a lot.<br />
<br />
Autoftp runs every night beginning at 6pm local time and fetches data files. These are placed into the '''hopper''' ($RAWDATA/hopper), a directory where all data files are put for entry into the system and processing. Autofront then runs at midnight to process all files in the hopper, including any placed there manually (from campaigns, for example). Finally, autoclean runs at 4am local to carry out automated screening for cycle slips and other bad data.<br />
<br />
====Autoftp====<br />
<br />
Autoftp is an efficient data-fetching tool that uses wget to automatically get data from any of several internet GPS data archives. It reads a list of desired sites from a ''request file'', which contains the date in the filename, and attempts to find and download data from as many sites as possible. It is intended to run automatically on a daily basis under cron, and when acccompanied by another simple program to generate a standard request file every day, it can easily fetch a standard set of sites on a daily basis for analysis. Because it keeps track in the request file of sites that it has found already, autoftp can be run multiple times with the same request file and it will not repeatedly fetch data. This is ideal for the real world, in which data from some sites are available rapidly while data from other sites may require many hours or days to become available.<br />
<br />
====Autofront====<br />
<br />
Autofront is a script intended to run under cron that carried out the initial "front end" processing on a set of GPS data files. When executed, it will process all files in the '''hopper''' directory, and will place each resulting qm file into the appropriate week directory.<br />
<br />
Autofront runs the following steps<br />
1. Checks on the validity of RINEX file and repair of some common problems.<br />
2. Depending on receiver type, clockprep -fixtags<br />
3. (optional, presently not default) PhasEdit<br />
4. ninja<br />
<br />
====Autoclean====<br />
<br />
Autoclean carries out automated cleaning of cycle slips, based on point positioning solutions. It is quite effective and at present it rarely misses cycle slips unless they are smaller than its minimum tolerance (10 cm). Autoclean operates on an ''edit-request'' file, which contains the name of the directory (week directory) and a list of qm files that need to be cleaned. It will clean all files on the list as long as orbits and clocks are available, and it marks off files that have been cleaned so that it can safely be run multiple times.<br />
<br />
Autoclean operates in an iterative mode. It's zeroth iteration is to do a pseudorange-only solution and identify and delete extremely bad pseudorange data. In this step it uses a tolerance that catches only grossly biased data. (Explain it). It then carries out 1 or more iterations of screening the phase data. In each iteration, it uses postbreak to identify discontinuities in the residuals of a point positioning solution. Postbreak is run with an adaptive tolerance (minimum 10 cm), and it is critical that my slightly modified version of postbreak be used. If any cycle slips are discovered, they are flagged and another iteration is run. Autoclean runs a maximum of 4 iterations on the phase data.<br />
<br />
===Where do the data files go?===<br />
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|week directory]] there are several [[subdirectories]]; qm files are stored in <code>$ANALYSIS/wwww/qm</code>, where <code>wwww</code> is the 4 character GPS week number (with a leading zero if needed).<br />
<br />
===Running Solutions===<br />
In the [[subdirectories|flt]] directory for each [[week directory|week]] there will (hopefully) be a UNIX script called<br><br />
''make-*''<br><br />
This script runs another script called<br><br />
''standard_*_solution''<br><br />
which again runs another script called<br><br />
''solve''<br><br />
for each [[subnets | network of stations]] (see each subnet with [[Subnets_GoogleEarth | Google Earth]]) for each day. The solve script runs solutions for each of these networks based on the data from sites in the network that are available in the qm directory.<br />
<br />
To run solutions, copy the ''make'' script to a file called ''make-flt'' (for example).<br />
<br />
Check that the ''make-flt'' script contains all the days that you want to run.<br />
<br />
Check which [[Linux Computer System | computer]] is free to run the script (to do so, type:)<br />
check-solves<br />
log on to a free computer and type<br />
submit make-flt<br />
<br />
As the script runs, files will appear in the [[subdirectories|flt]] directory for each [[subnets|network]] for each day. Usually<br />
this script will have been run once [[#What happens automatically? | automatically]], so there will often already be files in the [[subdirectories|flt]]<br />
directory ready to be cleaned and then re-run.<br />
<br />
<br />
Solve, a very flexible script. (link to detailed help)<br />
<br />
Philosophy of solve<br />
<br />
Subnet files and campaign files<br />
<br />
Standard solutions<br />
<br />
(text of standard_Alaska_solution)<br />
<br />
Running several days at once: make-make-flt and make-alaska<br />
<br />
(text of a standard make-alaska file and variant)<br />
<br />
Running several weeks at once<br />
<br />
(text of sample rerun-* file)<br />
<br />
===Cleaning Solutions===<br />
<br />
Sometimes bad data (outliers and cycle slips) make it past the automatic editors. When this<br />
happens the bad data are removed from the qm files by either deleting points or by inserting<br />
new phase ambiguities to deal with cycle slips. The steps, commands and scrips to use are somewhat explained [[How to clean a solution? | here]]. Once the data are cleaned, the files should be deleted from the [[subdirectories|flt]] directory and the solutions re-run (run <code>make-flt</code> again). Usually you will have to go through 2-3<br />
iterations of the cleaning-rerunning cycle. To be clean, the .point files for a solution do not<br />
exist or are small (below 1000 bytes). Once a solution is clean the files should remain in<br />
the [[subdirectories|flt]] directory and the lines to rerun that solution should be deleted from the <code>make-flt</code> file.<br />
<br />
Initial Explanation of terms<br />
<br />
Expected residuals from a clean solution<br />
<br />
Automated screening: postfit, the point file, postbreak<br />
<br />
Checking for bad pseudorange data: badp, [[How to clean a solution?|allbadp]]<br />
<br />
Removing biased pseudorange data: [[How to clean a solution?|del_pcode_arc]]<br />
<br />
Automatically identified cycle slips: breaks, [[How to clean a solution?|allbreaks]]<br />
<br />
Quickly scanning through residuals: short_hand<br><br />
The data problems can be identified and<br />
fixed using the program<br />
[[short_hand]] <br />
(follow the link to read about and ask for help to get started with this program).<br> <br />
Limitations of short_hand<br />
<br />
Manually checking residuals and fixing [[problem stations | problems]]<br />
<br />
===Procedure for Running Solutions for a week for the first time===<br />
<br />
A few special things need to be done the very first time solutions in a week are run. First, you need to make up a script to run all days of the week. This may need to be edited if the JPL final orbits are not available at the time. The <code>standard_Alaska_solution</code> uses the non-fiducial orbits and thus requires that the final JPL orbits be present. If they are not, you can run <code>rapid_Alaska_solution</code> instead. <br />
<br />
Then, the log files from autoclean should be moved away to a subdirectory, and any problem stations identified by autoclean should be checked. Then, you are ready to run the solutions.<br />
<br />
First, make a script to run solutions. For example, to make a script to run all days of the week for the Alaska solution:<br />
<pre><br />
cd $ANALYSIS<br />
make-make-flt 1381<br />
cd 1381/flt<br />
vi make-alaska<br />
# Edit the file if needed so that you are ready to run the rapid solutions.<br />
<br />
cat make-alaska<br />
#!/bin/csh -f<br />
#<br />
setenv CAMP $ANALYSIS/1381<br />
#<br />
#standard_Alaska_solution 06jul01<br />
#standard_Alaska_solution 06jun25<br />
#standard_Alaska_solution 06jun26<br />
#standard_Alaska_solution 06jun27<br />
#standard_Alaska_solution 06jun28<br />
#standard_Alaska_solution 06jun29<br />
#standard_Alaska_solution 06jun30<br />
#<br />
rapid_Alaska_solution 06jul01<br />
rapid_Alaska_solution 06jun25<br />
rapid_Alaska_solution 06jun26<br />
rapid_Alaska_solution 06jun27<br />
rapid_Alaska_solution 06jun28<br />
rapid_Alaska_solution 06jun29<br />
rapid_Alaska_solution 06jun30<br />
<br />
</pre><br />
<br />
The script <code>make-make-flt</code> finds all unique dates for qm files in that week's directory, and uses that to generate the script, so if you run it before the end of the week you will get a partial script. If the final JPL orbits are not yet present, you will need to edit the script to change "standard" ro "rapid". Or better yet, copy all the lines and comment one set out, then modify the others to read "rapid_Alaska_solution <date>".<br />
<br />
Next call <code>mv_logfiles</code> (being in the WEEK/flt directory!) which creates a subdirectory called <code>logfiles</code> and moves <br />
all of autoclean's logfiles of the format <code>*____*.i*</code> into this directory:<br />
<br />
<pre><br />
HOSTNAME WWWW/flt> mv_logfiles<br />
</pre><br />
<br />
Now look for a file called <code>make-problems</code>, which lists all files that autoclean had a problem with. Sometimes these files are almost clean, but sometimes they are full of junk or horribly mangled by the automated editing. There should be PPP solutions already run for these files, so they are ready to be checked.<br />
<br />
Set the <code>CAMP</code> variable (if not set): <br />
<pre><br />
setenv CAMP $ANALYSIS/wwww<br />
</pre><br />
Again, <code>wwww</code> is the 4-digit GPS-week.<br />
<br />
Now run the solutions. The first time you run the solutions, look at the residuals very carefully before trying <code>short_hand</code>. Uncompress the postlog, postfit and postbreak files, and then use <code>allbadp</code> to check the pseudorange and <code>allbreaks</code> to check for major cycle slips.<br />
<br />
A very common problem is that for several stations per week, there will be one satellite arc of pseudorange data that all have residuals of roughly 2000 cm. If you see these, don't delete the data, but instead run del_pcode_arc to remove only the pseudorange data. I am not sure why these show up, but it could be either a hardware channel bias or a pre-processing glitch. They happen much more often with Ashtechs than any others, and are particuarly common with the US Coast Guard CORS sites. In the <code>qm</code> directory,<br />
<br />
<pre><br />
del_pcode_arc *02gus2* GUS2 GPS41<br />
</pre><br />
<br />
If you just run <code>short_hand</code> without looking, it will probably either throw out all the pseudorange for one site, or delete a lot of data (phase and pseudorange) where only the pseudorange needs to be deleted. So don't do that. Then I delete a batch of bad pseudorange data to get the number of pseudorange outliers under control for the next run.<br />
<br />
<pre><br />
cd $ANALYSIS/1381/flt<br />
gunzip *alaska*post*<br />
allbadp<br />
allbreaks<br />
# Based on this, run del_pcode_arc as above, and add ambiguities manually if needed.<br />
#<br />
delete_allbadp 50<br />
# This creates a file called delete.<br />
vi delete<br />
# Remove lines for any points for which you have already run del_pocde_arc.<br />
cd ../qm<br />
sh ../flt/delete<br />
</pre><br />
<br />
At this point, don't worry too much about phase outliers. Basically we are trying to get the number of pseudorange outliers down into the range where <code>short_hand</code> will do the right thing when we run it later. Now may be a good time to run <code>Alaska_cleaning_solution $date</code>, which runs a smaller and much faster solution including the sites that most often need some cleaning.<br />
<br />
===Data Backup===<br />
<br />
RINEX file backups.<br />
There are either 1 or 2 separate backups of the raw rinex files. For data we collected<br />
ourselves, a copy of the original rinex files can be found in either the campaign<br />
directory (/gps/akda/Campaigns/Data.2007/<project>, where <project> is the project name,<br />
and Data.2007 will change with the year), or in the continuous site ftp area<br />
(/gps/akda/Permanent/2007/260/, where 2007 is the year and 160 is the day of year). Also,<br />
every rinex file put through the hopper is moved to a directory like $RAWDATA/2007/260/<br />
(again, year and day of year may change). However, the $RAWDATA/2007/260/ directories are<br />
not really archived and eventually they will be deleted. But in practice we have most of<br />
the last few years of rinex files online in case something goes wrong.<br />
<br />
QM file backups.<br />
Before autoclean makes any changes to a qm file, it copies the file to a subdirectory<br />
called "original" in the qm directory. so if you completely destroy a qm file by<br />
accident, you can still go back the original version. Of course, that loses all editing<br />
done to the file, but at least the original data can be recovered easily. In general, it<br />
is not a good idea to go back to the version in the original subdirectory unless you know<br />
what you are doing, because doing that can make a lot more work for everyone. Mostly we<br />
do that when files have been mangled by autoclean. It is actually hard to mangle data<br />
files using our usual editing procedures.<br />
<br />
<br />
<br />
===Customized Solutions===<br />
<br />
Sometimes customized solutions are required for various reasons. This link will provide some strategies that may improve your situation.<br />
<br>[[Kinematic Processing]]<br />
<br>[[Ambiguity Resolution]]<br />
<br />
===Products / file contents===<br />
<br />
Where to find certain information and what are the structure / content of output files? It is started to be summarized on the [[files | files]] page.<br />
<br />
=== Velocity solutions ===<br />
<pre><br />
/> su akda<br />
/> cd $ANALYZED<br />
/> mkdir <USEFUL NEW PROJECTNAME><br />
</pre><br />
<br />
Find another project and copy the following files into your new directory:<br />
<br />
<pre><br />
/> cp *.nml $ANALYZED/new_project<br />
/> cp make_vel* $ANALYZED/new_project<br />
</pre><br />
<br />
Rename the *.nml file to something reasonable for your project and edit this file, it needs to know the stations that you want to include<br />
into your velocity solution as well as the input file locations where the data comes from. To get the input files in the correct syntax you might wanna use:<br />
<br />
<pre><br />
/> grep_vel_infiles.pl --from-week=WWWW --to-week=WWWW --infile-index=x --sum-id=<alaska2.0_nfxigs03 | NEAsia2.0_nfxigs03 | ...><br />
</pre><br />
<br />
"WWWW" stands for the week you want to start / end with and "x" is the starting value for the id-counter. These id's are useful later to reference certain input files for additional editing purposes (see below). From-week, to-week, and infile-index are optional. "sum-id" is basically the solution name. Copy all lines of the format " infile(x) = '...'" into your namelist (nml) file (insert before the &amp;end). ([http://www.gps.alaska.edu/internal/index.php/Special:Call/Include_info%2C/export/ftpweb/htdocs/sh2doc/grep_vel_infiles.pl.html grep_vel_infiles.pl] documentation)<br />
<br />
Once the editing of the namelist file is finished:<br />
<br />
<pre><br />
/> refresh_zebu younamelist.nml outfile.ref<br />
</pre><br />
<br />
This is necessary to order and re-number the entries in your namelistfile which can contain comments. To not have you go through the namelist file whenever you want to try to throw out a station or some data and renumber everything, refresh_zebu does that for you.<br />
<br />
Once you have a nice reference file (.ref):<br />
<br />
<pre><br />
/> rzebu2 outfile.ref > & out<br />
</pre><br />
<br />
You should redirect the output to a file so you can look at it later :).<br />
<br />
For example right now. As soon as the solution is finished running, look at the total Chi_squared value at the bottom of the output in "out". It should be "1". If that's not the case which is likely if you run a solution for the first couple of times look for sites that cause the deviation from chi_squared=1. Note the site names with the larges chi squared values. Then you can do three things:<br />
<br />
<pre><br />
A) /> grep SITE outlier.inf<br />
B) /> grep SITE residual.inf<br />
C) /> vi $ANALYSIS/solution_timeseries/SITE.pfiles<br />
</pre><br />
<br />
In all three cases you want to find dates on which the sigmas for this site are rather large. Note down the date and find it in the namelist <br />
file (*.nml) and remove the respective site from the velocity solution for that day by adding a line:<br />
<br />
<pre><br />
removedat(a, infile_id) = 'SITENAME'<br />
</pre><br />
<br />
"a" is the id that simply counts how many removedats have been invoked on that one infile_id. "infile_id" is the counter I mentioned above. An example is probably best:<br />
<br />
<pre><br />
infile(161) = '/gps/analysis/1222/post/03jun10NEAsia2.0_nfxigs03.sum'<br />
removedat(1,161) = 'ELD '<br />
removedat(2,161) = 'PETP'<br />
</pre><br />
<br />
Here I assume that both sites, "ELD" and "PETP" misbehave on June 10, 2003 for the North East Asia solution. Hence I remove them from the velocity solution.<br />
<br />
Remove all the files created by <code>rzebu2</code>. Creating a Makefile of the form:<br />
<br />
<pre><br />
clean:<br />
rm *.ref ATWA ATY solution.* *.inf out nnr.* *.dat *.gmtvec *.vel fort.* gmt.format STACOV argus.weights<br />
</pre><br />
<br />
might be useful.<br />
<br />
Repeat the above until your reduced chi squared is <= 1.0. If you can't get there, change the fudge_factor as follows:<br />
<br />
<pre><br />
new_fudge = old_fudge * Chi_squared<br />
</pre><br />
<br />
and rerun the solution one last time. The reduced chi squared value should be 1.0 .<br />
<br />
Once you achieved that you can go to the next level and run one of the make_vel files you copied to your directory:<br />
<pre><br />
make_vel_Sella: velocities relative to a stable North America<br />
make_vel_ITRF: velocities in ITRF <br />
make_vel_EURA: velocities relative to a stable Eurasia <br />
make_vel_XXXX: velocities with reference station XXXX<br />
</pre><br />
<br />
There might be others, or you could go ahead and edit these files to adapt them to your needs. The make files create *.gmtvec output which you can use to with e.g., <code>psvelo</code> in a GMT script.</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=Solution_Strategy_2.5&diff=1699Solution Strategy 2.52010-01-12T20:03:50Z<p>Jeff: New page: page not yet prepared. Back to GPS Analysis System More stuff goes here. Back to GPS Analysis System</p>
<hr />
<div>page not yet prepared.<br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]<br />
<br />
More stuff goes here.<br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=Solution_Strategy_2.0&diff=1698Solution Strategy 2.02010-01-12T20:03:41Z<p>Jeff: New page: page not yet prepared. Back to GPS Analysis System More stuff goes here. Back to GPS Analysis System</p>
<hr />
<div>page not yet prepared.<br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]<br />
<br />
More stuff goes here.<br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=Solution_Strategy_1.0&diff=1697Solution Strategy 1.02010-01-12T20:03:21Z<p>Jeff: New page: page not yet prepared Back to GPS Analysis System More stuff goes here. Back to GPS Analysis System</p>
<hr />
<div>page not yet prepared<br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]<br />
<br />
More stuff goes here.<br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=Solution_Strategy_3.0&diff=1696Solution Strategy 3.02010-01-12T20:02:55Z<p>Jeff: </p>
<hr />
<div>This solution strategy is still under development.<br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]<br />
<br />
More stuff goes here.<br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=Solution_Strategy_3.0&diff=1695Solution Strategy 3.02010-01-12T20:02:25Z<p>Jeff: New page: This solution strategy is still under development. Back to GPS Analysis System</p>
<hr />
<div>This solution strategy is still under development.<br />
<br />
[[GPS_analysis_system | Back to GPS Analysis System]]</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=GPS_analysis_system&diff=1694GPS analysis system2010-01-12T20:00:39Z<p>Jeff: </p>
<hr />
<div>We use a GPS data analysis system based on the [http://sideshow.jpl.nasa.gov GIPSY] software developed at JPL. Most of the GIPSY programs are called by [[Special:Call/Include_info%2C/export/ftpweb/htdocs/sh2doc/index.html | 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.<br />
<br />
===Documentation of Solution Strategies (new)===<br />
The links below describe our solution strategy as it has evolved over time.<br />
[[Solution_Strategy_1.0 | 1.0 1990s strategy.]]<br />
[[Solution_Strategy_2.0 | 2.0 Network solutions used from ~2002 through 2008.]]<br />
[[Solution_Strategy_2.5 | 2.5 PPP solutions but otherwise strategy 2.0]]<br />
[[Solution_Strategy_3.0 | 3.0 2010 new solution strategy]]<br />
<br />
===Where do you put RINEX files?===<br />
RINEX files should be put into the hopper, <code>$RAWDATA/hopper</code>. 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 <code>autofront</code> and <code>autoclean</code> programs manually.<br />
<br />
===What happens automatically?===<br />
<br />
Quite a lot.<br />
<br />
Autoftp runs every night beginning at 6pm local time and fetches data files. These are placed into the '''hopper''' ($RAWDATA/hopper), a directory where all data files are put for entry into the system and processing. Autofront then runs at midnight to process all files in the hopper, including any placed there manually (from campaigns, for example). Finally, autoclean runs at 4am local to carry out automated screening for cycle slips and other bad data.<br />
<br />
====Autoftp====<br />
<br />
Autoftp is an efficient data-fetching tool that uses wget to automatically get data from any of several internet GPS data archives. It reads a list of desired sites from a ''request file'', which contains the date in the filename, and attempts to find and download data from as many sites as possible. It is intended to run automatically on a daily basis under cron, and when acccompanied by another simple program to generate a standard request file every day, it can easily fetch a standard set of sites on a daily basis for analysis. Because it keeps track in the request file of sites that it has found already, autoftp can be run multiple times with the same request file and it will not repeatedly fetch data. This is ideal for the real world, in which data from some sites are available rapidly while data from other sites may require many hours or days to become available.<br />
<br />
====Autofront====<br />
<br />
Autofront is a script intended to run under cron that carried out the initial "front end" processing on a set of GPS data files. When executed, it will process all files in the '''hopper''' directory, and will place each resulting qm file into the appropriate week directory.<br />
<br />
Autofront runs the following steps<br />
1. Checks on the validity of RINEX file and repair of some common problems.<br />
2. Depending on receiver type, clockprep -fixtags<br />
3. (optional, presently not default) PhasEdit<br />
4. ninja<br />
<br />
====Autoclean====<br />
<br />
Autoclean carries out automated cleaning of cycle slips, based on point positioning solutions. It is quite effective and at present it rarely misses cycle slips unless they are smaller than its minimum tolerance (10 cm). Autoclean operates on an ''edit-request'' file, which contains the name of the directory (week directory) and a list of qm files that need to be cleaned. It will clean all files on the list as long as orbits and clocks are available, and it marks off files that have been cleaned so that it can safely be run multiple times.<br />
<br />
Autoclean operates in an iterative mode. It's zeroth iteration is to do a pseudorange-only solution and identify and delete extremely bad pseudorange data. In this step it uses a tolerance that catches only grossly biased data. (Explain it). It then carries out 1 or more iterations of screening the phase data. In each iteration, it uses postbreak to identify discontinuities in the residuals of a point positioning solution. Postbreak is run with an adaptive tolerance (minimum 10 cm), and it is critical that my slightly modified version of postbreak be used. If any cycle slips are discovered, they are flagged and another iteration is run. Autoclean runs a maximum of 4 iterations on the phase data.<br />
<br />
===Where do the data files go?===<br />
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|week directory]] there are several [[subdirectories]]; qm files are stored in <code>$ANALYSIS/wwww/qm</code>, where <code>wwww</code> is the 4 character GPS week number (with a leading zero if needed).<br />
<br />
===Running Solutions===<br />
In the [[subdirectories|flt]] directory for each [[week directory|week]] there will (hopefully) be a UNIX script called<br><br />
''make-*''<br><br />
This script runs another script called<br><br />
''standard_*_solution''<br><br />
which again runs another script called<br><br />
''solve''<br><br />
for each [[subnets | network of stations]] (see each subnet with [[Subnets_GoogleEarth | Google Earth]]) for each day. The solve script runs solutions for each of these networks based on the data from sites in the network that are available in the qm directory.<br />
<br />
To run solutions, copy the ''make'' script to a file called ''make-flt'' (for example).<br />
<br />
Check that the ''make-flt'' script contains all the days that you want to run.<br />
<br />
Check which [[Linux Computer System | computer]] is free to run the script (to do so, type:)<br />
check-solves<br />
log on to a free computer and type<br />
submit make-flt<br />
<br />
As the script runs, files will appear in the [[subdirectories|flt]] directory for each [[subnets|network]] for each day. Usually<br />
this script will have been run once [[#What happens automatically? | automatically]], so there will often already be files in the [[subdirectories|flt]]<br />
directory ready to be cleaned and then re-run.<br />
<br />
<br />
Solve, a very flexible script. (link to detailed help)<br />
<br />
Philosophy of solve<br />
<br />
Subnet files and campaign files<br />
<br />
Standard solutions<br />
<br />
(text of standard_Alaska_solution)<br />
<br />
Running several days at once: make-make-flt and make-alaska<br />
<br />
(text of a standard make-alaska file and variant)<br />
<br />
Running several weeks at once<br />
<br />
(text of sample rerun-* file)<br />
<br />
===Cleaning Solutions===<br />
<br />
Sometimes bad data (outliers and cycle slips) make it past the automatic editors. When this<br />
happens the bad data are removed from the qm files by either deleting points or by inserting<br />
new phase ambiguities to deal with cycle slips. The steps, commands and scrips to use are somewhat explained [[How to clean a solution? | here]]. Once the data are cleaned, the files should be deleted from the [[subdirectories|flt]] directory and the solutions re-run (run <code>make-flt</code> again). Usually you will have to go through 2-3<br />
iterations of the cleaning-rerunning cycle. To be clean, the .point files for a solution do not<br />
exist or are small (below 1000 bytes). Once a solution is clean the files should remain in<br />
the [[subdirectories|flt]] directory and the lines to rerun that solution should be deleted from the <code>make-flt</code> file.<br />
<br />
Initial Explanation of terms<br />
<br />
Expected residuals from a clean solution<br />
<br />
Automated screening: postfit, the point file, postbreak<br />
<br />
Checking for bad pseudorange data: badp, [[How to clean a solution?|allbadp]]<br />
<br />
Removing biased pseudorange data: [[How to clean a solution?|del_pcode_arc]]<br />
<br />
Automatically identified cycle slips: breaks, [[How to clean a solution?|allbreaks]]<br />
<br />
Quickly scanning through residuals: short_hand<br><br />
The data problems can be identified and<br />
fixed using the program<br />
[[short_hand]] <br />
(follow the link to read about and ask for help to get started with this program).<br> <br />
Limitations of short_hand<br />
<br />
Manually checking residuals and fixing [[problem stations | problems]]<br />
<br />
===Procedure for Running Solutions for a week for the first time===<br />
<br />
A few special things need to be done the very first time solutions in a week are run. First, you need to make up a script to run all days of the week. This may need to be edited if the JPL final orbits are not available at the time. The <code>standard_Alaska_solution</code> uses the non-fiducial orbits and thus requires that the final JPL orbits be present. If they are not, you can run <code>rapid_Alaska_solution</code> instead. <br />
<br />
Then, the log files from autoclean should be moved away to a subdirectory, and any problem stations identified by autoclean should be checked. Then, you are ready to run the solutions.<br />
<br />
First, make a script to run solutions. For example, to make a script to run all days of the week for the Alaska solution:<br />
<pre><br />
cd $ANALYSIS<br />
make-make-flt 1381<br />
cd 1381/flt<br />
vi make-alaska<br />
# Edit the file if needed so that you are ready to run the rapid solutions.<br />
<br />
cat make-alaska<br />
#!/bin/csh -f<br />
#<br />
setenv CAMP $ANALYSIS/1381<br />
#<br />
#standard_Alaska_solution 06jul01<br />
#standard_Alaska_solution 06jun25<br />
#standard_Alaska_solution 06jun26<br />
#standard_Alaska_solution 06jun27<br />
#standard_Alaska_solution 06jun28<br />
#standard_Alaska_solution 06jun29<br />
#standard_Alaska_solution 06jun30<br />
#<br />
rapid_Alaska_solution 06jul01<br />
rapid_Alaska_solution 06jun25<br />
rapid_Alaska_solution 06jun26<br />
rapid_Alaska_solution 06jun27<br />
rapid_Alaska_solution 06jun28<br />
rapid_Alaska_solution 06jun29<br />
rapid_Alaska_solution 06jun30<br />
<br />
</pre><br />
<br />
The script <code>make-make-flt</code> finds all unique dates for qm files in that week's directory, and uses that to generate the script, so if you run it before the end of the week you will get a partial script. If the final JPL orbits are not yet present, you will need to edit the script to change "standard" ro "rapid". Or better yet, copy all the lines and comment one set out, then modify the others to read "rapid_Alaska_solution <date>".<br />
<br />
Next call <code>mv_logfiles</code> (being in the WEEK/flt directory!) which creates a subdirectory called <code>logfiles</code> and moves <br />
all of autoclean's logfiles of the format <code>*____*.i*</code> into this directory:<br />
<br />
<pre><br />
HOSTNAME WWWW/flt> mv_logfiles<br />
</pre><br />
<br />
Now look for a file called <code>make-problems</code>, which lists all files that autoclean had a problem with. Sometimes these files are almost clean, but sometimes they are full of junk or horribly mangled by the automated editing. There should be PPP solutions already run for these files, so they are ready to be checked.<br />
<br />
Set the <code>CAMP</code> variable (if not set): <br />
<pre><br />
setenv CAMP $ANALYSIS/wwww<br />
</pre><br />
Again, <code>wwww</code> is the 4-digit GPS-week.<br />
<br />
Now run the solutions. The first time you run the solutions, look at the residuals very carefully before trying <code>short_hand</code>. Uncompress the postlog, postfit and postbreak files, and then use <code>allbadp</code> to check the pseudorange and <code>allbreaks</code> to check for major cycle slips.<br />
<br />
A very common problem is that for several stations per week, there will be one satellite arc of pseudorange data that all have residuals of roughly 2000 cm. If you see these, don't delete the data, but instead run del_pcode_arc to remove only the pseudorange data. I am not sure why these show up, but it could be either a hardware channel bias or a pre-processing glitch. They happen much more often with Ashtechs than any others, and are particuarly common with the US Coast Guard CORS sites. In the <code>qm</code> directory,<br />
<br />
<pre><br />
del_pcode_arc *02gus2* GUS2 GPS41<br />
</pre><br />
<br />
If you just run <code>short_hand</code> without looking, it will probably either throw out all the pseudorange for one site, or delete a lot of data (phase and pseudorange) where only the pseudorange needs to be deleted. So don't do that. Then I delete a batch of bad pseudorange data to get the number of pseudorange outliers under control for the next run.<br />
<br />
<pre><br />
cd $ANALYSIS/1381/flt<br />
gunzip *alaska*post*<br />
allbadp<br />
allbreaks<br />
# Based on this, run del_pcode_arc as above, and add ambiguities manually if needed.<br />
#<br />
delete_allbadp 50<br />
# This creates a file called delete.<br />
vi delete<br />
# Remove lines for any points for which you have already run del_pocde_arc.<br />
cd ../qm<br />
sh ../flt/delete<br />
</pre><br />
<br />
At this point, don't worry too much about phase outliers. Basically we are trying to get the number of pseudorange outliers down into the range where <code>short_hand</code> will do the right thing when we run it later. Now may be a good time to run <code>Alaska_cleaning_solution $date</code>, which runs a smaller and much faster solution including the sites that most often need some cleaning.<br />
<br />
===Data Backup===<br />
<br />
RINEX file backups.<br />
There are either 1 or 2 separate backups of the raw rinex files. For data we collected<br />
ourselves, a copy of the original rinex files can be found in either the campaign<br />
directory (/gps/akda/Campaigns/Data.2007/<project>, where <project> is the project name,<br />
and Data.2007 will change with the year), or in the continuous site ftp area<br />
(/gps/akda/Permanent/2007/260/, where 2007 is the year and 160 is the day of year). Also,<br />
every rinex file put through the hopper is moved to a directory like $RAWDATA/2007/260/<br />
(again, year and day of year may change). However, the $RAWDATA/2007/260/ directories are<br />
not really archived and eventually they will be deleted. But in practice we have most of<br />
the last few years of rinex files online in case something goes wrong.<br />
<br />
QM file backups.<br />
Before autoclean makes any changes to a qm file, it copies the file to a subdirectory<br />
called "original" in the qm directory. so if you completely destroy a qm file by<br />
accident, you can still go back the original version. Of course, that loses all editing<br />
done to the file, but at least the original data can be recovered easily. In general, it<br />
is not a good idea to go back to the version in the original subdirectory unless you know<br />
what you are doing, because doing that can make a lot more work for everyone. Mostly we<br />
do that when files have been mangled by autoclean. It is actually hard to mangle data<br />
files using our usual editing procedures.<br />
<br />
<br />
<br />
===Customized Solutions===<br />
<br />
Sometimes customized solutions are required for various reasons. This link will provide some strategies that may improve your situation.<br />
<br>[[Kinematic Processing]]<br />
<br>[[Ambiguity Resolution]]<br />
<br />
===Products / file contents===<br />
<br />
Where to find certain information and what are the structure / content of output files? It is started to be summarized on the [[files | files]] page.<br />
<br />
=== Velocity solutions ===<br />
<pre><br />
/> su akda<br />
/> cd $ANALYZED<br />
/> mkdir <USEFUL NEW PROJECTNAME><br />
</pre><br />
<br />
Find another project and copy the following files into your new directory:<br />
<br />
<pre><br />
/> cp *.nml $ANALYZED/new_project<br />
/> cp make_vel* $ANALYZED/new_project<br />
</pre><br />
<br />
Rename the *.nml file to something reasonable for your project and edit this file, it needs to know the stations that you want to include<br />
into your velocity solution as well as the input file locations where the data comes from. To get the input files in the correct syntax you might wanna use:<br />
<br />
<pre><br />
/> grep_vel_infiles.pl --from-week=WWWW --infile-index=x --sum-id=<alaska2.0_nfxigs03 | NEAsia2.0_nfxigs03 | ...><br />
</pre><br />
<br />
"WWWW" stands for the week you want to start with and "x" is the starting value for the id-counter. These id's are useful later to reference certain input files for additional editing purposes (see below). "sum-id" is basically the solution name. Copy all lines of the format " infile(x) = '...'" into your namelist (nml) file (insert before the &amp;end).<br />
<br />
Once the editing of the namelist file is finished:<br />
<br />
<pre><br />
/> refresh_zebu younamelist.nml outfile.ref<br />
</pre><br />
<br />
This is necessary to order and re-number the entries in your namelistfile which can contain comments. To not have you go through the namelist file whenever you want to try to throw out a station or some data and renumber everything, refresh_zebu does that for you.<br />
<br />
Once you have a nice reference file (.ref):<br />
<br />
<pre><br />
/> rzebu2 outfile.ref > & out<br />
</pre><br />
<br />
You should redirect the output to a file so you can look at it later :).<br />
<br />
For example right now. As soon as the solution is finished running, look at the total Chi_squared value at the bottom of the output in "out". It should be "1". If that's not the case which is likely if you run a solution for the first couple of times look for sites that cause the deviation from chi_squared=1. Note the site names with the larges chi squared values. Then you can do three things:<br />
<br />
<pre><br />
A) /> grep SITE outlier.inf<br />
B) /> grep SITE residual.inf<br />
C) /> vi $ANALYSIS/solution_timeseries/SITE.pfiles<br />
</pre><br />
<br />
In all three cases you want to find dates on which the sigmas for this site are rather large. Note down the date and find it in the namelist <br />
file (*.nml) and remove the respective site from the velocity solution for that day by adding a line:<br />
<br />
<pre><br />
removedat(a, infile_id) = 'SITENAME'<br />
</pre><br />
<br />
"a" is the id that simply counts how many removedats have been invoked on that one infile_id. "infile_id" is the counter I mentioned above. An example is probably best:<br />
<br />
<pre><br />
infile(161) = '/gps/analysis/1222/post/03jun10NEAsia2.0_nfxigs03.sum'<br />
removedat(1,161) = 'ELD '<br />
removedat(2,161) = 'PETP'<br />
</pre><br />
<br />
Here I assume that both sites, "ELD" and "PETP" misbehave on June 10, 2003 for the North East Asia solution. Hence I remove them from the velocity solution.<br />
<br />
Remove all the files created by <code>rzebu2</code>. Creating a Makefile of the form:<br />
<br />
<pre><br />
clean:<br />
rm *.ref ATWA ATY solution.* *.inf out nnr.* *.dat *.gmtvec *.vel fort.* gmt.format STACOV argus.weights<br />
</pre><br />
<br />
might be useful.<br />
<br />
Repeat the above until your reduced chi squared is <= 1.0. If you can't get there, change the fudge_factor as follows:<br />
<br />
<pre><br />
new_fudge = old_fudge * Chi_squared<br />
</pre><br />
<br />
and rerun the solution one last time. The reduced chi squared value should be 1.0 .<br />
<br />
Once you achieved that you can go to the next level and run one of the make_vel files you copied to your directory:<br />
<pre><br />
make_vel_Sella: velocities relative to a stable North America<br />
make_vel_ITRF: velocities in ITRF <br />
make_vel_EURA: velocities relative to a stable Eurasia <br />
make_vel_XXXX: velocities with reference station XXXX<br />
</pre><br />
<br />
There might be others, or you could go ahead and edit these files to adapt them to your needs. The make files create *.gmtvec output which you can use to with e.g., <code>psvelo</code> in a GMT script.</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=WHOS&diff=214WHOS2006-08-01T00:47:50Z<p>Jeff: /* Recent weeks */</p>
<hr />
<div>The WHOS list tracks assigned GPS weeks for processing.<br />
<br />
More details about analysis at [[GPS analysis system]].<br />
<br />
===Recent weeks===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
<br />
1374 05/07/2006 Venkat<br />
1375 05/14/2006 Trivikram/trivikram 1/<br />
1376 05/21/2006 Trivikram/trivikram 1/<br />
1377 05/28/2006 07/20/2006 Trivikram 1<br />
1378 06/04/2006 07/20/2006 Trivikram 1 <br />
1379 06/11/2006 07/20/2006 Trivikram 1 <br />
1380 06/18/2006 07/20/2006 Trivikram 1 <br />
1381 06/25/2006 07/12/2006 Ryan<br />
1382 07/02/2006 Julie<br />
1383 07/09/2006 Julie<br />
1384 07/16/2006 Julie<br />
1385 07/23/2006 Julie<br />
<br />
<br />
</pre><br />
<br />
===2006===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
1356 01/01/2006 Sandeep 1 2/Venkat<br />
1357 01/08/2006 Sandeep 1 2/Venkat<br />
1358 01/15/2006 Sandeep 1 2/Venkat<br />
1359 01/22/2006 Sandeep 1 2/Venkat<br />
1360 01/29/2006 Sandeep 1 2/Venkat<br />
1361 02/05/2006 Trivikram/sandeep 1/ trivikram 2/<br />
1362 02/12/2006 Trivikram/sandeep 1/ trivikram 2/ CLEAN except 06feb12<br />
1363 02/19/2006 Venkat CLEAN <br />
1364 02/26/2006 Trivikram/trivikram 1/<br />
1365 03/05/2006 Venkat<br />
1366 03/12/2006 Trivikram/trivikram 1/<br />
1367 03/19/2006 Trivikram/trivikram 1/<br />
1368 03/26/2006 Trivikram/trivikram 1/<br />
1369 04/02/2006 Trivikram/triivkram 1/<br />
1370 04/09/2006 Tom<br />
1371 04/16/2006 Venkat<br />
1372 04/23/2006 Venkat<br />
1373 04/30/2006 Venkat<br />
</pre><br />
<br />
===2005===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
1304 01/02/2005 09/16/2005 Ryan CLEAN<br />
1305 01/09/2005 08/30/2005 Pravee CLEAN<br />
1306 01/16/2005 07/15/2005 Jill WORKING Trivikram(tibet) 07/26/2006 CLEAN<br />
1307 01/23/2005 08/31/2005 Pravee CLEAN Trivikram(tibet) 07/26/2006 CLEAN<br />
1308 01/30/2005 04/05/2005 Jill CLEAN Trivikram(tibet) 07/26/2006 CLEAN<br />
1309 02/06/2005 08/31/2005 Pravee CLEAN<br />
1310 02/13/2005 03/12/2005 Julie CLEAN<br />
1311 02/20/2005 03/12/2005 Pravee CLEANING<br />
1312 02/27/2005 03/31/2005 Tom CLEAN<br />
1313 03/06/2005 03/31/2005 Pravee CLEANING<br />
1314 03/13/2005 03/31/2005 Tom CLEAN<br />
1315 03/20/2005 06/13/2005 Samik CLEAN pt file size<500<br />
1316 03/27/2005 06/13/2005 Samik CLEAN pt file size<400<br />
1317 04/03/2005 06/16/2005 Samik CLEAN pt file size<400<br />
1318 04/10/2005 9/15/2005 Ryan not sure what's going on?<br />
1319 04/17/2005 10/4/2005 Ryan ak SUBMITTED<br />
1347 10/30/2005 Sandeep Done 1/tr<br />
1320 04/24/2005 Sandeep Done 1 2 Trivikram(tibet) 07/27/2006 soln running<br />
1321 05/01/2005 Sandeep Done 1 2 Trivikram(tibet) 07/28/2006 soln running <br />
1322 05/08/2005 Sandeep Done 1 2 Trivikram(tibet) 07/28/2006<br />
1323 05/15/2005 Sandeep Done 1 2<br />
1324 05/22/2005 Sandeep Done 1 2<br />
1325 05/29/2005 Sigrun DONE <br />
1326 06/05/2005 Sigrun DONE<br />
1327 06/12/2005 Sandeep Done 1 2 <br />
1328 06/19/2005 Sandeep Done 1 2<br />
1329 06/26/2005 Sandeep Done 1 2 <br />
1330 07/03/2005 9/14/2005 Ryan DONE<br />
1331 07/10/2005 11/10/2005 Tom Submitted<br />
1332 07/17/2005 Sandeep CLEAN 1-2-3/Venkat (Point File Size < 500)<br />
1333 07/24/2005 Sandeep CLEAN 1-2-3/Trivikram<br />
1334 07/31/2005 Sandeep CLEAN 1-2-3/Trivikram <br />
1335 08/07/2005 9/12/2005 Tom Done 1<br />
1336 08/14/2005 Sandeep Done 1 2/Venkat<br />
1337 08/21/2005 10/17/2005 Ryan ak CLEAN pt file size<500<br />
1338 08/28/2005 10/17/2005 Ryan ak CLEAN<br />
1339 09/04/2005 11/08/2005 Ryan CLEAN 1-2-3/Trivikram<br />
1340 09/11/2005 Sandeep Done 1-2/Venkat<br />
1341 09/18/2005 Sandeep Done 1-2/Venkat <br />
1342 09/25/2005 Sandeep Done 1-2/Venkat<br />
1343 10/02/2005 Sandeep CLEAN 1-2-3/Venkat (Point File Size < 300)<br />
1344 10/09/2005 Sandeep Done 1-2/Venkat<br />
1345 10/16/2005 Sandeep Done 1-2/Venkat<br />
1346 10/23/2005 Sandeep Done 1-2/Venkat <br />
1347 10/30/2005 Sandeep Done 1-2/Venkat<br />
1348 11/06/2005 Sandeep Done 1-2/Venkat<br />
1349 11/13/2005 Sandeep Done 1-2/Venkat<br />
1350 11/20/2005 Sandeep Done 1-2/Venkat <br />
1351 11/27/2005 Sandeep Done 1-2/Venkat<br />
1352 12/04/2005 Sandeep Done 1 2/Venkat<br />
1353 12/11/2005 Sandeep Done 1 2/Venkat<br />
1354 12/18/2005 Sandeep Done 1 2/Venkat<br />
1356 12/25/2005 Sandeep Done 1 2/Venkat<br />
</pre><br />
<br />
===Older Stuff===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
****************************************************************<br />
***************************2002*********************************<br />
**************************EARTHQUAKE****************************<br />
1189 10/20/02 02/26/05 Josh PENDING<br />
1190 10/27/02 Josh PENDING<br />
1191 11/03/02 03/04/05 Josh DONE<br />
1192 11/10/02 03/11/05 Josh DONE<br />
1193 11/17/02 03/11/05 Josh DONE<br />
1194 11/24/02 03/11/05 Josh DONE<br />
1195 12/01/02 03/11/05 Josh RUNNING<br />
1196 12/08/02 03/11/05 Josh DONE<br />
1197 12/15/02 03/11/05 Josh DONE<br />
1198 12/22/02 03/12/05 Josh DONE<br />
1199 12/29/02 03/12/05 Josh DONE<br />
<br />
*************************2003***********************************<br />
<br />
1200 01/05/03 03/12/05 Josh DONE<br />
1201 01/12/03 03/12/05 Josh DONE<br />
1202 01/19/03 03/15/05 Josh RUNNING<br />
1203 01/26/03 03/14/05 Josh DONE<br />
1204 02/02/03 03/14/05 Josh DONE<br />
1205 02/09/03 Josh PENDING<br />
1206 02/16/03 Josh PENDING<br />
1207 02/23/03 Josh PENDING<br />
1208 03/02/03 02/26/05 Josh ALMOST CLEAN<br />
1209 03/09/03 02/26/05 Josh ALMOST CLEAN<br />
1210 03/16/03 02/26/05 Josh NEEDS CLEAN<br />
1211 03/23/03 02/27/05 Josh DONE<br />
1212 03/30/03 02/26/05 Josh DONE<br />
1213 04/06/03 03/12/05 Josh RUNNING<br />
1214 04/13/03 02/26/05 Josh CLEANED<br />
1215 04/20/03 02/27/05 Josh CLEANED<br />
1216 04/27/03 02/26/05 Josh PENDING<br />
1217 05/04/03 02/26/05 Josh NEEDS CLEAN<br />
1218 05/11/03 02/27/05 Josh NEEDS CLEAN<br />
1219 05/18/03 02/27/05 Josh WORKING<br />
1220 05/25/03 02/27/05 Josh PENDING<br />
1221 06/01/03 Josh PENDING<br />
1222 06/08/03 Josh PENDING<br />
1223 06/15/03 Josh PENDING<br />
1224 06/22/03 Josh PENDING<br />
1225 06/29/03 02/26/05 Josh FAILED<br />
1226 07/06/03 02/26/05 Josh ALMOST CLEAN<br />
1227 07/13/03 02/26/05 Josh FAILED<br />
1228 07/20/03 Josh FAILED<br />
1229 07/27/03 11/10/05 Tom Submitted <br />
1230 08/03/03 Josh FAILED<br />
1231 08/10/03 Josh FAILED<br />
1232 08/17/03 11/10/05 Tom Submitted <br />
1233 08/24/03 02/26/05 Josh ALMOST CLEAN<br />
1234 08/31/03 02/26/05 Josh ALMOST CLEAN<br />
1235 09/07/03 02/26/05 Josh ALMOST CLEAN<br />
1236 09/14/03 02/26/05 Josh ALMOST CLEAN<br />
1237 09/21/03 02/26/05 Josh NEEDS CLEAN<br />
1238 09/28/03 02/26/05 Josh NEEDS CLEAN<br />
1239 10/05/03 02/26/05 Josh WORKING<br />
1240 10/12/03 02/26/05 Josh PENDING<br />
1241 10/19/03 02/26/05 Josh NEEDS CLEAN<br />
1242 10/26/03 02/26/05 Josh ALMOST CLEAN<br />
1243 11/02/03 02/26/05 Josh NEEDS CLEAN<br />
1244 11/09/03 02/26/05 Josh NEEDS CLEAN<br />
1245 11/16/03 02/26/05 Josh ALMOST CLEAN<br />
1246 11/23/03 02/26/05 Josh ALMOST CLEAN<br />
1247 11/30/03 02/26/05 Josh ALMOST CLEAN<br />
1248 12/07/03 02/26/05 Josh NEEDS CLEAN<br />
1249 12/14/03 02/26/05 Josh NEEDS CLEAN<br />
1250 12/21/03 02/26/05 Josh NEEDS CLEAN<br />
1251 12/28/03 02/26/05 Josh WORKING<br />
<br />
***************************2004*********************************<br />
<br />
1253 01/11/04 02/26/05 Josh PENDING<br />
1254 01/18/04 Josh PENDING<br />
1255 01/25/04 Josh NEEDS<br />
1256 02/01/04 Josh PENDING<br />
1257 02/08/04 Josh PENDING<br />
1258 02/15/04 Josh PENDING<br />
1259 02/22/04 Josh PENDING<br />
1260 02/29/04 Josh PENDING<br />
1261 03/07/04 02/26/05 Josh PENDING<br />
1262 03/14/04 02/26/05 Josh NEEDS CLEAN<br />
1263 03/21/04 02/26/05 Josh NEEDS CLEAN<br />
1264 03/28/04 02/26/05 Josh NEEDS CLEAN<br />
1265 04/04/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1266 04/11/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1267 04/18/04 02/26/05 Josh NEEDS CLEAN<br />
1268 04/25/04 02/26/05 Josh NEEDS CLEAN<br />
1269 05/02/04 02/26/05 Josh NEEDS CLEAN<br />
1270 05/09/04 02/26/05 Josh NEEDS CLEAN<br />
1271 05/16/04 02/26/05 Josh NEEDS CLEAN<br />
1272 05/23/04 02/26/05 Josh NEEDS CLEAN<br />
1273 05/30/04 02/26/05 Josh NEEDS CLEAN<br />
1274 06/06/04 02/26/05 Josh NEEDS CLEAN<br />
1275 06/13/04 02/26/05 Josh NEEDS CLEAN<br />
1276 06/20/04 02/27/05 Samik DONE<br />
1277 06/27/04 03/19/05 Jeff NEEDS CLEAN<br />
1278 07/04/04 03/19/05 Jeff NEEDS CLEAN<br />
1279 07/11/04 03/19/05 Jeff NEEDS CLEAN<br />
1280 07/18/04 03/19/05 Jeff NEEDS CLEAN<br />
1281 07/25/04 03/19/05 Jeff NEEDS CLEAN<br />
1282 08/01/04 Josh PENDING<br />
1283 08/08/04 Josh PENDING<br />
1284 08/15/04 Josh PENDING<br />
1285 08/22/04 Josh PENDING<br />
1286 08/29/04 Josh PENDING<br />
1287 09/05/04 Josh PENDING<br />
1288 09/12/04 Josh PENDING<br />
1289 09/19/04 03/19/05 Jeff ??<br />
1290 09/26/04 Josh PENDING<br />
1291 10/03/04 Josh PENDING<br />
1292 10/10/04 03/19/05 Jeff ??<br />
1293 10/17/04 Josh PENDING<br />
1294 10/24/04 03/19/05 Jeff ??<br />
1295 10/31/04 03/25/05 Tom CLEAN<br />
1296 11/07/04 04/07/05 Tom Cleaning<br />
1297 11/14/04 03/19/05 Jeff ??<br />
1298 11/21/04 NEEDS CLEAN<br />
1299 11/28/04 NEEDS CLEAN<br />
1300 12/05/04 08/16/05 Pravee CLEAN<br />
1301 12/12/04 08/19/05 Pravee CLEAN<br />
1302 12/19/04 08/19/05 Pravee CLEAN trivikram(tibet) CLEAN 07/26/2006<br />
1303 12/26/04 08/26/05 Pravee CLEAN <br />
</pre><br />
<br />
</pre><br />
<br />
===Archaic (pre-1996)===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
At the moment, Jeff is dealing with these.<br />
</pre></div>Jeffhttp://gps.alaska.edu/internal/index.php?title=GPS_analysis_system&diff=291GPS analysis system2006-07-04T22:34:20Z<p>Jeff: </p>
<hr />
<div>We use a GPS data analysis system based on the [http://sideshow.jpl.nasa.gov 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.<br />
<br />
===Where do you put RINEX files?===<br />
RINEX files should be put into the hopper, <code>$RAWDATA/hopper</code>. 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 <code>autofront</code> and <code>autoclean</code> programs manually.<br />
<br />
===What happens automatically?===<br />
<br />
Quite a lot.<br />
<br />
Autoftp runs every night beginning at 6pm local time and fetches data files. These are placed into the '''hopper''' ($RAWDATA/hopper), a directory where all data files are put for entry into the system and processing. Autofront then runs at midnight to process all files in the hopper, including any placed there manually (from campaigns, for example). Finally, autoclean runs at 4am local to carry out automated screening for cycle slips and other bad data.<br />
<br />
====Autoftp====<br />
<br />
Autoftp is an efficient data-fetching tool that uses wget to automatically get data from any of several internet GPS data archives. It reads a list of desired sites from a ''request file'', which contains the date in the filename, and attempts to find and download data from as many sites as possible. It is intended to run automatically on a daily basis under cron, and when acccompanied by another simple program to generate a standard request file every day, it can easily fetch a standard set of sites on a daily basis for analysis. Because it keeps track in the request file of sites that it has found already, autoftp can be run multiple times with the same request file and it will not repeatedly fetch data. This is ideal for the real world, in which data from some sites are available rapidly while data from other sites may require many hours or days to become available.<br />
<br />
====Autofront====<br />
<br />
Autofront is a script intended to run under cron that carried out the initial "front end" processing on a set of GPS data files. When executed, it will process all files in the '''hopper''' directory, and will place each resulting qm file into the appropriate week directory.<br />
<br />
Autofront runs the following steps<br />
1. Checks on the validity of RINEX file and repair of some common problems.<br />
2. Depending on receiver type, clockprep -fixtags<br />
3. (optional, presently not default) PhasEdit<br />
4. ninja<br />
<br />
====Autoclean====<br />
<br />
Autoclean carries out automated cleaning of cycle slips, based on point positioning solutions. It is quite effective and at present it rarely misses cycle slips unless they are smaller than its minimum tolerance (10 cm). Autoclean operates on an ''edit-request'' file, which contains the name of the directory (week directory) and a list of qm files that need to be cleaned. It will clean all files on the list as long as orbits and clocks are available, and it marks off files that have been cleaned so that it can safely be run multiple times.<br />
<br />
Autoclean operates in an iterative mode. It's zeroth iteration is to do a pseudorange-only solution and identify and delete extremely bad pseudorange data. In this step it uses a tolerance that catches only grossly biased data. (Explain it). It then carries out 1 or more iterations of screening the phase data. In each iteration, it uses postbreak to identify discontinuities in the residuals of a point positioning solution. Postbreak is run with an adaptive tolerance (minimum 10 cm), and it is critical that my slightly modified version of postbreak be used. If any cycle slips are discovered, they are flagged and another iteration is run. Autoclean runs a maximum of 4 iterations on the phase data.<br />
<br />
===Where do the data files go?===<br />
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|week directory]] there are several subdirectories; qm files are stored in <code>$ANALYSIS/wwww/qm</code>, where <code>wwww</code> is the 4 character GPS week number (with a leading zero if needed).<br />
<br />
===Running Solutions===<br />
<br />
Solve, a very flexible script. (link to detailed help)<br />
<br />
Philosophy of solve<br />
<br />
Subnet files and campaign files<br />
<br />
Standard solutions<br />
<br />
(text of standard_Alaska_solution)<br />
<br />
Running several days at once: make-make-flt and make-alaska<br />
<br />
(text of a standard make-alaska file and variant)<br />
<br />
Running several weeks at once<br />
<br />
(text of sample rerun-* file)<br />
<br />
===Cleaning Solutions===<br />
<br />
Initial Explanation of terms<br />
<br />
Expected residuals from a clean solution<br />
<br />
Automated screening: postfit, the point file, postbreak<br />
<br />
Checking for bad pseudorange data: badp, allbadp<br />
<br />
Removing biased pseudorange data: del_pcode_arc<br />
<br />
Automatically identified cycle slips: breaks<br />
<br />
Quickly scanning through residuals: short_hand<br />
<br />
Limitations of short_hand<br />
<br />
Manually checking residuals and fixing problems (link)<br />
<br />
<br />
===Procedure for Running Solutions for a week for the first time===<br />
<br />
A few special things need to be done the very first time solutions in a week are run. First, you need to make up a script to run all days of the week. This may need to be edited if the JPL final orbits are not available at the time. The <code>standard_Alaska_solution</code> uses the non-fiducial orbits and thus requires that the final JPL orbits be present. If they are not, you can run <code>rapid_Alaska_solution</code> instead. <br />
<br />
Then, the log files from autoclean should be moved away to a subdirectory, and any problem stations identified by autoclean should be checked. Then, you are ready to run the solutions.<br />
<br />
First, make a script to run solutions. For example, to make a script to run all days of the week for the Alaska solution:<br />
<pre><br />
cd $ANALYSIS<br />
make-make-flt 1381<br />
cd 1381/flt<br />
vi make-alaska<br />
# Edit the file if needed so that you are ready to run the rapid solutions.<br />
<br />
cat make-alaska<br />
#!/bin/csh -f<br />
#<br />
setenv CAMP $ANALYSIS/1381<br />
#<br />
#standard_Alaska_solution 06jul01<br />
#standard_Alaska_solution 06jun25<br />
#standard_Alaska_solution 06jun26<br />
#standard_Alaska_solution 06jun27<br />
#standard_Alaska_solution 06jun28<br />
#standard_Alaska_solution 06jun29<br />
#standard_Alaska_solution 06jun30<br />
#<br />
rapid_Alaska_solution 06jul01<br />
rapid_Alaska_solution 06jun25<br />
rapid_Alaska_solution 06jun26<br />
rapid_Alaska_solution 06jun27<br />
rapid_Alaska_solution 06jun28<br />
rapid_Alaska_solution 06jun29<br />
rapid_Alaska_solution 06jun30<br />
<br />
</pre><br />
<br />
The script <code>make-make-flt</code> finds all unique dates for qm files in that week's directory, and uses that to generate the script, so if you run it before the end of the week you will get a partial script. If the final JPL orbits are not yet present, you will need to edit the script to change "standard" ro "rapid". Or better yet, copy all the lines and comment one set out, then modify the others to read "rapid_Alaska_solution <date>".<br />
<br />
Next, make a subdirectory called <code>logfiles</code>, and move all of autoclean's logfiles into it. You will need to use two separate <code>mv</code> commands because the list of files is too big for one.<br />
<br />
<pre><br />
mkdir logfiles<br />
mv *____*.i1* logfiles<br />
mv *____*.i* logfiles<br />
</pre><br />
<br />
Now look for a file called <code>make-problems</code>, which lists all files that autoclean had a problem with. Sometimes these files are almost clean, but sometimes they are full of junk or horribly mangled by the automated editing. There should be PPP solutions already run for these files, so they are ready to eb checked.<br />
<br />
Now run the solutions. The first time you run the solutions, look at the residuals very carefully before trying <code>short_hand</code>. Uncompress the postlog, postfit and postbreak files, and then use <code>allbadp</code> to check the pseudorange and <code>allbreaks</code> to check for major cycle slips.<br />
<br />
A very common problem is that for several stations per week, there will be one satellite arc of pseudorange data that all have residuals of roughly 2000 cm. If you see these, don't delete the data, but instead run del_pcode_arc to remove only the pseudorange data. I am not sure why these show up, but it could be either a hardware channel bias or a pre-processing glitch. They happen much more often with Ashtechs than any others, and are particuarly common with the US Coast Guard CORS sites. In the <code>qm</code> directory,<br />
<br />
<pre><br />
del_pcode_arc *02gus2* GUS2 GPS41<br />
</pre><br />
<br />
If you just run <code>short_hand</code> without looking, it will probably either throw out all the pseudorange for one site, or delete a lot of data (phase and pseudorange) where only the pseudorange needs to be deleted. So don't do that. Then I delete a batch of bad pseudorange data to get the number of pseudorange outliers under control for the next run.<br />
<br />
<pre><br />
cd $ANALYSIS/1381/flt<br />
gunzip *alaska*post*<br />
allbadp<br />
allbreaks<br />
# Based on this, run del_pcode_arc as above, and add ambiguities manually if needed.<br />
#<br />
delete_allbadp 50<br />
# This creates a file called delete.<br />
vi delete<br />
# Remove lines for any points for which you have already run del_pocde_arc.<br />
cd ../qm<br />
sh ../flt/delete<br />
</pre><br />
<br />
At this point, don't worry too much about phase outliers. Basically we are trying to get the number of pseudorange outliers down into the range where <code>short_hand</code> will do the right thing when we run it later. Now may be a good time to run <code>Alaska_cleaning_solution $date</code>, which runs a smaller and much faster solution including the sites that most often need some cleaning.</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=WHOS&diff=187WHOS2006-07-04T22:01:15Z<p>Jeff: /* 2006 */</p>
<hr />
<div>The WHOS list tracks assigned GPS weeks for processing.<br />
<br />
More details about analysis at [[GPS analysis system]].<br />
<br />
===Recent weeks===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
<br />
1374 05/07/2006 Venkat<br />
1375 05/14/2006 Trivikram<br />
1376 05/21/2006 Trivikram<br />
1377 05/28/2006 <br />
1378 06/04/2006 <br />
1379 06/11/2006 <br />
1380 06/18/2006 <br />
1381 06/25/2006 <br />
1382 07/02/2006 <br />
1383 07/09/2006 <br />
<br />
</pre><br />
<br />
===2006===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
1356 01/01/2006 <br />
1357 01/08/2006 <br />
1358 01/15/2006 <br />
1359 01/22/2006 Sandeep 1<br />
1360 01/29/2006 Sandeep 1<br />
1361 02/05/2006 Trivikram/sandeep 1/ trivikram 2/soln running<br />
1362 02/12/2006 Trivikram/sandeep 1/ trivikram 2/soln running<br />
1363 02/19/2006 Venkat CLEAN <br />
1364 02/26/2006 Trivikram/trivikram 1/<br />
1365 03/05/2006 Venkat<br />
1366 03/12/2006 Trivikram/trivikram 1/<br />
1367 03/19/2006 Trivikram/trivikram 1/<br />
1368 03/26/2006 Trivikram/trivikram 1/<br />
1369 04/02/2006 Trivikram<br />
1370 04/09/2006 Tom<br />
1371 04/16/2006 Venkat<br />
1372 04/23/2006 Venkat<br />
1373 04/30/2006 Venkat<br />
</pre><br />
<br />
===2005===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
1304 01/02/2005 09/16/2005 Ryan CLEAN<br />
1305 01/09/2005 08/30/2005 Pravee CLEAN<br />
1306 01/16/2005 07/15/2005 Jill WORKING<br />
1307 01/23/2005 08/31/2005 Pravee CLEAN<br />
1308 01/30/2005 04/05/2005 Jill CLEAN<br />
1309 02/06/2005 08/31/2005 Pravee CLEAN<br />
1310 02/13/2005 03/12/2005 Julie CLEAN<br />
1311 02/20/2005 03/12/2005 Pravee CLEANING<br />
1312 02/27/2005 03/31/2005 Tom CLEAN<br />
1313 03/06/2005 03/31/2005 Pravee CLEANING<br />
1314 03/13/2005 03/31/2005 Tom CLEAN<br />
1315 03/20/2005 06/13/2005 Samik CLEAN pt file size<500<br />
1316 03/27/2005 06/13/2005 Samik CLEAN pt file size<400<br />
1317 04/03/2005 06/16/2005 Samik CLEAN pt file size<400<br />
1318 04/10/2005 9/15/2005 Ryan not sure what's going on?<br />
1319 04/17/2005 10/4/2005 Ryan ak SUBMITTED<br />
1347 10/30/2005 Sandeep Done 1/tr<br />
1320 04/24/2005 Sandeep Done 1 2<br />
1321 05/01/2005 Sandeep Done 1 2<br />
1322 05/08/2005 Sandeep Done 1 2<br />
1323 05/15/2005 Sandeep Done 1 2<br />
1324 05/22/2005 Sandeep Done 1 2<br />
1325 05/29/2005 Sigrun DONE <br />
1326 06/05/2005 Sigrun DONE<br />
1327 06/12/2005 Sandeep Done 1 2 <br />
1328 06/19/2005 Sandeep Done 1 2<br />
1329 06/26/2005 Sandeep Done 1 2 <br />
1330 07/03/2005 9/14/2005 Ryan DONE<br />
1331 07/10/2005 11/10/2005 Tom Submitted<br />
1332 07/17/2005 Sandeep Done 1 2/Venkat<br />
1333 07/24/2005 Sandeep Done 1/trivikram soln running<br />
1334 07/31/2005 Sandeep Done 1/trivikram soln running <br />
1335 08/07/2005 9/12/2005 Tom Done 1/trivikram fatal error problem(2 days)<br />
1336 08/14/2005 Sandeep Done 1 2/Venkat<br />
1337 08/21/2005 10/17/2005 Ryan ak CLEAN pt file size<500<br />
1338 08/28/2005 10/17/2005 Ryan ak CLEAN<br />
1339 09/04/2005 11/08/2005 Ryan working on it /trivikram<br />
1340 09/11/2005 Sandeep Done 1-2/Venkat<br />
1341 09/18/2005 Sandeep Done 1-2/Venkat <br />
1342 09/25/2005 Sandeep Done 1-2/Venkat<br />
1343 10/02/2005 Sandeep CLEAN 1-2/Venkat<br />
1344 10/09/2005 Sandeep Done 1-2/Venkat<br />
1345 10/16/2005 Sandeep Done 1-2/Venkat<br />
1346 10/23/2005 Sandeep Done 1-2/Venkat <br />
1347 10/30/2005 Sandeep Done 1-2/Venkat<br />
1348 11/06/2005 Sandeep Done 1-2/Venkat<br />
1349 11/13/2005 Sandeep Done 1-2/Venkat<br />
1350 11/20/2005 Sandeep Done 1-2/Venkat <br />
1351 11/27/2005 Sandeep Done 1-2/Venkat<br />
1352 12/04/2005 Sandeep Done 1 2<br />
1353 12/11/2005 Sandeep Done 1 2<br />
1354 12/18/2005 Sandeep Done 1<br />
1356 12/25/2005 Sandeep Done 1<br />
</pre><br />
<br />
===Older Stuff===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
****************************************************************<br />
***************************2002*********************************<br />
**************************EARTHQUAKE****************************<br />
1189 10/20/02 02/26/05 Josh PENDING<br />
1190 10/27/02 Josh PENDING<br />
1191 11/03/02 03/04/05 Josh DONE<br />
1192 11/10/02 03/11/05 Josh DONE<br />
1193 11/17/02 03/11/05 Josh DONE<br />
1194 11/24/02 03/11/05 Josh DONE<br />
1195 12/01/02 03/11/05 Josh RUNNING<br />
1196 12/08/02 03/11/05 Josh DONE<br />
1197 12/15/02 03/11/05 Josh DONE<br />
1198 12/22/02 03/12/05 Josh DONE<br />
1199 12/29/02 03/12/05 Josh DONE<br />
<br />
*************************2003***********************************<br />
<br />
1200 01/05/03 03/12/05 Josh DONE<br />
1201 01/12/03 03/12/05 Josh DONE<br />
1202 01/19/03 03/15/05 Josh RUNNING<br />
1203 01/26/03 03/14/05 Josh DONE<br />
1204 02/02/03 03/14/05 Josh DONE<br />
1205 02/09/03 Josh PENDING<br />
1206 02/16/03 Josh PENDING<br />
1207 02/23/03 Josh PENDING<br />
1208 03/02/03 02/26/05 Josh ALMOST CLEAN<br />
1209 03/09/03 02/26/05 Josh ALMOST CLEAN<br />
1210 03/16/03 02/26/05 Josh NEEDS CLEAN<br />
1211 03/23/03 02/27/05 Josh DONE<br />
1212 03/30/03 02/26/05 Josh DONE<br />
1213 04/06/03 03/12/05 Josh RUNNING<br />
1214 04/13/03 02/26/05 Josh CLEANED<br />
1215 04/20/03 02/27/05 Josh CLEANED<br />
1216 04/27/03 02/26/05 Josh PENDING<br />
1217 05/04/03 02/26/05 Josh NEEDS CLEAN<br />
1218 05/11/03 02/27/05 Josh NEEDS CLEAN<br />
1219 05/18/03 02/27/05 Josh WORKING<br />
1220 05/25/03 02/27/05 Josh PENDING<br />
1221 06/01/03 Josh PENDING<br />
1222 06/08/03 Josh PENDING<br />
1223 06/15/03 Josh PENDING<br />
1224 06/22/03 Josh PENDING<br />
1225 06/29/03 02/26/05 Josh FAILED<br />
1226 07/06/03 02/26/05 Josh ALMOST CLEAN<br />
1227 07/13/03 02/26/05 Josh FAILED<br />
1228 07/20/03 Josh FAILED<br />
1229 07/27/03 11/10/05 Tom Submitted <br />
1230 08/03/03 Josh FAILED<br />
1231 08/10/03 Josh FAILED<br />
1232 08/17/03 11/10/05 Tom Submitted <br />
1233 08/24/03 02/26/05 Josh ALMOST CLEAN<br />
1234 08/31/03 02/26/05 Josh ALMOST CLEAN<br />
1235 09/07/03 02/26/05 Josh ALMOST CLEAN<br />
1236 09/14/03 02/26/05 Josh ALMOST CLEAN<br />
1237 09/21/03 02/26/05 Josh NEEDS CLEAN<br />
1238 09/28/03 02/26/05 Josh NEEDS CLEAN<br />
1239 10/05/03 02/26/05 Josh WORKING<br />
1240 10/12/03 02/26/05 Josh PENDING<br />
1241 10/19/03 02/26/05 Josh NEEDS CLEAN<br />
1242 10/26/03 02/26/05 Josh ALMOST CLEAN<br />
1243 11/02/03 02/26/05 Josh NEEDS CLEAN<br />
1244 11/09/03 02/26/05 Josh NEEDS CLEAN<br />
1245 11/16/03 02/26/05 Josh ALMOST CLEAN<br />
1246 11/23/03 02/26/05 Josh ALMOST CLEAN<br />
1247 11/30/03 02/26/05 Josh ALMOST CLEAN<br />
1248 12/07/03 02/26/05 Josh NEEDS CLEAN<br />
1249 12/14/03 02/26/05 Josh NEEDS CLEAN<br />
1250 12/21/03 02/26/05 Josh NEEDS CLEAN<br />
1251 12/28/03 02/26/05 Josh WORKING<br />
<br />
***************************2004*********************************<br />
<br />
1253 01/11/04 02/26/05 Josh PENDING<br />
1254 01/18/04 Josh PENDING<br />
1255 01/25/04 Josh NEEDS<br />
1256 02/01/04 Josh PENDING<br />
1257 02/08/04 Josh PENDING<br />
1258 02/15/04 Josh PENDING<br />
1259 02/22/04 Josh PENDING<br />
1260 02/29/04 Josh PENDING<br />
1261 03/07/04 02/26/05 Josh PENDING<br />
1262 03/14/04 02/26/05 Josh NEEDS CLEAN<br />
1263 03/21/04 02/26/05 Josh NEEDS CLEAN<br />
1264 03/28/04 02/26/05 Josh NEEDS CLEAN<br />
1265 04/04/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1266 04/11/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1267 04/18/04 02/26/05 Josh NEEDS CLEAN<br />
1268 04/25/04 02/26/05 Josh NEEDS CLEAN<br />
1269 05/02/04 02/26/05 Josh NEEDS CLEAN<br />
1270 05/09/04 02/26/05 Josh NEEDS CLEAN<br />
1271 05/16/04 02/26/05 Josh NEEDS CLEAN<br />
1272 05/23/04 02/26/05 Josh NEEDS CLEAN<br />
1273 05/30/04 02/26/05 Josh NEEDS CLEAN<br />
1274 06/06/04 02/26/05 Josh NEEDS CLEAN<br />
1275 06/13/04 02/26/05 Josh NEEDS CLEAN<br />
1276 06/20/04 02/27/05 Samik DONE<br />
1277 06/27/04 03/19/05 Jeff NEEDS CLEAN<br />
1278 07/04/04 03/19/05 Jeff NEEDS CLEAN<br />
1279 07/11/04 03/19/05 Jeff NEEDS CLEAN<br />
1280 07/18/04 03/19/05 Jeff NEEDS CLEAN<br />
1281 07/25/04 03/19/05 Jeff NEEDS CLEAN<br />
1282 08/01/04 Josh PENDING<br />
1283 08/08/04 Josh PENDING<br />
1284 08/15/04 Josh PENDING<br />
1285 08/22/04 Josh PENDING<br />
1286 08/29/04 Josh PENDING<br />
1287 09/05/04 Josh PENDING<br />
1288 09/12/04 Josh PENDING<br />
1289 09/19/04 03/19/05 Jeff ??<br />
1290 09/26/04 Josh PENDING<br />
1291 10/03/04 Josh PENDING<br />
1292 10/10/04 03/19/05 Jeff ??<br />
1293 10/17/04 Josh PENDING<br />
1294 10/24/04 03/19/05 Jeff ??<br />
1295 10/31/04 03/25/05 Tom CLEAN<br />
1296 11/07/04 04/07/05 Tom Cleaning<br />
1297 11/14/04 03/19/05 Jeff ??<br />
1298 11/21/04 NEEDS CLEAN<br />
1299 11/28/04 NEEDS CLEAN<br />
1300 12/05/04 08/16/05 Pravee CLEAN<br />
1301 12/12/04 08/19/05 Pravee CLEAN<br />
1302 12/19/04 08/19/05 Pravee CLEAN<br />
1303 12/26/04 08/26/05 Pravee CLEAN<br />
</pre><br />
<br />
</pre><br />
<br />
===Archaic (pre-1996)===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
At the moment, Jeff is dealing with these.<br />
</pre></div>Jeffhttp://gps.alaska.edu/internal/index.php?title=WHOS&diff=185WHOS2006-07-04T22:00:14Z<p>Jeff: /* 2006 */</p>
<hr />
<div>The WHOS list tracks assigned GPS weeks for processing.<br />
<br />
More details about analysis at [[GPS analysis system]].<br />
<br />
===Recent weeks===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
<br />
1374 05/07/2006 Venkat<br />
1375 05/14/2006 Trivikram<br />
1376 05/21/2006 Trivikram<br />
1377 05/28/2006 <br />
1378 06/04/2006 <br />
1379 06/11/2006 <br />
1380 06/18/2006 <br />
1381 06/25/2006 <br />
1382 07/02/2006 <br />
1383 07/09/2006 <br />
<br />
</pre><br />
<br />
===2006===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
1357<br />
1358<br />
1359 01/22/2006 Sandeep 1<br />
1360 01/29/2006 Sandeep 1<br />
1361 02/05/2006 Trivikram/sandeep 1/ trivikram 2/soln running<br />
1362 02/12/2006 Trivikram/sandeep 1/ trivikram 2/soln running<br />
1363 02/19/2006 Venkat CLEAN <br />
1364 02/26/2006 Trivikram/trivikram 1/<br />
1365 03/05/2006 Venkat<br />
1366 03/12/2006 Trivikram/trivikram 1/<br />
1367 03/19/2006 Trivikram/trivikram 1/<br />
1368 03/26/2006 Trivikram/trivikram 1/<br />
1369 04/02/2006 Trivikram<br />
1370 04/09/2006 Tom<br />
1371 04/16/2006 Venkat<br />
1372 04/23/2006 Venkat<br />
1373 04/30/2006 Venkat<br />
</pre><br />
<br />
===2005===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
1304 01/02/2005 09/16/2005 Ryan CLEAN<br />
1305 01/09/2005 08/30/2005 Pravee CLEAN<br />
1306 01/16/2005 07/15/2005 Jill WORKING<br />
1307 01/23/2005 08/31/2005 Pravee CLEAN<br />
1308 01/30/2005 04/05/2005 Jill CLEAN<br />
1309 02/06/2005 08/31/2005 Pravee CLEAN<br />
1310 02/13/2005 03/12/2005 Julie CLEAN<br />
1311 02/20/2005 03/12/2005 Pravee CLEANING<br />
1312 02/27/2005 03/31/2005 Tom CLEAN<br />
1313 03/06/2005 03/31/2005 Pravee CLEANING<br />
1314 03/13/2005 03/31/2005 Tom CLEAN<br />
1315 03/20/2005 06/13/2005 Samik CLEAN pt file size<500<br />
1316 03/27/2005 06/13/2005 Samik CLEAN pt file size<400<br />
1317 04/03/2005 06/16/2005 Samik CLEAN pt file size<400<br />
1318 04/10/2005 9/15/2005 Ryan not sure what's going on?<br />
1319 04/17/2005 10/4/2005 Ryan ak SUBMITTED<br />
1347 10/30/2005 Sandeep Done 1/tr<br />
1320 04/24/2005 Sandeep Done 1 2<br />
1321 05/01/2005 Sandeep Done 1 2<br />
1322 05/08/2005 Sandeep Done 1 2<br />
1323 05/15/2005 Sandeep Done 1 2<br />
1324 05/22/2005 Sandeep Done 1 2<br />
1325 05/29/2005 Sigrun DONE <br />
1326 06/05/2005 Sigrun DONE<br />
1327 06/12/2005 Sandeep Done 1 2 <br />
1328 06/19/2005 Sandeep Done 1 2<br />
1329 06/26/2005 Sandeep Done 1 2 <br />
1330 07/03/2005 9/14/2005 Ryan DONE<br />
1331 07/10/2005 11/10/2005 Tom Submitted<br />
1332 07/17/2005 Sandeep Done 1 2/Venkat<br />
1333 07/24/2005 Sandeep Done 1/trivikram soln running<br />
1334 07/31/2005 Sandeep Done 1/trivikram soln running <br />
1335 08/07/2005 9/12/2005 Tom Done 1/trivikram fatal error problem(2 days)<br />
1336 08/14/2005 Sandeep Done 1 2/Venkat<br />
1337 08/21/2005 10/17/2005 Ryan ak CLEAN pt file size<500<br />
1338 08/28/2005 10/17/2005 Ryan ak CLEAN<br />
1339 09/04/2005 11/08/2005 Ryan working on it /trivikram<br />
1340 09/11/2005 Sandeep Done 1-2/Venkat<br />
1341 09/18/2005 Sandeep Done 1-2/Venkat <br />
1342 09/25/2005 Sandeep Done 1-2/Venkat<br />
1343 10/02/2005 Sandeep CLEAN 1-2/Venkat<br />
1344 10/09/2005 Sandeep Done 1-2/Venkat<br />
1345 10/16/2005 Sandeep Done 1-2/Venkat<br />
1346 10/23/2005 Sandeep Done 1-2/Venkat <br />
1347 10/30/2005 Sandeep Done 1-2/Venkat<br />
1348 11/06/2005 Sandeep Done 1-2/Venkat<br />
1349 11/13/2005 Sandeep Done 1-2/Venkat<br />
1350 11/20/2005 Sandeep Done 1-2/Venkat <br />
1351 11/27/2005 Sandeep Done 1-2/Venkat<br />
1352 12/04/2005 Sandeep Done 1 2<br />
1353 12/11/2005 Sandeep Done 1 2<br />
1354 12/18/2005 Sandeep Done 1<br />
1356 12/25/2005 Sandeep Done 1<br />
</pre><br />
<br />
===Older Stuff===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
****************************************************************<br />
***************************2002*********************************<br />
**************************EARTHQUAKE****************************<br />
1189 10/20/02 02/26/05 Josh PENDING<br />
1190 10/27/02 Josh PENDING<br />
1191 11/03/02 03/04/05 Josh DONE<br />
1192 11/10/02 03/11/05 Josh DONE<br />
1193 11/17/02 03/11/05 Josh DONE<br />
1194 11/24/02 03/11/05 Josh DONE<br />
1195 12/01/02 03/11/05 Josh RUNNING<br />
1196 12/08/02 03/11/05 Josh DONE<br />
1197 12/15/02 03/11/05 Josh DONE<br />
1198 12/22/02 03/12/05 Josh DONE<br />
1199 12/29/02 03/12/05 Josh DONE<br />
<br />
*************************2003***********************************<br />
<br />
1200 01/05/03 03/12/05 Josh DONE<br />
1201 01/12/03 03/12/05 Josh DONE<br />
1202 01/19/03 03/15/05 Josh RUNNING<br />
1203 01/26/03 03/14/05 Josh DONE<br />
1204 02/02/03 03/14/05 Josh DONE<br />
1205 02/09/03 Josh PENDING<br />
1206 02/16/03 Josh PENDING<br />
1207 02/23/03 Josh PENDING<br />
1208 03/02/03 02/26/05 Josh ALMOST CLEAN<br />
1209 03/09/03 02/26/05 Josh ALMOST CLEAN<br />
1210 03/16/03 02/26/05 Josh NEEDS CLEAN<br />
1211 03/23/03 02/27/05 Josh DONE<br />
1212 03/30/03 02/26/05 Josh DONE<br />
1213 04/06/03 03/12/05 Josh RUNNING<br />
1214 04/13/03 02/26/05 Josh CLEANED<br />
1215 04/20/03 02/27/05 Josh CLEANED<br />
1216 04/27/03 02/26/05 Josh PENDING<br />
1217 05/04/03 02/26/05 Josh NEEDS CLEAN<br />
1218 05/11/03 02/27/05 Josh NEEDS CLEAN<br />
1219 05/18/03 02/27/05 Josh WORKING<br />
1220 05/25/03 02/27/05 Josh PENDING<br />
1221 06/01/03 Josh PENDING<br />
1222 06/08/03 Josh PENDING<br />
1223 06/15/03 Josh PENDING<br />
1224 06/22/03 Josh PENDING<br />
1225 06/29/03 02/26/05 Josh FAILED<br />
1226 07/06/03 02/26/05 Josh ALMOST CLEAN<br />
1227 07/13/03 02/26/05 Josh FAILED<br />
1228 07/20/03 Josh FAILED<br />
1229 07/27/03 11/10/05 Tom Submitted <br />
1230 08/03/03 Josh FAILED<br />
1231 08/10/03 Josh FAILED<br />
1232 08/17/03 11/10/05 Tom Submitted <br />
1233 08/24/03 02/26/05 Josh ALMOST CLEAN<br />
1234 08/31/03 02/26/05 Josh ALMOST CLEAN<br />
1235 09/07/03 02/26/05 Josh ALMOST CLEAN<br />
1236 09/14/03 02/26/05 Josh ALMOST CLEAN<br />
1237 09/21/03 02/26/05 Josh NEEDS CLEAN<br />
1238 09/28/03 02/26/05 Josh NEEDS CLEAN<br />
1239 10/05/03 02/26/05 Josh WORKING<br />
1240 10/12/03 02/26/05 Josh PENDING<br />
1241 10/19/03 02/26/05 Josh NEEDS CLEAN<br />
1242 10/26/03 02/26/05 Josh ALMOST CLEAN<br />
1243 11/02/03 02/26/05 Josh NEEDS CLEAN<br />
1244 11/09/03 02/26/05 Josh NEEDS CLEAN<br />
1245 11/16/03 02/26/05 Josh ALMOST CLEAN<br />
1246 11/23/03 02/26/05 Josh ALMOST CLEAN<br />
1247 11/30/03 02/26/05 Josh ALMOST CLEAN<br />
1248 12/07/03 02/26/05 Josh NEEDS CLEAN<br />
1249 12/14/03 02/26/05 Josh NEEDS CLEAN<br />
1250 12/21/03 02/26/05 Josh NEEDS CLEAN<br />
1251 12/28/03 02/26/05 Josh WORKING<br />
<br />
***************************2004*********************************<br />
<br />
1253 01/11/04 02/26/05 Josh PENDING<br />
1254 01/18/04 Josh PENDING<br />
1255 01/25/04 Josh NEEDS<br />
1256 02/01/04 Josh PENDING<br />
1257 02/08/04 Josh PENDING<br />
1258 02/15/04 Josh PENDING<br />
1259 02/22/04 Josh PENDING<br />
1260 02/29/04 Josh PENDING<br />
1261 03/07/04 02/26/05 Josh PENDING<br />
1262 03/14/04 02/26/05 Josh NEEDS CLEAN<br />
1263 03/21/04 02/26/05 Josh NEEDS CLEAN<br />
1264 03/28/04 02/26/05 Josh NEEDS CLEAN<br />
1265 04/04/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1266 04/11/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1267 04/18/04 02/26/05 Josh NEEDS CLEAN<br />
1268 04/25/04 02/26/05 Josh NEEDS CLEAN<br />
1269 05/02/04 02/26/05 Josh NEEDS CLEAN<br />
1270 05/09/04 02/26/05 Josh NEEDS CLEAN<br />
1271 05/16/04 02/26/05 Josh NEEDS CLEAN<br />
1272 05/23/04 02/26/05 Josh NEEDS CLEAN<br />
1273 05/30/04 02/26/05 Josh NEEDS CLEAN<br />
1274 06/06/04 02/26/05 Josh NEEDS CLEAN<br />
1275 06/13/04 02/26/05 Josh NEEDS CLEAN<br />
1276 06/20/04 02/27/05 Samik DONE<br />
1277 06/27/04 03/19/05 Jeff NEEDS CLEAN<br />
1278 07/04/04 03/19/05 Jeff NEEDS CLEAN<br />
1279 07/11/04 03/19/05 Jeff NEEDS CLEAN<br />
1280 07/18/04 03/19/05 Jeff NEEDS CLEAN<br />
1281 07/25/04 03/19/05 Jeff NEEDS CLEAN<br />
1282 08/01/04 Josh PENDING<br />
1283 08/08/04 Josh PENDING<br />
1284 08/15/04 Josh PENDING<br />
1285 08/22/04 Josh PENDING<br />
1286 08/29/04 Josh PENDING<br />
1287 09/05/04 Josh PENDING<br />
1288 09/12/04 Josh PENDING<br />
1289 09/19/04 03/19/05 Jeff ??<br />
1290 09/26/04 Josh PENDING<br />
1291 10/03/04 Josh PENDING<br />
1292 10/10/04 03/19/05 Jeff ??<br />
1293 10/17/04 Josh PENDING<br />
1294 10/24/04 03/19/05 Jeff ??<br />
1295 10/31/04 03/25/05 Tom CLEAN<br />
1296 11/07/04 04/07/05 Tom Cleaning<br />
1297 11/14/04 03/19/05 Jeff ??<br />
1298 11/21/04 NEEDS CLEAN<br />
1299 11/28/04 NEEDS CLEAN<br />
1300 12/05/04 08/16/05 Pravee CLEAN<br />
1301 12/12/04 08/19/05 Pravee CLEAN<br />
1302 12/19/04 08/19/05 Pravee CLEAN<br />
1303 12/26/04 08/26/05 Pravee CLEAN<br />
</pre><br />
<br />
</pre><br />
<br />
===Archaic (pre-1996)===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
At the moment, Jeff is dealing with these.<br />
</pre></div>Jeffhttp://gps.alaska.edu/internal/index.php?title=WHOS&diff=184WHOS2006-07-04T21:58:53Z<p>Jeff: /* Recent weeks */</p>
<hr />
<div>The WHOS list tracks assigned GPS weeks for processing.<br />
<br />
More details about analysis at [[GPS analysis system]].<br />
<br />
===Recent weeks===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
<br />
1374 05/07/2006 Venkat<br />
1375 05/14/2006 Trivikram<br />
1376 05/21/2006 Trivikram<br />
1377 05/28/2006 <br />
1378 06/04/2006 <br />
1379 06/11/2006 <br />
1380 06/18/2006 <br />
1381 06/25/2006 <br />
1382 07/02/2006 <br />
1383 07/09/2006 <br />
<br />
</pre><br />
<br />
===2006===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
1357<br />
1358<br />
1359 1/22/2006 Sandeep<br />
1360 1/29/2006 Sandeep<br />
1361 2/05/2006 Trivikram<br />
1362 2/12/2006 Trivikram<br />
1363 2/19/2006 Venkat CLEAN <br />
1364 2/26/2006 Trivikram <br />
1365 3/05/2006 Venkat<br />
1366 3/12/2006 Trivikram<br />
1367 3/19/2006 Trivikram<br />
1368 3/26/2006 Trivikram<br />
1369 4/02/2006 06/08/06 Trivikram <br />
1370 04/09/2006 05/31/2006 Tom running<br />
1371 4/16/2006 Venkat<br />
1372 4/23/2006 Venkat<br />
1373 4/30/2006 Venkat<br />
1374 5/07/2006 Venkat<br />
1375 5/14/2006 Trivikram<br />
1376 5/21/2006 Trivikram<br />
1377 <br />
1378 <br />
1379<br />
1380<br />
</pre><br />
<br />
===2005===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
1304 01/02/2005 09/16/2005 Ryan CLEAN<br />
1305 01/09/2005 08/30/2005 Pravee CLEAN<br />
1306 01/16/2005 07/15/2005 Jill WORKING<br />
1307 01/23/2005 08/31/2005 Pravee CLEAN<br />
1308 01/30/2005 04/05/2005 Jill CLEAN<br />
1309 02/06/2005 08/31/2005 Pravee CLEAN<br />
1310 02/13/2005 03/12/2005 Julie CLEAN<br />
1311 02/20/2005 03/12/2005 Pravee CLEANING<br />
1312 02/27/2005 03/31/2005 Tom CLEAN<br />
1313 03/06/2005 03/31/2005 Pravee CLEANING<br />
1314 03/13/2005 03/31/2005 Tom CLEAN<br />
1315 03/20/2005 06/13/2005 Samik CLEAN pt file size<500<br />
1316 03/27/2005 06/13/2005 Samik CLEAN pt file size<400<br />
1317 04/03/2005 06/16/2005 Samik CLEAN pt file size<400<br />
1318 04/10/2005 9/15/2005 Ryan not sure what's going on?<br />
1319 04/17/2005 10/4/2005 Ryan ak SUBMITTED<br />
1347 10/30/2005 Sandeep Done 1/tr<br />
1320 04/24/2005 Sandeep Done 1 2<br />
1321 05/01/2005 Sandeep Done 1 2<br />
1322 05/08/2005 Sandeep Done 1 2<br />
1323 05/15/2005 Sandeep Done 1 2<br />
1324 05/22/2005 Sandeep Done 1 2<br />
1325 05/29/2005 Sigrun DONE <br />
1326 06/05/2005 Sigrun DONE<br />
1327 06/12/2005 Sandeep Done 1 2 <br />
1328 06/19/2005 Sandeep Done 1 2<br />
1329 06/26/2005 Sandeep Done 1 2 <br />
1330 07/03/2005 9/14/2005 Ryan DONE<br />
1331 07/10/2005 11/10/2005 Tom Submitted<br />
1332 07/17/2005 Sandeep Done 1 2/Venkat<br />
1333 07/24/2005 Sandeep Done 1/trivikram soln running<br />
1334 07/31/2005 Sandeep Done 1/trivikram soln running <br />
1335 08/07/2005 9/12/2005 Tom Done 1/trivikram fatal error problem(2 days)<br />
1336 08/14/2005 Sandeep Done 1 2/Venkat<br />
1337 08/21/2005 10/17/2005 Ryan ak CLEAN pt file size<500<br />
1338 08/28/2005 10/17/2005 Ryan ak CLEAN<br />
1339 09/04/2005 11/08/2005 Ryan working on it /trivikram<br />
1340 09/11/2005 Sandeep Done 1-2/Venkat<br />
1341 09/18/2005 Sandeep Done 1-2/Venkat <br />
1342 09/25/2005 Sandeep Done 1-2/Venkat<br />
1343 10/02/2005 Sandeep CLEAN 1-2/Venkat<br />
1344 10/09/2005 Sandeep Done 1-2/Venkat<br />
1345 10/16/2005 Sandeep Done 1-2/Venkat<br />
1346 10/23/2005 Sandeep Done 1-2/Venkat <br />
1347 10/30/2005 Sandeep Done 1-2/Venkat<br />
1348 11/06/2005 Sandeep Done 1-2/Venkat<br />
1349 11/13/2005 Sandeep Done 1-2/Venkat<br />
1350 11/20/2005 Sandeep Done 1-2/Venkat <br />
1351 11/27/2005 Sandeep Done 1-2/Venkat<br />
1352 12/04/2005 Sandeep Done 1 2<br />
1353 12/11/2005 Sandeep Done 1 2<br />
1354 12/18/2005 Sandeep Done 1<br />
1356 12/25/2005 Sandeep Done 1<br />
</pre><br />
<br />
===Older Stuff===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
****************************************************************<br />
***************************2002*********************************<br />
**************************EARTHQUAKE****************************<br />
1189 10/20/02 02/26/05 Josh PENDING<br />
1190 10/27/02 Josh PENDING<br />
1191 11/03/02 03/04/05 Josh DONE<br />
1192 11/10/02 03/11/05 Josh DONE<br />
1193 11/17/02 03/11/05 Josh DONE<br />
1194 11/24/02 03/11/05 Josh DONE<br />
1195 12/01/02 03/11/05 Josh RUNNING<br />
1196 12/08/02 03/11/05 Josh DONE<br />
1197 12/15/02 03/11/05 Josh DONE<br />
1198 12/22/02 03/12/05 Josh DONE<br />
1199 12/29/02 03/12/05 Josh DONE<br />
<br />
*************************2003***********************************<br />
<br />
1200 01/05/03 03/12/05 Josh DONE<br />
1201 01/12/03 03/12/05 Josh DONE<br />
1202 01/19/03 03/15/05 Josh RUNNING<br />
1203 01/26/03 03/14/05 Josh DONE<br />
1204 02/02/03 03/14/05 Josh DONE<br />
1205 02/09/03 Josh PENDING<br />
1206 02/16/03 Josh PENDING<br />
1207 02/23/03 Josh PENDING<br />
1208 03/02/03 02/26/05 Josh ALMOST CLEAN<br />
1209 03/09/03 02/26/05 Josh ALMOST CLEAN<br />
1210 03/16/03 02/26/05 Josh NEEDS CLEAN<br />
1211 03/23/03 02/27/05 Josh DONE<br />
1212 03/30/03 02/26/05 Josh DONE<br />
1213 04/06/03 03/12/05 Josh RUNNING<br />
1214 04/13/03 02/26/05 Josh CLEANED<br />
1215 04/20/03 02/27/05 Josh CLEANED<br />
1216 04/27/03 02/26/05 Josh PENDING<br />
1217 05/04/03 02/26/05 Josh NEEDS CLEAN<br />
1218 05/11/03 02/27/05 Josh NEEDS CLEAN<br />
1219 05/18/03 02/27/05 Josh WORKING<br />
1220 05/25/03 02/27/05 Josh PENDING<br />
1221 06/01/03 Josh PENDING<br />
1222 06/08/03 Josh PENDING<br />
1223 06/15/03 Josh PENDING<br />
1224 06/22/03 Josh PENDING<br />
1225 06/29/03 02/26/05 Josh FAILED<br />
1226 07/06/03 02/26/05 Josh ALMOST CLEAN<br />
1227 07/13/03 02/26/05 Josh FAILED<br />
1228 07/20/03 Josh FAILED<br />
1229 07/27/03 11/10/05 Tom Submitted <br />
1230 08/03/03 Josh FAILED<br />
1231 08/10/03 Josh FAILED<br />
1232 08/17/03 11/10/05 Tom Submitted <br />
1233 08/24/03 02/26/05 Josh ALMOST CLEAN<br />
1234 08/31/03 02/26/05 Josh ALMOST CLEAN<br />
1235 09/07/03 02/26/05 Josh ALMOST CLEAN<br />
1236 09/14/03 02/26/05 Josh ALMOST CLEAN<br />
1237 09/21/03 02/26/05 Josh NEEDS CLEAN<br />
1238 09/28/03 02/26/05 Josh NEEDS CLEAN<br />
1239 10/05/03 02/26/05 Josh WORKING<br />
1240 10/12/03 02/26/05 Josh PENDING<br />
1241 10/19/03 02/26/05 Josh NEEDS CLEAN<br />
1242 10/26/03 02/26/05 Josh ALMOST CLEAN<br />
1243 11/02/03 02/26/05 Josh NEEDS CLEAN<br />
1244 11/09/03 02/26/05 Josh NEEDS CLEAN<br />
1245 11/16/03 02/26/05 Josh ALMOST CLEAN<br />
1246 11/23/03 02/26/05 Josh ALMOST CLEAN<br />
1247 11/30/03 02/26/05 Josh ALMOST CLEAN<br />
1248 12/07/03 02/26/05 Josh NEEDS CLEAN<br />
1249 12/14/03 02/26/05 Josh NEEDS CLEAN<br />
1250 12/21/03 02/26/05 Josh NEEDS CLEAN<br />
1251 12/28/03 02/26/05 Josh WORKING<br />
<br />
***************************2004*********************************<br />
<br />
1253 01/11/04 02/26/05 Josh PENDING<br />
1254 01/18/04 Josh PENDING<br />
1255 01/25/04 Josh NEEDS<br />
1256 02/01/04 Josh PENDING<br />
1257 02/08/04 Josh PENDING<br />
1258 02/15/04 Josh PENDING<br />
1259 02/22/04 Josh PENDING<br />
1260 02/29/04 Josh PENDING<br />
1261 03/07/04 02/26/05 Josh PENDING<br />
1262 03/14/04 02/26/05 Josh NEEDS CLEAN<br />
1263 03/21/04 02/26/05 Josh NEEDS CLEAN<br />
1264 03/28/04 02/26/05 Josh NEEDS CLEAN<br />
1265 04/04/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1266 04/11/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1267 04/18/04 02/26/05 Josh NEEDS CLEAN<br />
1268 04/25/04 02/26/05 Josh NEEDS CLEAN<br />
1269 05/02/04 02/26/05 Josh NEEDS CLEAN<br />
1270 05/09/04 02/26/05 Josh NEEDS CLEAN<br />
1271 05/16/04 02/26/05 Josh NEEDS CLEAN<br />
1272 05/23/04 02/26/05 Josh NEEDS CLEAN<br />
1273 05/30/04 02/26/05 Josh NEEDS CLEAN<br />
1274 06/06/04 02/26/05 Josh NEEDS CLEAN<br />
1275 06/13/04 02/26/05 Josh NEEDS CLEAN<br />
1276 06/20/04 02/27/05 Samik DONE<br />
1277 06/27/04 03/19/05 Jeff NEEDS CLEAN<br />
1278 07/04/04 03/19/05 Jeff NEEDS CLEAN<br />
1279 07/11/04 03/19/05 Jeff NEEDS CLEAN<br />
1280 07/18/04 03/19/05 Jeff NEEDS CLEAN<br />
1281 07/25/04 03/19/05 Jeff NEEDS CLEAN<br />
1282 08/01/04 Josh PENDING<br />
1283 08/08/04 Josh PENDING<br />
1284 08/15/04 Josh PENDING<br />
1285 08/22/04 Josh PENDING<br />
1286 08/29/04 Josh PENDING<br />
1287 09/05/04 Josh PENDING<br />
1288 09/12/04 Josh PENDING<br />
1289 09/19/04 03/19/05 Jeff ??<br />
1290 09/26/04 Josh PENDING<br />
1291 10/03/04 Josh PENDING<br />
1292 10/10/04 03/19/05 Jeff ??<br />
1293 10/17/04 Josh PENDING<br />
1294 10/24/04 03/19/05 Jeff ??<br />
1295 10/31/04 03/25/05 Tom CLEAN<br />
1296 11/07/04 04/07/05 Tom Cleaning<br />
1297 11/14/04 03/19/05 Jeff ??<br />
1298 11/21/04 NEEDS CLEAN<br />
1299 11/28/04 NEEDS CLEAN<br />
1300 12/05/04 08/16/05 Pravee CLEAN<br />
1301 12/12/04 08/19/05 Pravee CLEAN<br />
1302 12/19/04 08/19/05 Pravee CLEAN<br />
1303 12/26/04 08/26/05 Pravee CLEAN<br />
</pre><br />
<br />
</pre><br />
<br />
===Archaic (pre-1996)===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
At the moment, Jeff is dealing with these.<br />
</pre></div>Jeffhttp://gps.alaska.edu/internal/index.php?title=GPS_analysis_system&diff=186GPS analysis system2006-05-20T13:55:14Z<p>Jeff: /* What happens automatically? */</p>
<hr />
<div>We use a GPS data analysis system based on the [http://sideshow.jpl.nasa.gov 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.<br />
<br />
===Where do you put RINEX files?===<br />
RINEX files should be put into the hopper, <code>$RAWDATA/hopper</code>. 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 <code>autofront</code> and <code>autoclean</code> programs manually.<br />
<br />
===What happens automatically?===<br />
<br />
Quite a lot.<br />
<br />
Autoftp runs every night beginning at 6pm local time and fetches data files. These are placed into the '''hopper''' ($RAWDATA/hopper), a directory where all data files are put for entry into the system and processing. Autofront then runs at midnight to process all files in the hopper, including any placed there manually (from campaigns, for example). Finally, autoclean runs at 4am local to carry out automated screening for cycle slips and other bad data.<br />
<br />
====Autoftp====<br />
<br />
Autoftp is an efficient data-fetching tool that uses wget to automatically get data from any of several internet GPS data archives. It reads a list of desired sites from a ''request file'', which contains the date in the filename, and attempts to find and download data from as many sites as possible. It is intended to run automatically on a daily basis under cron, and when acccompanied by another simple program to generate a standard request file every day, it can easily fetch a standard set of sites on a daily basis for analysis. Because it keeps track in the request file of sites that it has found already, autoftp can be run multiple times with the same request file and it will not repeatedly fetch data. This is ideal for the real world, in which data from some sites are available rapidly while data from other sites may require many hours or days to become available.<br />
<br />
====Autofront====<br />
<br />
Autofront is a script intended to run under cron that carried out the initial "front end" processing on a set of GPS data files. When executed, it will process all files in the '''hopper''' directory, and will place each resulting qm file into the appropriate week directory.<br />
<br />
Autofront runs the following steps<br />
1. Checks on the validity of RINEX file and repair of some common problems.<br />
2. Depending on receiver type, clockprep -fixtags<br />
3. (optional, presently not default) PhasEdit<br />
4. ninja<br />
<br />
====Autoclean====<br />
<br />
Autoclean carries out automated cleaning of cycle slips, based on point positioning solutions. It is quite effective and at present it rarely misses cycle slips unless they are smaller than its minimum tolerance (10 cm). Autoclean operates on an ''edit-request'' file, which contains the name of the directory (week directory) and a list of qm files that need to be cleaned. It will clean all files on the list as long as orbits and clocks are available, and it marks off files that have been cleaned so that it can safely be run multiple times.<br />
<br />
Autoclean operates in an iterative mode. It's zeroth iteration is to do a pseudorange-only solution and identify and delete extremely bad pseudorange data. In this step it uses a tolerance that catches only grossly biased data. (Explain it). It then carries out 1 or more iterations of screening the phase data. In each iteration, it uses postbreak to identify discontinuities in the residuals of a point positioning solution. Postbreak is run with an adaptive tolerance (minimum 10 cm), and it is critical that my slightly modified version of postbreak be used. If any cycle slips are discovered, they are flagged and another iteration is run. Autoclean runs a maximum of 4 iterations on the phase data.<br />
<br />
===Where do the data files go?===<br />
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|week directory]] there are several subdirectories; qm files are stored in <code>$ANALYSIS/wwww/qm</code>, where <code>wwww</code> is the 4 character GPS week number (with a leading zero if needed).<br />
<br />
===Running Solutions===<br />
<br />
Solve, a very flexible script. (link to detailed help)<br />
<br />
Philosophy of solve<br />
<br />
Subnet files and campaign files<br />
<br />
Standard solutions<br />
<br />
(text of standard_Alaska_solution)<br />
<br />
Running several days at once: make-make-flt and make-alaska<br />
<br />
(text of a standard make-alaska file and variant)<br />
<br />
Running several weeks at once<br />
<br />
(text of sample rerun-* file)<br />
<br />
===Cleaning Solutions===<br />
<br />
Initial Explanation of terms<br />
<br />
Expected residuals from a clean solution<br />
<br />
Automated screening: postfit, the point file, postbreak<br />
<br />
Checking for bad pseudorange data: badp, allbadp<br />
<br />
Removing biased pseudorange data: del_pcode_arc<br />
<br />
Automatically identified cycle slips: breaks<br />
<br />
Quickly scanning through residuals: short_hand<br />
<br />
Limitations of short_hand<br />
<br />
Manually checking residuals and fixing problems (link)</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=GPS_analysis_system&diff=42GPS analysis system2006-05-20T13:46:17Z<p>Jeff: /* Autofront */</p>
<hr />
<div>We use a GPS data analysis system based on the [http://sideshow.jpl.nasa.gov 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.<br />
<br />
===Where do you put RINEX files?===<br />
RINEX files should be put into the hopper, <code>$RAWDATA/hopper</code>. 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 <code>autofront</code> and <code>autoclean</code> programs manually.<br />
<br />
===What happens automatically?===<br />
<br />
====Autoftp====<br />
<br />
Autoftp is an efficient data-fetching tool that uses wget to automatically get data from any of several internet GPS data archives. It reads a list of desired sites from a ''request file'', which contains the date in the filename, and attempts to find and download data from as many sites as possible. It is intended to run automatically on a daily basis under cron, and when acccompanied by another simple program to generate a standard request file every day, it can easily fetch a standard set of sites on a daily basis for analysis. Because it keeps track in the request file of sites that it has found already, autoftp can be run multiple times with the same request file and it will not repeatedly fetch data. This is ideal for the real world, in which data from some sites are available rapidly while data from other sites may require many hours or days to become available.<br />
<br />
====Autofront====<br />
<br />
Autofront is a script intended to run under cron that carried out the initial "front end" processing on a set of GPS data files. When executed, it will process all files in the '''hopper''' directory, and will place each resulting qm file into the appropriate week directory.<br />
<br />
Autofront runs the following steps<br />
1. Checks on the validity of RINEX file and repair of some common problems.<br />
2. Depending on receiver type, clockprep -fixtags<br />
3. (optional, presently not default) PhasEdit<br />
4. ninja<br />
<br />
====Autoclean====<br />
<br />
<br />
===Where do the data files go?===<br />
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|week directory]] there are several subdirectories; qm files are stored in <code>$ANALYSIS/wwww/qm</code>, where <code>wwww</code> is the 4 character GPS week number (with a leading zero if needed).<br />
<br />
===Running Solutions===<br />
<br />
Solve, a very flexible script. (link to detailed help)<br />
<br />
Philosophy of solve<br />
<br />
Subnet files and campaign files<br />
<br />
Standard solutions<br />
<br />
(text of standard_Alaska_solution)<br />
<br />
Running several days at once: make-make-flt and make-alaska<br />
<br />
(text of a standard make-alaska file and variant)<br />
<br />
Running several weeks at once<br />
<br />
(text of sample rerun-* file)<br />
<br />
===Cleaning Solutions===<br />
<br />
Initial Explanation of terms<br />
<br />
Expected residuals from a clean solution<br />
<br />
Automated screening: postfit, the point file, postbreak<br />
<br />
Checking for bad pseudorange data: badp, allbadp<br />
<br />
Removing biased pseudorange data: del_pcode_arc<br />
<br />
Automatically identified cycle slips: breaks<br />
<br />
Quickly scanning through residuals: short_hand<br />
<br />
Limitations of short_hand<br />
<br />
Manually checking residuals and fixing problems (link)</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=GPS_analysis_system&diff=41GPS analysis system2006-05-20T13:41:42Z<p>Jeff: /* Autoftp */</p>
<hr />
<div>We use a GPS data analysis system based on the [http://sideshow.jpl.nasa.gov 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.<br />
<br />
===Where do you put RINEX files?===<br />
RINEX files should be put into the hopper, <code>$RAWDATA/hopper</code>. 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 <code>autofront</code> and <code>autoclean</code> programs manually.<br />
<br />
===What happens automatically?===<br />
<br />
====Autoftp====<br />
<br />
Autoftp is an efficient data-fetching tool that uses wget to automatically get data from any of several internet GPS data archives. It reads a list of desired sites from a ''request file'', which contains the date in the filename, and attempts to find and download data from as many sites as possible. It is intended to run automatically on a daily basis under cron, and when acccompanied by another simple program to generate a standard request file every day, it can easily fetch a standard set of sites on a daily basis for analysis. Because it keeps track in the request file of sites that it has found already, autoftp can be run multiple times with the same request file and it will not repeatedly fetch data. This is ideal for the real world, in which data from some sites are available rapidly while data from other sites may require many hours or days to become available.<br />
<br />
====Autofront====<br />
<br />
====Autoclean====<br />
<br />
<br />
===Where do the data files go?===<br />
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|week directory]] there are several subdirectories; qm files are stored in <code>$ANALYSIS/wwww/qm</code>, where <code>wwww</code> is the 4 character GPS week number (with a leading zero if needed).<br />
<br />
===Running Solutions===<br />
<br />
Solve, a very flexible script. (link to detailed help)<br />
<br />
Philosophy of solve<br />
<br />
Subnet files and campaign files<br />
<br />
Standard solutions<br />
<br />
(text of standard_Alaska_solution)<br />
<br />
Running several days at once: make-make-flt and make-alaska<br />
<br />
(text of a standard make-alaska file and variant)<br />
<br />
Running several weeks at once<br />
<br />
(text of sample rerun-* file)<br />
<br />
===Cleaning Solutions===<br />
<br />
Initial Explanation of terms<br />
<br />
Expected residuals from a clean solution<br />
<br />
Automated screening: postfit, the point file, postbreak<br />
<br />
Checking for bad pseudorange data: badp, allbadp<br />
<br />
Removing biased pseudorange data: del_pcode_arc<br />
<br />
Automatically identified cycle slips: breaks<br />
<br />
Quickly scanning through residuals: short_hand<br />
<br />
Limitations of short_hand<br />
<br />
Manually checking residuals and fixing problems (link)</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=GPS_analysis_system&diff=40GPS analysis system2006-05-20T13:35:31Z<p>Jeff: /* Running Solutions */</p>
<hr />
<div>We use a GPS data analysis system based on the [http://sideshow.jpl.nasa.gov 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.<br />
<br />
===Where do you put RINEX files?===<br />
RINEX files should be put into the hopper, <code>$RAWDATA/hopper</code>. 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 <code>autofront</code> and <code>autoclean</code> programs manually.<br />
<br />
===What happens automatically?===<br />
<br />
====Autoftp====<br />
<br />
====Autofront====<br />
<br />
====Autoclean====<br />
<br />
<br />
===Where do the data files go?===<br />
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|week directory]] there are several subdirectories; qm files are stored in <code>$ANALYSIS/wwww/qm</code>, where <code>wwww</code> is the 4 character GPS week number (with a leading zero if needed).<br />
<br />
===Running Solutions===<br />
<br />
Solve, a very flexible script. (link to detailed help)<br />
<br />
Philosophy of solve<br />
<br />
Subnet files and campaign files<br />
<br />
Standard solutions<br />
<br />
(text of standard_Alaska_solution)<br />
<br />
Running several days at once: make-make-flt and make-alaska<br />
<br />
(text of a standard make-alaska file and variant)<br />
<br />
Running several weeks at once<br />
<br />
(text of sample rerun-* file)<br />
<br />
===Cleaning Solutions===<br />
<br />
Initial Explanation of terms<br />
<br />
Expected residuals from a clean solution<br />
<br />
Automated screening: postfit, the point file, postbreak<br />
<br />
Checking for bad pseudorange data: badp, allbadp<br />
<br />
Removing biased pseudorange data: del_pcode_arc<br />
<br />
Automatically identified cycle slips: breaks<br />
<br />
Quickly scanning through residuals: short_hand<br />
<br />
Limitations of short_hand<br />
<br />
Manually checking residuals and fixing problems (link)</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=GPS_analysis_system&diff=39GPS analysis system2006-05-20T13:30:40Z<p>Jeff: /* Cleaning Solutions */</p>
<hr />
<div>We use a GPS data analysis system based on the [http://sideshow.jpl.nasa.gov 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.<br />
<br />
===Where do you put RINEX files?===<br />
RINEX files should be put into the hopper, <code>$RAWDATA/hopper</code>. 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 <code>autofront</code> and <code>autoclean</code> programs manually.<br />
<br />
===What happens automatically?===<br />
<br />
====Autoftp====<br />
<br />
====Autofront====<br />
<br />
====Autoclean====<br />
<br />
<br />
===Where do the data files go?===<br />
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|week directory]] there are several subdirectories; qm files are stored in <code>$ANALYSIS/wwww/qm</code>, where <code>wwww</code> is the 4 character GPS week number (with a leading zero if needed).<br />
<br />
===Running Solutions===<br />
<br />
<br />
===Cleaning Solutions===<br />
<br />
Initial Explanation of terms<br />
<br />
Expected residuals from a clean solution<br />
<br />
Automated screening: postfit, the point file, postbreak<br />
<br />
Checking for bad pseudorange data: badp, allbadp<br />
<br />
Removing biased pseudorange data: del_pcode_arc<br />
<br />
Automatically identified cycle slips: breaks<br />
<br />
Quickly scanning through residuals: short_hand<br />
<br />
Limitations of short_hand<br />
<br />
Manually checking residuals and fixing problems (link)</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=WHOS&diff=43WHOS2006-05-19T21:16:03Z<p>Jeff: /* Recent weeks */</p>
<hr />
<div>The WHOS list tracks assigned GPS weeks for processing.<br />
<br />
More details about analysis at [[GPS analysis system]].<br />
<br />
===Recent weeks===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
1321 05/01/2005 Jill<br />
1322 05/08/2005 Jill<br />
1323 05/15/2005 Jill<br />
1324 05/22/2005 Julie<br />
1325 05/29/2005 Sigrun DONE <br />
1326 06/05/2005 Sigrun DONE<br />
1327 06/12/2005 Sigrun<br />
1328 06/19/2005 Tom<br />
1329 06/26/2005 Tom<br />
1330 07/03/2005 9/14/2005 Ryan ak CLEAN pt file size<500<br />
1331 07/10/2005 11/10/2005 Tom Submitted<br />
1332 07/17/2005 Samik<br />
1333 07/24/2005 Julie<br />
1334 07/31/2005 Jill<br />
1335 08/07/2005 9/12/2005 Tom SUBMITTED<br />
1336 08/14/2005 Jill<br />
1337 08/21/2005 10/17/2005 Ryan ak CLEAN pt file size<500<br />
1338 08/28/2005 10/17/2005 Ryan ak CLEAN<br />
1339 09/04/2005 11/08/2005 Ryan working on it<br />
1340 09/11/2005 Julie<br />
1341 09/18/2005 Julie<br />
1342 09/25/2005 Tom<br />
1343 10/02/2005 Tom<br />
1344 10/09/2005 Tom<br />
1345 10/16/2005 01/10/06 Ryan Working on it<br />
1346 10/23/2005 (nobody)<br />
<br />
(skipping some weeks)<br />
<br />
1359 1/22/2006 Sandeep<br />
1360 1/29/2006 Sandeep<br />
1361 2/05/2006 Trivikram<br />
1362 2/12/2006 Venkat<br />
<br />
(skipping some weeks)<br />
<br />
1374 10/23/2005 (nobody)<br />
<br />
</pre><br />
<br />
===2005===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
week # start date last processed who status<br />
1304 01/02/2005 09/16/2005 Ryan CLEAN<br />
1305 01/09/2005 08/30/2005 Pravee CLEAN<br />
1306 01/16/2005 07/15/2005 Jill WORKING<br />
1307 01/23/2005 08/31/2005 Pravee CLEAN<br />
1308 01/30/2005 04/05/2005 Jill CLEAN<br />
1309 02/06/2005 08/31/2005 Pravee CLEAN<br />
1310 02/13/2005 03/12/2005 Julie CLEAN<br />
1311 02/20/2005 03/12/2005 Pravee CLEANING<br />
1312 02/27/2005 03/31/2005 Tom CLEAN<br />
1313 03/06/2005 03/31/2005 Pravee CLEANING<br />
1314 03/13/2005 03/31/2005 Tom CLEAN<br />
1315 03/20/2005 06/13/2005 Samik CLEAN pt file size<500<br />
1316 03/27/2005 06/13/2005 Samik CLEAN pt file size<400<br />
1317 04/03/2005 06/16/2005 Samik CLEAN pt file size<400<br />
1318 04/10/2005 9/15/2005 Ryan not sure what's going on?<br />
1319 04/17/2005 10/4/2005 Ryan ak SUBMITTED<br />
1320 04/24/2005 Jill<br />
</pre><br />
<br />
===Older Stuff===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
****************************************************************<br />
***************************2002*********************************<br />
**************************EARTHQUAKE****************************<br />
1189 10/20/02 02/26/05 Josh PENDING<br />
1190 10/27/02 Josh PENDING<br />
1191 11/03/02 03/04/05 Josh DONE<br />
1192 11/10/02 03/11/05 Josh DONE<br />
1193 11/17/02 03/11/05 Josh DONE<br />
1194 11/24/02 03/11/05 Josh DONE<br />
1195 12/01/02 03/11/05 Josh RUNNING<br />
1196 12/08/02 03/11/05 Josh DONE<br />
1197 12/15/02 03/11/05 Josh DONE<br />
1198 12/22/02 03/12/05 Josh DONE<br />
1199 12/29/02 03/12/05 Josh DONE<br />
<br />
*************************2003***********************************<br />
<br />
1200 01/05/03 03/12/05 Josh DONE<br />
1201 01/12/03 03/12/05 Josh DONE<br />
1202 01/19/03 03/15/05 Josh RUNNING<br />
1203 01/26/03 03/14/05 Josh DONE<br />
1204 02/02/03 03/14/05 Josh DONE<br />
1205 02/09/03 Josh PENDING<br />
1206 02/16/03 Josh PENDING<br />
1207 02/23/03 Josh PENDING<br />
1208 03/02/03 02/26/05 Josh ALMOST CLEAN<br />
1209 03/09/03 02/26/05 Josh ALMOST CLEAN<br />
1210 03/16/03 02/26/05 Josh NEEDS CLEAN<br />
1211 03/23/03 02/27/05 Josh DONE<br />
1212 03/30/03 02/26/05 Josh DONE<br />
1213 04/06/03 03/12/05 Josh RUNNING<br />
1214 04/13/03 02/26/05 Josh CLEANED<br />
1215 04/20/03 02/27/05 Josh CLEANED<br />
1216 04/27/03 02/26/05 Josh PENDING<br />
1217 05/04/03 02/26/05 Josh NEEDS CLEAN<br />
1218 05/11/03 02/27/05 Josh NEEDS CLEAN<br />
1219 05/18/03 02/27/05 Josh WORKING<br />
1220 05/25/03 02/27/05 Josh PENDING<br />
1221 06/01/03 Josh PENDING<br />
1222 06/08/03 Josh PENDING<br />
1223 06/15/03 Josh PENDING<br />
1224 06/22/03 Josh PENDING<br />
1225 06/29/03 02/26/05 Josh FAILED<br />
1226 07/06/03 02/26/05 Josh ALMOST CLEAN<br />
1227 07/13/03 02/26/05 Josh FAILED<br />
1228 07/20/03 Josh FAILED<br />
1229 07/27/03 11/10/05 Tom Submitted <br />
1230 08/03/03 Josh FAILED<br />
1231 08/10/03 Josh FAILED<br />
1232 08/17/03 11/10/05 Tom Submitted <br />
1233 08/24/03 02/26/05 Josh ALMOST CLEAN<br />
1234 08/31/03 02/26/05 Josh ALMOST CLEAN<br />
1235 09/07/03 02/26/05 Josh ALMOST CLEAN<br />
1236 09/14/03 02/26/05 Josh ALMOST CLEAN<br />
1237 09/21/03 02/26/05 Josh NEEDS CLEAN<br />
1238 09/28/03 02/26/05 Josh NEEDS CLEAN<br />
1239 10/05/03 02/26/05 Josh WORKING<br />
1240 10/12/03 02/26/05 Josh PENDING<br />
1241 10/19/03 02/26/05 Josh NEEDS CLEAN<br />
1242 10/26/03 02/26/05 Josh ALMOST CLEAN<br />
1243 11/02/03 02/26/05 Josh NEEDS CLEAN<br />
1244 11/09/03 02/26/05 Josh NEEDS CLEAN<br />
1245 11/16/03 02/26/05 Josh ALMOST CLEAN<br />
1246 11/23/03 02/26/05 Josh ALMOST CLEAN<br />
1247 11/30/03 02/26/05 Josh ALMOST CLEAN<br />
1248 12/07/03 02/26/05 Josh NEEDS CLEAN<br />
1249 12/14/03 02/26/05 Josh NEEDS CLEAN<br />
1250 12/21/03 02/26/05 Josh NEEDS CLEAN<br />
1251 12/28/03 02/26/05 Josh WORKING<br />
<br />
***************************2004*********************************<br />
<br />
1253 01/11/04 02/26/05 Josh PENDING<br />
1254 01/18/04 Josh PENDING<br />
1255 01/25/04 Josh NEEDS<br />
1256 02/01/04 Josh PENDING<br />
1257 02/08/04 Josh PENDING<br />
1258 02/15/04 Josh PENDING<br />
1259 02/22/04 Josh PENDING<br />
1260 02/29/04 Josh PENDING<br />
1261 03/07/04 02/26/05 Josh PENDING<br />
1262 03/14/04 02/26/05 Josh NEEDS CLEAN<br />
1263 03/21/04 02/26/05 Josh NEEDS CLEAN<br />
1264 03/28/04 02/26/05 Josh NEEDS CLEAN<br />
1265 04/04/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1266 04/11/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1267 04/18/04 02/26/05 Josh NEEDS CLEAN<br />
1268 04/25/04 02/26/05 Josh NEEDS CLEAN<br />
1269 05/02/04 02/26/05 Josh NEEDS CLEAN<br />
1270 05/09/04 02/26/05 Josh NEEDS CLEAN<br />
1271 05/16/04 02/26/05 Josh NEEDS CLEAN<br />
1272 05/23/04 02/26/05 Josh NEEDS CLEAN<br />
1273 05/30/04 02/26/05 Josh NEEDS CLEAN<br />
1274 06/06/04 02/26/05 Josh NEEDS CLEAN<br />
1275 06/13/04 02/26/05 Josh NEEDS CLEAN<br />
1276 06/20/04 02/27/05 Samik DONE<br />
1277 06/27/04 03/19/05 Jeff NEEDS CLEAN<br />
1278 07/04/04 03/19/05 Jeff NEEDS CLEAN<br />
1279 07/11/04 03/19/05 Jeff NEEDS CLEAN<br />
1280 07/18/04 03/19/05 Jeff NEEDS CLEAN<br />
1281 07/25/04 03/19/05 Jeff NEEDS CLEAN<br />
1282 08/01/04 Josh PENDING<br />
1283 08/08/04 Josh PENDING<br />
1284 08/15/04 Josh PENDING<br />
1285 08/22/04 Josh PENDING<br />
1286 08/29/04 Josh PENDING<br />
1287 09/05/04 Josh PENDING<br />
1288 09/12/04 Josh PENDING<br />
1289 09/19/04 03/19/05 Jeff ??<br />
1290 09/26/04 Josh PENDING<br />
1291 10/03/04 Josh PENDING<br />
1292 10/10/04 03/19/05 Jeff ??<br />
1293 10/17/04 Josh PENDING<br />
1294 10/24/04 03/19/05 Jeff ??<br />
1295 10/31/04 03/25/05 Tom CLEAN<br />
1296 11/07/04 04/07/05 Tom Cleaning<br />
1297 11/14/04 03/19/05 Jeff ??<br />
1298 11/21/04 NEEDS CLEAN<br />
1299 11/28/04 NEEDS CLEAN<br />
1300 12/05/04 08/16/05 Pravee CLEAN<br />
1301 12/12/04 08/19/05 Pravee CLEAN<br />
1302 12/19/04 08/19/05 Pravee CLEAN<br />
1303 12/26/04 08/26/05 Pravee CLEAN<br />
</pre><br />
<br />
</pre><br />
<br />
===Archaic (pre-1996)===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
At the moment, Jeff is dealing with these.<br />
</pre></div>Jeffhttp://gps.alaska.edu/internal/index.php?title=WHOS&diff=37WHOS2006-05-19T20:47:25Z<p>Jeff: /* Older Stuff */</p>
<hr />
<div>The WHOS list tracks assigned GPS weeks for processing.<br />
<br />
More details about analysis at [[GPS analysis system]].<br />
<br />
===Recent weeks===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
1321 05/01/2005 Jill<br />
1322 05/08/2005 Jill<br />
1323 05/15/2005 Jill<br />
1324 05/22/2005 Julie<br />
1325 05/29/2005 Sigrun DONE <br />
1326 06/05/2005 Sigrun DONE<br />
1327 06/12/2005 Sigrun<br />
1328 06/19/2005 Tom<br />
1329 06/26/2005 Tom<br />
1330 07/03/2005 9/14/2005 Ryan ak CLEAN pt file size<500<br />
1331 07/10/2005 11/10/2005 Tom Submitted<br />
1332 07/17/2005 Samik<br />
1333 07/24/2005 Julie<br />
1334 07/31/2005 Jill<br />
1335 08/07/2005 9/12/2005 Tom SUBMITTED<br />
1336 08/14/2005 Jill<br />
1337 08/21/2005 10/17/2005 Ryan ak CLEAN pt file size<500<br />
1338 08/28/2005 10/17/2005 Ryan ak CLEAN<br />
1339 09/04/2005 11/08/2005 Ryan working on it<br />
1340 09/11/2005 Julie<br />
1341 09/18/2005 Julie<br />
1342 09/25/2005 Tom<br />
1343 10/02/2005 Tom<br />
1344 10/09/2005 Tom<br />
1345 10/16/2005 01/10/06 Ryan Working on it<br />
1346 10/23/2005 (nobody)<br />
<br />
(skipping some weeks)<br />
<br />
1360 1/29/2006 Sandeep<br />
1361 2/05/2006 Trivikram<br />
1362 2/12/2006 Venkat<br />
<br />
(skipping some weeks)<br />
<br />
1374 10/23/2005 (nobody)<br />
<br />
</pre><br />
<br />
===2005===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
week # start date last processed who status<br />
1304 01/02/2005 09/16/2005 Ryan CLEAN<br />
1305 01/09/2005 08/30/2005 Pravee CLEAN<br />
1306 01/16/2005 07/15/2005 Jill WORKING<br />
1307 01/23/2005 08/31/2005 Pravee CLEAN<br />
1308 01/30/2005 04/05/2005 Jill CLEAN<br />
1309 02/06/2005 08/31/2005 Pravee CLEAN<br />
1310 02/13/2005 03/12/2005 Julie CLEAN<br />
1311 02/20/2005 03/12/2005 Pravee CLEANING<br />
1312 02/27/2005 03/31/2005 Tom CLEAN<br />
1313 03/06/2005 03/31/2005 Pravee CLEANING<br />
1314 03/13/2005 03/31/2005 Tom CLEAN<br />
1315 03/20/2005 06/13/2005 Samik CLEAN pt file size<500<br />
1316 03/27/2005 06/13/2005 Samik CLEAN pt file size<400<br />
1317 04/03/2005 06/16/2005 Samik CLEAN pt file size<400<br />
1318 04/10/2005 9/15/2005 Ryan not sure what's going on?<br />
1319 04/17/2005 10/4/2005 Ryan ak SUBMITTED<br />
1320 04/24/2005 Jill<br />
</pre><br />
<br />
===Older Stuff===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
****************************************************************<br />
***************************2002*********************************<br />
**************************EARTHQUAKE****************************<br />
1189 10/20/02 02/26/05 Josh PENDING<br />
1190 10/27/02 Josh PENDING<br />
1191 11/03/02 03/04/05 Josh DONE<br />
1192 11/10/02 03/11/05 Josh DONE<br />
1193 11/17/02 03/11/05 Josh DONE<br />
1194 11/24/02 03/11/05 Josh DONE<br />
1195 12/01/02 03/11/05 Josh RUNNING<br />
1196 12/08/02 03/11/05 Josh DONE<br />
1197 12/15/02 03/11/05 Josh DONE<br />
1198 12/22/02 03/12/05 Josh DONE<br />
1199 12/29/02 03/12/05 Josh DONE<br />
<br />
*************************2003***********************************<br />
<br />
1200 01/05/03 03/12/05 Josh DONE<br />
1201 01/12/03 03/12/05 Josh DONE<br />
1202 01/19/03 03/15/05 Josh RUNNING<br />
1203 01/26/03 03/14/05 Josh DONE<br />
1204 02/02/03 03/14/05 Josh DONE<br />
1205 02/09/03 Josh PENDING<br />
1206 02/16/03 Josh PENDING<br />
1207 02/23/03 Josh PENDING<br />
1208 03/02/03 02/26/05 Josh ALMOST CLEAN<br />
1209 03/09/03 02/26/05 Josh ALMOST CLEAN<br />
1210 03/16/03 02/26/05 Josh NEEDS CLEAN<br />
1211 03/23/03 02/27/05 Josh DONE<br />
1212 03/30/03 02/26/05 Josh DONE<br />
1213 04/06/03 03/12/05 Josh RUNNING<br />
1214 04/13/03 02/26/05 Josh CLEANED<br />
1215 04/20/03 02/27/05 Josh CLEANED<br />
1216 04/27/03 02/26/05 Josh PENDING<br />
1217 05/04/03 02/26/05 Josh NEEDS CLEAN<br />
1218 05/11/03 02/27/05 Josh NEEDS CLEAN<br />
1219 05/18/03 02/27/05 Josh WORKING<br />
1220 05/25/03 02/27/05 Josh PENDING<br />
1221 06/01/03 Josh PENDING<br />
1222 06/08/03 Josh PENDING<br />
1223 06/15/03 Josh PENDING<br />
1224 06/22/03 Josh PENDING<br />
1225 06/29/03 02/26/05 Josh FAILED<br />
1226 07/06/03 02/26/05 Josh ALMOST CLEAN<br />
1227 07/13/03 02/26/05 Josh FAILED<br />
1228 07/20/03 Josh FAILED<br />
1229 07/27/03 11/10/05 Tom Submitted <br />
1230 08/03/03 Josh FAILED<br />
1231 08/10/03 Josh FAILED<br />
1232 08/17/03 11/10/05 Tom Submitted <br />
1233 08/24/03 02/26/05 Josh ALMOST CLEAN<br />
1234 08/31/03 02/26/05 Josh ALMOST CLEAN<br />
1235 09/07/03 02/26/05 Josh ALMOST CLEAN<br />
1236 09/14/03 02/26/05 Josh ALMOST CLEAN<br />
1237 09/21/03 02/26/05 Josh NEEDS CLEAN<br />
1238 09/28/03 02/26/05 Josh NEEDS CLEAN<br />
1239 10/05/03 02/26/05 Josh WORKING<br />
1240 10/12/03 02/26/05 Josh PENDING<br />
1241 10/19/03 02/26/05 Josh NEEDS CLEAN<br />
1242 10/26/03 02/26/05 Josh ALMOST CLEAN<br />
1243 11/02/03 02/26/05 Josh NEEDS CLEAN<br />
1244 11/09/03 02/26/05 Josh NEEDS CLEAN<br />
1245 11/16/03 02/26/05 Josh ALMOST CLEAN<br />
1246 11/23/03 02/26/05 Josh ALMOST CLEAN<br />
1247 11/30/03 02/26/05 Josh ALMOST CLEAN<br />
1248 12/07/03 02/26/05 Josh NEEDS CLEAN<br />
1249 12/14/03 02/26/05 Josh NEEDS CLEAN<br />
1250 12/21/03 02/26/05 Josh NEEDS CLEAN<br />
1251 12/28/03 02/26/05 Josh WORKING<br />
<br />
***************************2004*********************************<br />
<br />
1253 01/11/04 02/26/05 Josh PENDING<br />
1254 01/18/04 Josh PENDING<br />
1255 01/25/04 Josh NEEDS<br />
1256 02/01/04 Josh PENDING<br />
1257 02/08/04 Josh PENDING<br />
1258 02/15/04 Josh PENDING<br />
1259 02/22/04 Josh PENDING<br />
1260 02/29/04 Josh PENDING<br />
1261 03/07/04 02/26/05 Josh PENDING<br />
1262 03/14/04 02/26/05 Josh NEEDS CLEAN<br />
1263 03/21/04 02/26/05 Josh NEEDS CLEAN<br />
1264 03/28/04 02/26/05 Josh NEEDS CLEAN<br />
1265 04/04/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1266 04/11/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1267 04/18/04 02/26/05 Josh NEEDS CLEAN<br />
1268 04/25/04 02/26/05 Josh NEEDS CLEAN<br />
1269 05/02/04 02/26/05 Josh NEEDS CLEAN<br />
1270 05/09/04 02/26/05 Josh NEEDS CLEAN<br />
1271 05/16/04 02/26/05 Josh NEEDS CLEAN<br />
1272 05/23/04 02/26/05 Josh NEEDS CLEAN<br />
1273 05/30/04 02/26/05 Josh NEEDS CLEAN<br />
1274 06/06/04 02/26/05 Josh NEEDS CLEAN<br />
1275 06/13/04 02/26/05 Josh NEEDS CLEAN<br />
1276 06/20/04 02/27/05 Samik DONE<br />
1277 06/27/04 03/19/05 Jeff NEEDS CLEAN<br />
1278 07/04/04 03/19/05 Jeff NEEDS CLEAN<br />
1279 07/11/04 03/19/05 Jeff NEEDS CLEAN<br />
1280 07/18/04 03/19/05 Jeff NEEDS CLEAN<br />
1281 07/25/04 03/19/05 Jeff NEEDS CLEAN<br />
1282 08/01/04 Josh PENDING<br />
1283 08/08/04 Josh PENDING<br />
1284 08/15/04 Josh PENDING<br />
1285 08/22/04 Josh PENDING<br />
1286 08/29/04 Josh PENDING<br />
1287 09/05/04 Josh PENDING<br />
1288 09/12/04 Josh PENDING<br />
1289 09/19/04 03/19/05 Jeff ??<br />
1290 09/26/04 Josh PENDING<br />
1291 10/03/04 Josh PENDING<br />
1292 10/10/04 03/19/05 Jeff ??<br />
1293 10/17/04 Josh PENDING<br />
1294 10/24/04 03/19/05 Jeff ??<br />
1295 10/31/04 03/25/05 Tom CLEAN<br />
1296 11/07/04 04/07/05 Tom Cleaning<br />
1297 11/14/04 03/19/05 Jeff ??<br />
1298 11/21/04 NEEDS CLEAN<br />
1299 11/28/04 NEEDS CLEAN<br />
1300 12/05/04 08/16/05 Pravee CLEAN<br />
1301 12/12/04 08/19/05 Pravee CLEAN<br />
1302 12/19/04 08/19/05 Pravee CLEAN<br />
1303 12/26/04 08/26/05 Pravee CLEAN<br />
</pre><br />
<br />
</pre><br />
<br />
===Archaic (pre-1996)===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
At the moment, Jeff is dealing with these.<br />
</pre></div>Jeffhttp://gps.alaska.edu/internal/index.php?title=WHOS&diff=36WHOS2006-05-19T20:41:37Z<p>Jeff: /* Recent weeks */</p>
<hr />
<div>The WHOS list tracks assigned GPS weeks for processing.<br />
<br />
More details about analysis at [[GPS analysis system]].<br />
<br />
===Recent weeks===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
1321 05/01/2005 Jill<br />
1322 05/08/2005 Jill<br />
1323 05/15/2005 Jill<br />
1324 05/22/2005 Julie<br />
1325 05/29/2005 Sigrun DONE <br />
1326 06/05/2005 Sigrun DONE<br />
1327 06/12/2005 Sigrun<br />
1328 06/19/2005 Tom<br />
1329 06/26/2005 Tom<br />
1330 07/03/2005 9/14/2005 Ryan ak CLEAN pt file size<500<br />
1331 07/10/2005 11/10/2005 Tom Submitted<br />
1332 07/17/2005 Samik<br />
1333 07/24/2005 Julie<br />
1334 07/31/2005 Jill<br />
1335 08/07/2005 9/12/2005 Tom SUBMITTED<br />
1336 08/14/2005 Jill<br />
1337 08/21/2005 10/17/2005 Ryan ak CLEAN pt file size<500<br />
1338 08/28/2005 10/17/2005 Ryan ak CLEAN<br />
1339 09/04/2005 11/08/2005 Ryan working on it<br />
1340 09/11/2005 Julie<br />
1341 09/18/2005 Julie<br />
1342 09/25/2005 Tom<br />
1343 10/02/2005 Tom<br />
1344 10/09/2005 Tom<br />
1345 10/16/2005 01/10/06 Ryan Working on it<br />
1346 10/23/2005 (nobody)<br />
<br />
(skipping some weeks)<br />
<br />
1360 1/29/2006 Sandeep<br />
1361 2/05/2006 Trivikram<br />
1362 2/12/2006 Venkat<br />
<br />
(skipping some weeks)<br />
<br />
1374 10/23/2005 (nobody)<br />
<br />
</pre><br />
<br />
===2005===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
week # start date last processed who status<br />
1304 01/02/2005 09/16/2005 Ryan CLEAN<br />
1305 01/09/2005 08/30/2005 Pravee CLEAN<br />
1306 01/16/2005 07/15/2005 Jill WORKING<br />
1307 01/23/2005 08/31/2005 Pravee CLEAN<br />
1308 01/30/2005 04/05/2005 Jill CLEAN<br />
1309 02/06/2005 08/31/2005 Pravee CLEAN<br />
1310 02/13/2005 03/12/2005 Julie CLEAN<br />
1311 02/20/2005 03/12/2005 Pravee CLEANING<br />
1312 02/27/2005 03/31/2005 Tom CLEAN<br />
1313 03/06/2005 03/31/2005 Pravee CLEANING<br />
1314 03/13/2005 03/31/2005 Tom CLEAN<br />
1315 03/20/2005 06/13/2005 Samik CLEAN pt file size<500<br />
1316 03/27/2005 06/13/2005 Samik CLEAN pt file size<400<br />
1317 04/03/2005 06/16/2005 Samik CLEAN pt file size<400<br />
1318 04/10/2005 9/15/2005 Ryan not sure what's going on?<br />
1319 04/17/2005 10/4/2005 Ryan ak SUBMITTED<br />
1320 04/24/2005 Jill<br />
</pre><br />
<br />
===Older Stuff===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
****************************************************************<br />
***************************2002*********************************<br />
**************************EARTHQUAKE****************************<br />
1189 10/20/02 02/26/05 Josh PENDING<br />
1190 10/27/02 Josh PENDING<br />
1191 11/03/02 03/04/05 Josh DONE<br />
1192 11/10/02 03/11/05 Josh DONE<br />
1193 11/17/02 03/11/05 Josh DONE<br />
1194 11/24/02 03/11/05 Josh DONE<br />
1195 12/01/02 03/11/05 Josh RUNNING<br />
1196 12/08/02 03/11/05 Josh DONE<br />
1197 12/15/02 03/11/05 Josh DONE<br />
1198 12/22/02 03/12/05 Josh DONE<br />
1199 12/29/02 03/12/05 Josh DONE<br />
<br />
*************************2003***********************************<br />
<br />
1200 01/05/03 03/12/05 Josh DONE<br />
1201 01/12/03 03/12/05 Josh DONE<br />
1202 01/19/03 03/15/05 Josh RUNNING<br />
1203 01/26/03 03/14/05 Josh DONE<br />
1204 02/02/03 03/14/05 Josh DONE<br />
1205 02/09/03 Josh PENDING<br />
1206 02/16/03 Josh PENDING<br />
1207 02/23/03 Josh PENDING<br />
1208 03/02/03 02/26/05 Josh ALMOST CLEAN<br />
1209 03/09/03 02/26/05 Josh ALMOST CLEAN<br />
1210 03/16/03 02/26/05 Josh NEEDS CLEAN<br />
1211 03/23/03 02/27/05 Josh CLEANING<br />
1212 03/30/03 02/26/05 Josh DONE<br />
1213 04/06/03 03/12/05 Josh RUNNING<br />
1214 04/13/03 02/26/05 Josh CLEANED<br />
1215 04/20/03 02/27/05 Josh CLEANED<br />
1216 04/27/03 02/26/05 Josh PENDING<br />
1217 05/04/03 02/26/05 Josh NEEDS CLEAN<br />
1218 05/11/03 02/27/05 Josh NEEDS CLEAN<br />
1219 05/18/03 02/27/05 Josh WORKING<br />
1220 05/25/03 02/27/05 Josh PENDING<br />
1221 06/01/03 Josh PENDING<br />
1222 06/08/03 Josh PENDING<br />
1223 06/15/03 Josh PENDING<br />
1224 06/22/03 Josh PENDING<br />
1225 06/29/03 02/26/05 Josh FAILED<br />
1226 07/06/03 02/26/05 Josh ALMOST CLEAN<br />
1227 07/13/03 02/26/05 Josh FAILED<br />
1228 07/20/03 Josh FAILED<br />
1229 07/27/03 11/10/05 Tom Submitted <br />
1230 08/03/03 Josh FAILED<br />
1231 08/10/03 Josh FAILED<br />
1232 08/17/03 11/10/05 Tom Submitted <br />
1233 08/24/03 02/26/05 Josh ALMOST CLEAN<br />
1234 08/31/03 02/26/05 Josh ALMOST CLEAN<br />
1235 09/07/03 02/26/05 Josh ALMOST CLEAN<br />
1236 09/14/03 02/26/05 Josh ALMOST CLEAN<br />
1237 09/21/03 02/26/05 Josh NEEDS CLEAN<br />
1238 09/28/03 02/26/05 Josh NEEDS CLEAN<br />
1239 10/05/03 02/26/05 Josh WORKING<br />
1240 10/12/03 02/26/05 Josh PENDING<br />
1241 10/19/03 02/26/05 Josh NEEDS CLEAN<br />
1242 10/26/03 02/26/05 Josh ALMOST CLEAN<br />
1243 11/02/03 02/26/05 Josh NEEDS CLEAN<br />
1244 11/09/03 02/26/05 Josh NEEDS CLEAN<br />
1245 11/16/03 02/26/05 Josh ALMOST CLEAN<br />
1246 11/23/03 02/26/05 Josh ALMOST CLEAN<br />
1247 11/30/03 02/26/05 Josh ALMOST CLEAN<br />
1248 12/07/03 02/26/05 Josh NEEDS CLEAN<br />
1249 12/14/03 02/26/05 Josh NEEDS CLEAN<br />
1250 12/21/03 02/26/05 Josh NEEDS CLEAN<br />
1251 12/28/03 02/26/05 Josh WORKING<br />
<br />
***************************2004*********************************<br />
<br />
1253 01/11/04 02/26/05 Josh PENDING<br />
1254 01/18/04 Josh PENDING<br />
1255 01/25/04 Josh NEEDS<br />
1256 02/01/04 Josh PENDING<br />
1257 02/08/04 Josh PENDING<br />
1258 02/15/04 Josh PENDING<br />
1259 02/22/04 Josh PENDING<br />
1260 02/29/04 Josh PENDING<br />
1261 03/07/04 02/26/05 Josh PENDING<br />
1262 03/14/04 02/26/05 Josh NEEDS CLEAN<br />
1263 03/21/04 02/26/05 Josh NEEDS CLEAN<br />
1264 03/28/04 02/26/05 Josh NEEDS CLEAN<br />
1265 04/04/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1266 04/11/04 02/26/05 Josh FAILED No files found, needs re<br />
run<br />
1267 04/18/04 02/26/05 Josh NEEDS CLEAN<br />
1268 04/25/04 02/26/05 Josh NEEDS CLEAN<br />
1269 05/02/04 02/26/05 Josh NEEDS CLEAN<br />
1270 05/09/04 02/26/05 Josh NEEDS CLEAN<br />
1271 05/16/04 02/26/05 Josh NEEDS CLEAN<br />
1272 05/23/04 02/26/05 Josh NEEDS CLEAN<br />
1273 05/30/04 02/26/05 Josh NEEDS CLEAN<br />
1274 06/06/04 02/26/05 Josh NEEDS CLEAN<br />
1275 06/13/04 02/26/05 Josh NEEDS CLEAN<br />
1276 06/20/04 02/27/05 Samik DONE<br />
1277 06/27/04 03/19/05 Jeff NEEDS CLEAN<br />
1278 07/04/04 03/19/05 Jeff NEEDS CLEAN<br />
1279 07/11/04 03/19/05 Jeff NEEDS CLEAN<br />
1280 07/18/04 03/19/05 Jeff NEEDS CLEAN<br />
1281 07/25/04 03/19/05 Jeff NEEDS CLEAN<br />
1282 08/01/04 Josh PENDING<br />
1283 08/08/04 Josh PENDING<br />
1284 08/15/04 Josh PENDING<br />
1285 08/22/04 Josh PENDING<br />
1286 08/29/04 Josh PENDING<br />
1287 09/05/04 Josh PENDING<br />
1288 09/12/04 Josh PENDING<br />
1289 09/19/04 03/19/05 Jeff ??<br />
1290 09/26/04 Josh PENDING<br />
1291 10/03/04 Josh PENDING<br />
1292 10/10/04 03/19/05 Jeff ??<br />
1293 10/17/04 Josh PENDING<br />
1294 10/24/04 03/19/05 Jeff ??<br />
1295 10/31/04 03/25/05 Tom CLEAN<br />
1296 11/07/04 04/07/05 Tom Cleaning<br />
1297 11/14/04 03/19/05 Jeff ??<br />
1298 11/21/04 NEEDS CLEAN<br />
1299 11/28/04 NEEDS CLEAN<br />
1300 12/05/04 08/16/05 Pravee CLEAN<br />
1301 12/12/04 08/19/05 Pravee CLEAN<br />
1302 12/19/04 08/19/05 Pravee CLEAN<br />
1303 12/26/04 08/26/05 Pravee CLEAN<br />
</pre><br />
<br />
</pre><br />
<br />
===Archaic (pre-1996)===<br />
<pre><br />
week # start date last processed who status<br />
****************************************************************<br />
At the moment, Jeff is dealing with these.<br />
</pre></div>Jeffhttp://gps.alaska.edu/internal/index.php?title=RINEXing&diff=1566RINEXing2005-10-21T04:58:05Z<p>Jeff: </p>
<hr />
<div>The program we now use to convert most files to rinex is called teqc, which is written and maintained by Lou Estey at UNAVCO. Teqc can handle data from many different receiver types. This page describes how to convert the data from Trimble receivers into RINEX format.<br />
<br />
===Converting Trimble .t00/.t01 files to .dat===<br />
Normally you don't have to do this. The exception is the data from the Net-RS receiver, which under some circumstances we will only get in .t01 format. Or if you copy .t00 files straight off a flash card.<br />
<br />
====.t00 files====<br />
There are two ways to convert these files to .dat format. You can do it on a Windows PC by right-clicking on the file and selecting "Convert to DAT format" from the contextual menu. Or you can convert the files on our Linux system using:<br />
<br />
<pre><br />
/usr/local/UNAVCO/bin/runpkr00 -d file.t00<br />
</pre><br />
<br />
This will create the file <code>file.dat</code>.<br />
<br />
====.t01 files====<br />
At the moment, these files can only be converted on a Windows PC that has the latest version of Trimble Data Transfer installed. Right-click on the file and choose "Convert to DAT format" from the contextual menu.<br />
<br />
===Converting dat files to RINEX===<br />
You can create a single file to RINEX using teqc. We have a script that will create RINEX files and also add appropriate information into the RINEX headers. The easiest way to convert multiple files is to make up a script and then execute it.<br />
<br />
<pre><br />
/bin/ls *.dat | awk '{print "newrinex_teqc -5700 tr_d " $0}' > rinexem<br />
</pre><br />
<br />
There are some options you can add to this:<br />
* The -5700 flag really means to use the Zephyr Geodetic antenna, you can use it for the Net-RS as well<br />
* For data from a Trimble 4000 receiver, use -4000 instead.<br />
* You can add the operator name using -oper Name (no spaces)<br />
* If the data are from a non-UAF group, add -agency Agency<br />
* For 4000 receivers, add -slant 0.2334 -0.0591 to convert from slant to vertical height<br />
<br />
Then execute the script:<br />
<br />
<pre><br />
sh rinexem<br />
</pre><br />
<br />
There should be one RINEX observation file (<code>*.YYo</code>, YY = last 2 digits of the year) and one RINEX navigation file (<code>*.YYn</code>) for each .dat file.<br />
<br />
To make a fully complete RINEX file, you would have to edit the file in a text editor and add any missing items that are blank. That is important for files that we might send to someone else, but it doesn't matter for our own processing.<br />
<br />
The final step is to compress the files using gzip.<br />
<br />
===Splitting mulit-day dat files===<br />
Normally we set our receivers to start a new file every day at UTC midnight and track for 24 hours. Every so often we get a data file that has several days all in one file, because the receiver was not programmed correctly. Most often this happens with borrowed receivers that we forget to reprogram.<br />
<br />
If the file contains just a few days of data you can just create a RINEX file as above, then use <pre>rinexwin</pre> to split it into daily files. For example,<br />
<br />
<pre><br />
rinexwin warr2061.05o -ge "25-jul-2005 00:00" -lt "26-jul-2005 00:00" > ../warr2060.05o<br />
rinexwin warr2061.05o -ge "26-jul-2005 00:00" -lt "27-jul-2005 00:00" > ../warr2070.05o<br />
</pre><br />
<br />
However, once a file spans a long enough time it requires some special handling. For files spanning several days you can generally add the +smtt flag to the teqc command (at the moment you have to edit scripte or run it manually to do this). For longer files you need to split the dat file up into daily dat files. The reason for this has to do with the convention typically used in RINEX for handling the 1 millisecond clock offsets in the Trimble and other receivers. These files require some manual fiddling.<br />
<br />
There is a 4 step process:<br />
1. Use teqc to create a diagnostic file that contains information about the time and byte position of each data record in the file.<br />
2. Run a perl program that processes this file to make a list of epochs around UTC midnight along with their byte locations.<br />
3. Edit this file, or a copy, to keep only those lines for the epochs at midnight.<br />
4. Use a simple awk command to convert this file into a script to run the program chop, which chops bytes out of a file.<br />
5. Edit this script to make a final simple change, and run it. OK, that is 5 steps.<br />
<br />
The reason for all of these steps is because of the millisecond offsets in the data, so that it becomes difficult for a long file to predict exactly which observation is the one at UTC midnight. To do it would require figuring out which way the clock is drifting. It would not be too hard to do that, but is too much programming hassle.<br />
<br />
This was developed before the teqc +smtt option, and I believe that by using teqc +smtt it should be possible to create a single perl program that would do all of the above steps in one.<br />
<br />
For example, suppose the file tk5e1440.dat contains a couple of months of data. The sequence of commands to split the file is given below.<br />
<br />
<pre><br />
teqc +diag -O.obs - tk5e1440.dat >& tk5e1440.dat.diag<br />
~jeff/bin/split_big_dat tk5e1440.dat.diag > rectimes<br />
</pre><br />
<br />
<br />
The file tk5e1440.dat.diag has the RINEX file lines with the observations times, plus a bunch of lines that refer to Trimble download frames. There is one of these with type=17 for each data record.<br />
<br />
<pre><br />
05 5 24 2 41 15.0000000 0 4G 4G13G16G23<br />
Trimble download frame t @ 0o00004373 = 0x000008fb = 00002299 type= 0x15 = 21<br />
Trimble download frame t @ 0o00004671 = 0x000009b9 = 00002489 type= 0x15 = 21<br />
Trimble download frame t @ 0o00005167 = 0x00000a77 = 00002679 type= 0x15 = 21<br />
Trimble download frame t @ 0o00005465 = 0x00000b35 = 00002869 type= 0x11 = 17<br />
05 5 24 2 41 30.0000000 0 4G 4G13G16G23<br />
Trimble download frame t @ 0o00006152 = 0x00000c6a = 00003178 type= 0x15 = 21<br />
Trimble download frame t @ 0o00006450 = 0x00000d28 = 00003368 type= 0x15 = 21<br />
Trimble download frame t @ 0o00006746 = 0x00000de6 = 00003558 type= 0x15 = 21<br />
Trimble download frame t @ 0o00007244 = 0x00000ea4 = 00003748 type= 0x15 = 21<br />
Trimble download frame t @ 0o00007542 = 0x00000f62 = 00003938 type= 0x11 = 17<br />
05 5 24 2 41 45.0000000 0 8G 2G 4G 8G10G13G16G23G20<br />
Trimble download frame t @ 0o00010667 = 0x000011b7 = 00004535 type= 0x11 = 17<br />
05 5 24 2 42 0.0000000 0 8G 2G 4G 8G10G13G16G23G20<br />
Trimble download frame t @ 0o00011764 = 0x000013f4 = 00005108 type= 0x15 = 21<br />
Trimble download frame t @ 0o00012262 = 0x000014b2 = 00005298 type= 0x11 = 17<br />
05 5 24 2 42 15.0000000 0 8G 2G 4G 8G10G13G16G23G20<br />
</pre><br />
<br />
The split_big_dat program is written in perl, and it processes this file and boils it down to an essential one line per data record, giving the byte number and the observation time:<br />
<br />
<pre><br />
5097 at byte number 03354160 : 05 5 24 23 55 14.9710000<br />
5098 at byte number 03354829 : 05 5 24 23 55 29.9710000<br />
5099 at byte number 03355498 : 05 5 24 23 55 44.9710000<br />
5100 at byte number 03356167 : 05 5 24 23 55 59.9710000<br />
5101 at byte number 03356836 : 05 5 24 23 56 14.9710000<br />
5102 at byte number 03357505 : 05 5 24 23 56 29.9710000<br />
5103 at byte number 03358174 : 05 5 24 23 56 44.9710000<br />
</pre><br />
<br />
Now the trick is to edit this file and keep only the lines that correspond to the day boundaries. Be careful about the millisecond offsets. The split_big_dat program only prints out the lines that are near to midnight, so it will be pretty easy to do this. A trick is that once you have found the first one, you can delete 43 lines and the line after that will be the next one. The first few lines of the edited file look like this:<br />
<br />
<pre><br />
5116 at byte number 03366871 : 05 5 24 23 59 59.9710000<br />
10876 at byte number 07145513 : 05 5 25 23 59 59.9390000<br />
16636 at byte number 10925649 : 05 5 26 23 59 59.9060000<br />
22396 at byte number 14704101 : 05 5 27 23 59 59.8720000<br />
</pre><br />
<br />
In this file, every few days there was some problem with the data point at 0000 UTC, so I picked the one at 0015 for those days. This example file had data from 43 different days (42 lines in the file).<br />
<br />
Next we make up a script that will run a program called chop over and over again to chop out pieces of the file. Chop needs to know the byte number of the start and end of the file.<br />
<br />
<pre><br />
mkdir split<br />
awk 'BEGIN {last = 0} {print "~jeff/bin/chop +" last " -" $5 " tk5e1440.dat > split/tk5exxx0.dat" ; last = $5}' rectimes.edited > splits<br />
<br />
more splits<br />
~jeff/bin/chop +0 -03366871 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +03366871 -07145513 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +07145513 -10925649 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +10925649 -14704101 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +14704101 -18486658 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +18486658 -22266015 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +22266015 -26042019 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +26042019 -29821755 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +29821755 -33716237 tk5e1440.dat > split/tk5exxx0.dat<br />
</pre><br />
<br />
The last step is to edit the splits file and put in the correct day number for each of the output RINEX files. You have to add a final line for the last day by hand. It should look like this:<br />
<br />
<pre><br />
~jeff/bin/chop +157859599 -161760773 tk5e1440.dat > split/tk5e1840.dat<br />
~jeff/bin/chop +161760773 tk5e1440.dat > split/tk5e1850.dat<br />
</pre><br />
<br />
Then run the script, and you have daily .dat files! One catch is that some of the header meta-data may be missing from the files, unless it is repeated every day. So you may need to provide more meta-data when running teqc to have a complete RINEX header.</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=RINEXing&diff=25RINEXing2005-10-21T00:56:23Z<p>Jeff: </p>
<hr />
<div>The program we now use to convert most files to rinex is called teqc, which is written and maintained by Lou Estey at UNAVCO. Teqc can handle data from many different receiver types. This page describes how to convert the data from Trimble receivers into RINEX format.<br />
<br />
===Converting Trimble .t00/.t01 files to .dat===<br />
Normally you don't have to do this. The exception is the data from the Net-RS receiver, which under some circumstances we will only get in .t01 format. Or if you copy .t00 files straight off a flash card.<br />
<br />
====.t00 files====<br />
There are two ways to convert these files to .dat format. You can do it on a Windows PC by right-clicking on the file and selecting "Convert to DAT format" from the contextual menu. Or you can convert the files on our Linux system using:<br />
<br />
<pre><br />
/usr/local/UNAVCO/bin/runpkr00 -d file.t00<br />
</pre><br />
<br />
This will create the file <code>file.dat</code>.<br />
<br />
====.t01 files====<br />
At the moment, these files can only be converted on a Windows PC that has the latest version of Trimble Data Transfer installed. Right-click on the file and choose "Convert to DAT format" from the contextual menu.<br />
<br />
===Converting dat files to RINEX===<br />
You can create a single file to RINEX using teqc. We have a script that will create RINEX files and also add appropriate information into the RINEX headers. The easiest way to convert multiple files is to make up a script and then execute it.<br />
<br />
<pre><br />
/bin/ls *.dat | awk '{print "newrinex_teqc -5700 tr_d " $0}' > rinexem<br />
</pre><br />
<br />
There are some options you can add to this:<br />
* The -5700 flag really means to use the Zephyr Geodetic antenna, you can use it for the Net-RS as well<br />
* For data from a Trimble 4000 receiver, use -4000 instead.<br />
* You can add the operator name using -oper Name (no spaces)<br />
* If the data are from a non-UAF group, add -agency Agency<br />
* For 4000 receivers, add -slant 0.2334 -0.0591 to convert from slant to vertical height<br />
<br />
Then execute the script:<br />
<br />
<pre><br />
sh rinexem<br />
</pre><br />
<br />
There should be one RINEX observation file (<code>*.YYo</code>, YY = last 2 digits of the year) and one RINEX navigation file (<code>*.YYn</code>) for each .dat file.<br />
<br />
To make a fully complete RINEX file, you would have to edit the file in a text editor and add any missing items that are blank. That is important for files that we might send to someone else, but it doesn't matter for our own processing.<br />
<br />
The final step is to compress the files using gzip.<br />
<br />
===Splitting mulit-day dat files===<br />
Normally we set our receivers to start a new file every day at UTC midnight and track for 24 hours. Every so often we get a data file that has several days all in one file, because the receiver was not programmed correctly. Most often this happens with borrowed receivers that we forget to reprogram.<br />
<br />
If the file contains just a few days of data you can just create a RINEX file as above, then use <pre>rinexwin</pre> to split it into daily files. For example,<br />
<br />
<pre><br />
rinexwin warr2061.05o -ge "25-jul-2005 00:00" -lt "26-jul-2005 00:00" > ../warr2060.05o<br />
rinexwin warr2061.05o -ge "26-jul-2005 00:00" -lt "27-jul-2005 00:00" > ../warr2070.05o<br />
</pre><br />
<br />
However, once a file spans a long enough time it requires some special handling. For files spanning several days you can generally add the +smtt flag to the teqc command (at the moment you have to edit scripte or run it manually to do this). For longer files you need to split the dat file up into daily dat files. The reason for this has to do with the convention typically used in RINEX for handling the 1 millisecond clock offsets in the Trimble and other receivers. These files require some manual fiddling.<br />
<br />
There is a 4 step process:<br />
1. Use teqc to create a diagnostic file that contains information about the time and byte position of each data record in the file.<br />
2. Run a perl program that processes this file to make a list of <br />
<br />
<br />
For example, suppose the file tk5e1440.dat contains a couple of months of data. The sequence of commands to split the file is given below.<br />
<br />
<pre><br />
teqc +diag -O.obs - tk5e1440.dat >& tk5e1440.dat.diag<br />
~jeff/bin/split_big_dat tk5e1440.dat.diag > rectimes<br />
</pre><br />
<br />
<br />
The file tk5e1440.dat.diag has the RINEX file lines with the observations times, plus a bunch of lines that refer to Trimble download frames. There is one of these with type=17 for each data record.<br />
<br />
<pre><br />
05 5 24 2 41 15.0000000 0 4G 4G13G16G23<br />
Trimble download frame t @ 0o00004373 = 0x000008fb = 00002299 type= 0x15 = 21<br />
Trimble download frame t @ 0o00004671 = 0x000009b9 = 00002489 type= 0x15 = 21<br />
Trimble download frame t @ 0o00005167 = 0x00000a77 = 00002679 type= 0x15 = 21<br />
Trimble download frame t @ 0o00005465 = 0x00000b35 = 00002869 type= 0x11 = 17<br />
05 5 24 2 41 30.0000000 0 4G 4G13G16G23<br />
Trimble download frame t @ 0o00006152 = 0x00000c6a = 00003178 type= 0x15 = 21<br />
Trimble download frame t @ 0o00006450 = 0x00000d28 = 00003368 type= 0x15 = 21<br />
Trimble download frame t @ 0o00006746 = 0x00000de6 = 00003558 type= 0x15 = 21<br />
Trimble download frame t @ 0o00007244 = 0x00000ea4 = 00003748 type= 0x15 = 21<br />
Trimble download frame t @ 0o00007542 = 0x00000f62 = 00003938 type= 0x11 = 17<br />
05 5 24 2 41 45.0000000 0 8G 2G 4G 8G10G13G16G23G20<br />
Trimble download frame t @ 0o00010667 = 0x000011b7 = 00004535 type= 0x11 = 17<br />
05 5 24 2 42 0.0000000 0 8G 2G 4G 8G10G13G16G23G20<br />
Trimble download frame t @ 0o00011764 = 0x000013f4 = 00005108 type= 0x15 = 21<br />
Trimble download frame t @ 0o00012262 = 0x000014b2 = 00005298 type= 0x11 = 17<br />
05 5 24 2 42 15.0000000 0 8G 2G 4G 8G10G13G16G23G20<br />
</pre><br />
<br />
The split_big_dat program is written in perl, and it processes this file and boils it down to an essential one line per data record, giving the byte number and the observation time:<br />
<br />
<pre><br />
5097 at byte number 03354160 : 05 5 24 23 55 14.9710000<br />
5098 at byte number 03354829 : 05 5 24 23 55 29.9710000<br />
5099 at byte number 03355498 : 05 5 24 23 55 44.9710000<br />
5100 at byte number 03356167 : 05 5 24 23 55 59.9710000<br />
5101 at byte number 03356836 : 05 5 24 23 56 14.9710000<br />
5102 at byte number 03357505 : 05 5 24 23 56 29.9710000<br />
5103 at byte number 03358174 : 05 5 24 23 56 44.9710000<br />
</pre><br />
<br />
Now the trick is to edit this file and keep only the lines that correspond to the day boundaries. Be careful about the millisecond offsets. The split_big_dat program only prints out the lines that are near to midnight, so it will be pretty easy to do this. A trick is that once you have found the first one, you can delete 43 lines and the line after that will be the next one. The first few lines of the edited file look like this:<br />
<br />
<pre><br />
5116 at byte number 03366871 : 05 5 24 23 59 59.9710000<br />
10876 at byte number 07145513 : 05 5 25 23 59 59.9390000<br />
16636 at byte number 10925649 : 05 5 26 23 59 59.9060000<br />
22396 at byte number 14704101 : 05 5 27 23 59 59.8720000<br />
</pre><br />
<br />
In this file, every few days there was some problem with the data point at 0000 UTC, so I picked the one at 0015 for those days. This example file had data from 43 different days (42 lines in the file).<br />
<br />
Next we make up a script that will run a program called chop over and over again to chop out pieces of the file. Chop needs to know the byte number of the start and end of the file.<br />
<br />
<pre><br />
mkdir split<br />
awk 'BEGIN {last = 0} {print "~jeff/bin/chop +" last " -" $5 " tk5e1440.dat > split/tk5exxx0.dat" ; last = $5}' rectimes.edited > splits<br />
<br />
more splits<br />
~jeff/bin/chop +0 -03366871 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +03366871 -07145513 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +07145513 -10925649 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +10925649 -14704101 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +14704101 -18486658 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +18486658 -22266015 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +22266015 -26042019 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +26042019 -29821755 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +29821755 -33716237 tk5e1440.dat > split/tk5exxx0.dat<br />
</pre><br />
<br />
The last step is to edit the splits file and put in the correct day number for each of the output RINEX files. You have to add a final line for the last day by hand. It should look like this:<br />
<br />
<pre><br />
~jeff/bin/chop +157859599 -161760773 tk5e1440.dat > split/tk5e1840.dat<br />
~jeff/bin/chop +161760773 tk5e1440.dat > split/tk5e1850.dat<br />
</pre><br />
<br />
Then run the script, and you have daily .dat files! One catch is that some of the header meta-data may be missing from the files, unless it is repeated every day. So you may need to provide more meta-data when running teqc to have a complete RINEX header.</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=RINEXing&diff=24RINEXing2005-10-20T01:13:54Z<p>Jeff: </p>
<hr />
<div>The program we now use to convert most files to rinex is called teqc, which is written and maintained by Lou Estey at UNAVCO. Teqc can handle data from many different receiver types. This page describes how to convert the data from Trimble receivers into RINEX format.<br />
<br />
===Converting Trimble .t00/.t01 files to .dat===<br />
Normally you don't have to do this. The exception is the data from the Net-RS receiver, which under some circumstances we will only get in .t01 format. Or if you copy .t00 files straight off a flash card.<br />
<br />
====.t00 files====<br />
There are two ways to convert these files to .dat format. You can do it on a Windows PC by right-clicking on the file and selecting "Convert to DAT format" from the contextual menu. Or you can convert the files on our Linux system using:<br />
<br />
<pre><br />
/usr/local/UNAVCO/bin/runpkr00 -d file.t00<br />
</pre><br />
<br />
This will create the file <code>file.dat</code>.<br />
<br />
====.t01 files====<br />
At the moment, these files can only be converted on a Windows PC that has the latest version of Trimble Data Transfer installed. Right-click on the file and choose "Convert to DAT format" from the contextual menu.<br />
<br />
===Converting dat files to RINEX===<br />
You can create a single file to RINEX using teqc. We have a script that will create RINEX files and also add appropriate information into the RINEX headers. The easiest way to convert multiple files is to make up a script and then execute it.<br />
<br />
<pre><br />
/bin/ls *.dat | awk '{print "newrinex_teqc -5700 tr_d " $0}' > rinexem<br />
</pre><br />
<br />
There are some options you can add to this:<br />
* The -5700 flag really means to use the Zephyr Geodetic antenna, you can use it for the Net-RS as well<br />
* For data from a Trimble 4000 receiver, use -4000 instead.<br />
* You can add the operator name using -oper Name (no spaces)<br />
* If the data are from a non-UAF group, add -agency Agency<br />
* For 4000 receivers, add -slant 0.2334 -0.0591 to convert from slant to vertical height<br />
<br />
Then execute the script:<br />
<br />
<pre><br />
sh rinexem<br />
</pre><br />
<br />
There should be one RINEX observation file (<code>*.YYo</code>, YY = last 2 digits of the year) and one RINEX navigation file (<code>*.YYn</code>) for each .dat file.<br />
<br />
To make a fully complete RINEX file, you would have to edit the file in a text editor and add any missing items that are blank. That is important for files that we might send to someone else, but it doesn't matter for our own processing.<br />
<br />
The final step is to compress the files using gzip.<br />
<br />
===Splitting mulit-day dat files===<br />
Normally we set our receivers to start a new file every day at UTC midnight and track for 24 hours. Every so often we get a data file that has several days all in one file, because the receiver was not programmed correctly. Most often this happens with borrowed receivers that we forget to reprogram.<br />
<br />
If the file contains just a few days of data you can just create a RINEX file as above, then use <pre>rinexwin</pre> to split it into daily files. For example,<br />
<br />
<pre><br />
rinexwin warr2061.05o -ge "25-jul-2005 00:00" -lt "26-jul-2005 00:00" > ../warr2060.05o<br />
rinexwin warr2061.05o -ge "26-jul-2005 00:00" -lt "27-jul-2005 00:00" > ../warr2070.05o<br />
</pre><br />
<br />
However, once a file spans a long enough time it requires some special handling. For files spanning several days you can generally add the +smtt flag to the teqc command (at the moment you have to edit scripte or run it manually to do this). For longer files you need to split the dat file up into daily dat files. The reason for this has to do with the convention typically used in RINEX for handling the 1 millisecond clock offsets in the Trimble and other receivers. These files require some manual fiddling.<br />
<br />
There is a 4 step process:<br />
1. Use teqc to create a diagnostic file that contains information about the time and byte position of each data record in the file.<br />
2. Run a perl program that processes this file to make a list of <br />
<br />
<br />
For example, suppose the file tk5e1440.dat contains a couple of months of data. The sequence of commands to split the file is given below.<br />
<br />
<pre><br />
teqc +diag -O.obs - tk5e1440.dat >& tk5e1440.dat.diag<br />
~jeff/bin/split_big_dat tk5e1440.dat.diag > rectimes<br />
</pre><br />
<br />
<br />
The file tk5e1440.dat.diag has the RINEX file lines with the observations times, plus a bunch of lines that refer to Trimble download frames. There is one of these with type=17 for each data record.<br />
<br />
<pre><br />
05 5 24 2 41 15.0000000 0 4G 4G13G16G23<br />
Trimble download frame t @ 0o00004373 = 0x000008fb = 00002299 type= 0x15 = 21<br />
Trimble download frame t @ 0o00004671 = 0x000009b9 = 00002489 type= 0x15 = 21<br />
Trimble download frame t @ 0o00005167 = 0x00000a77 = 00002679 type= 0x15 = 21<br />
Trimble download frame t @ 0o00005465 = 0x00000b35 = 00002869 type= 0x11 = 17<br />
05 5 24 2 41 30.0000000 0 4G 4G13G16G23<br />
Trimble download frame t @ 0o00006152 = 0x00000c6a = 00003178 type= 0x15 = 21<br />
Trimble download frame t @ 0o00006450 = 0x00000d28 = 00003368 type= 0x15 = 21<br />
Trimble download frame t @ 0o00006746 = 0x00000de6 = 00003558 type= 0x15 = 21<br />
Trimble download frame t @ 0o00007244 = 0x00000ea4 = 00003748 type= 0x15 = 21<br />
Trimble download frame t @ 0o00007542 = 0x00000f62 = 00003938 type= 0x11 = 17<br />
05 5 24 2 41 45.0000000 0 8G 2G 4G 8G10G13G16G23G20<br />
Trimble download frame t @ 0o00010667 = 0x000011b7 = 00004535 type= 0x11 = 17<br />
05 5 24 2 42 0.0000000 0 8G 2G 4G 8G10G13G16G23G20<br />
Trimble download frame t @ 0o00011764 = 0x000013f4 = 00005108 type= 0x15 = 21<br />
Trimble download frame t @ 0o00012262 = 0x000014b2 = 00005298 type= 0x11 = 17<br />
05 5 24 2 42 15.0000000 0 8G 2G 4G 8G10G13G16G23G20<br />
</pre><br />
<br />
The split_big_dat program is written in perl, and it processes this file and boils it down to an essential one line per data record, giving the byte number and the observation time:<br />
<br />
<pre><br />
5097 at byte number 03354160 : 05 5 24 23 55 14.9710000<br />
5098 at byte number 03354829 : 05 5 24 23 55 29.9710000<br />
5099 at byte number 03355498 : 05 5 24 23 55 44.9710000<br />
5100 at byte number 03356167 : 05 5 24 23 55 59.9710000<br />
5101 at byte number 03356836 : 05 5 24 23 56 14.9710000<br />
5102 at byte number 03357505 : 05 5 24 23 56 29.9710000<br />
5103 at byte number 03358174 : 05 5 24 23 56 44.9710000<br />
</pre><br />
<br />
Now the trick is to edit this file and keep only the lines that correspond to the day boundaries. Be careful about the millisecond offsets. The split_big_dat program only prints out the lines that are near to midnight, so it will be pretty easy to do this. A trick is that once you have found the first one, you can delete 43 lines and the line after that will be the next one. The first few lines of the edited file look like this:<br />
<br />
<pre><br />
5116 at byte number 03366871 : 05 5 24 23 59 59.9710000<br />
10876 at byte number 07145513 : 05 5 25 23 59 59.9390000<br />
16636 at byte number 10925649 : 05 5 26 23 59 59.9060000<br />
22396 at byte number 14704101 : 05 5 27 23 59 59.8720000<br />
</pre><br />
<br />
In this file, every few days there was some problem with the data point at 0000 UTC, so I picked the one at 0015 for those days. This example file had data from 43 different days (42 lines in the file).<br />
<br />
Next we make up a script that will run a program called chop over and over again to chop out pieces of the file. Chop needs to know the byte number of the start and end of the file.<br />
<br />
<pre><br />
mkdir split<br />
awk 'BEGIN {last = 0} {print "~jeff/bin/chop +" last " -" $5 " tk5e1440.dat > split/tk5exxx0.dat"; last = $5}' rectimes.edited > splits<br />
<br />
more splits<br />
~jeff/bin/chop +0 -03366871 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +03366871 -07145513 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +07145513 -10925649 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +10925649 -14704101 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +14704101 -18486658 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +18486658 -22266015 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +22266015 -26042019 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +26042019 -29821755 tk5e1440.dat > split/tk5exxx0.dat<br />
~jeff/bin/chop +29821755 -33716237 tk5e1440.dat > split/tk5exxx0.dat<br />
</pre><br />
<br />
The last step is to edit the splits file and put in the correct day number for each of the output RINEX files. You have to add a final line for the last day by hand. It should look like this:<br />
<br />
<pre><br />
~jeff/bin/chop +157859599 -161760773 tk5e1440.dat > split/tk5e1840.dat<br />
~jeff/bin/chop +161760773 tk5e1440.dat > split/tk5e1850.dat<br />
</pre><br />
<br />
Then run the script, and you have daily .dat files! One catch is that some of the header meta-data may be missing from the files, unless it is repeated every day. So you may need to provide more meta-data when running teqc to have a complete RINEX header.</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=RINEXing&diff=23RINEXing2005-10-04T07:01:22Z<p>Jeff: </p>
<hr />
<div>The program we now use to convert most files to rinex is called teqc, which is written and maintained by Lou Estey at UNAVCO. Teqc can handle data from many different receiver types. This page describes how to convert the data from Trimble receivers into RINEX format.<br />
<br />
===Converting Trimble .t00/.t01 files to .dat===<br />
Normally you don't have to do this. The exception is the data from the Net-RS receiver, which under some circumstances we will only get in .t01 format. Or if you copy .t00 files straight off a flash card.<br />
<br />
====.t00 files====<br />
There are two ways to convert these files to .dat format. You can do it on a Windows PC by right-clicking on the file and selecting "Convert to DAT format" from the contextual menu. Or you can convert the files on our Linux system using:<br />
<br />
<pre><br />
/usr/local/UNAVCO/bin/runpkr00 -d file.t00<br />
</pre><br />
<br />
This will create the file <code>file.dat</code>.<br />
<br />
====.t01 files====<br />
At the moment, these files can only be converted on a Windows PC that has the latest version of Trimble Data Transfer installed. Right-click on the file and choose "Convert to DAT format" from the contextual menu.<br />
<br />
===Converting dat files to RINEX===<br />
You can create a single file to RINEX using teqc. We have a script that will create RINEX files and also add appropriate information into the RINEX headers. The easiest way to convert multiple files is to make up a script and then execute it.<br />
<br />
<pre><br />
/bin/ls *.dat | awk '{print "newrinex_teqc -5700 tr_d " $0}' > rinexem<br />
</pre><br />
<br />
There are some options you can add to this:<br />
* The -5700 flag really means to use the Zephyr Geodetic antenna, you can use it for the Net-RS as well<br />
* For data from a Trimble 4000 receiver, use -4000 instead.<br />
* You can add the operator name using -oper Name (no spaces)<br />
* If the data are from a non-UAF group, add -agency Agency<br />
* For 4000 receivers, add -slant 0.2334 -0.0591 to convert from slant to vertical height<br />
<br />
Then execute the script:<br />
<br />
<pre><br />
sh rinexem<br />
</pre><br />
<br />
There should be one RINEX observation file (<code>*.YYo</code>, YY = last 2 digits of the year) and one RINEX navigation file (<code>*.YYn</code>) for each .dat file.<br />
<br />
To make a fully complete RINEX file, you would have to edit the file in a text editor and add any missing items that are blank. That is important for files that we might send to someone else, but it doesn't matter for our own processing.<br />
<br />
The final step is to compress the files using gzip.</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=GeodesyLab:About&diff=421GeodesyLab:About2005-10-04T06:31:15Z<p>Jeff: </p>
<hr />
<div>The UAF Geophysical Institute Geodesy Lab is a research group also associated with the Department of Geology and Geophysics. We conduct research into a variety of crustal deformation problems using modern space geodetic techniques. Primarily we use the Global Positioning System (GPS) and Interferometric Synthetic Aperture Radar (InSAR).<br />
<br />
Dr. Jeff Freymueller, Professor of Geophysics<br />
<br />
Dr. Chris Larsen, Research Associate (also with Glaciology group)<br />
<br />
Max Kaufman, Research Technician<br />
<br />
Graduate Students<br />
* Ryan Cross, M.S. candidate<br />
* Julie Elliott, Ph.D. candidate<br />
* Tom Fournier, Ph.D. candidate<br />
* Jill Shipman, Ph.D. candidate<br />
* Samik Sil, M.S. candidate</div>Jeffhttp://gps.alaska.edu/internal/index.php?title=Main_Page&diff=7Main Page2005-10-04T05:27:18Z<p>Jeff: </p>
<hr />
<div>'''Welcome to the GI Geodesy internal page'''<br />
<br />
This internal page is based on a wiki, which is a web-based system for creating collaborative content. We can all edit the content on this site. The particular wiki engine used here is [http://www.mediawiki.org MediaWiki], which is the engine used for [http://www.wikipedia.org Wikipedia], the multi-lingual free encyclopedia. Once it is fully set up, a username and password will be required to edit content, although others can browse it.<br />
:For more information on how this works, see http://meta.wikimedia.org/wiki/MediaWiki_User's_Guide<br />
<br />
If all goes according to plan, all of us will contribute useful information to this site, which will then become a useful reference for the rest of us.<br />
<br />
One quick set up note: links shown in Red are links to non-existent pages (add some content there!). Links shown in blue are to existing pages. This is all in the early stages of construction. -- Jeff Freymueller, 10/3/2005.<br />
<br />
=== GPS Fieldwork ===<br />
A simple guide to GPS [[fieldwork]], from finding site information to<br />
setting up the receiver and antenna, and converting data files to rinex format.<br />
<br />
=== Working with the Geodesy Lab linux computer system ===<br />
General information about our computer system will go here.<br />
<br />
=== The WHOS data analysis list ===<br />
The [[WHOS]] list keeps track of which GPS weeks are assigned to<br />
which people.<br />
<br />
=== GPS Data Analysis ===<br />
We use the GIPSY software for GPS data analysis. Jeff Freymueller has written<br />
a set of scripts around GIPSY that automate data acquisition and much<br />
of the data analysis tasks. Documentation for the [[GPS analysis system]] is<br />
under construction here.<br />
<br />
=== InSAR software ===<br />
We have the ROI_PAC software installed. More information will follow.</div>Jeff