Kinematic Processing - Revision history

Jeff at 17:30, 24 October 2013

2013-10-24T17:30:06Z

2012-06-05T19:00:40Z

‎Define the solution parameters

2010-01-07T11:23:19Z

2009-06-21T01:03:34Z

‎Temporal Resolution below 5 min

2009-02-26T23:50:13Z

‎Workflow

2009-02-26T00:27:56Z

‎Temporal Resolution below 5 min

2009-02-25T23:27:40Z

‎Temporal Resolution below 5 min

2009-02-25T23:27:22Z

‎Temporal Resolution below 5 min

2009-02-25T23:27:04Z

‎Temporal Resolution below 5 min

2009-02-25T03:51:44Z

‎Temporal Resolution below 5 min

@@ Line 32: / Line 32: @@
 </ul>
-==Define the solution parameters==
+==Standard/Automated Processing for Kinematic PPP Solutions==
 Use an NML file to define the solution parameters.   Here is an example to start with.

@@ Line 44: / Line 44: @@
   ! except for very short baselines, this is always true.
     WETZTROP  = .TRUE.
-  ! don't recall what this is
+  ! This is the white noise sigma applied to phase ambiguity parameters
     yaddsg = 0.1
   ! this is the random walk constraint for the troposphere, in km/sqrt(sec)

@@ Line 17: / Line 17: @@
          <code>
           rnx2qm RINEX-file -dir $procdir -interval 30
          </code>
      </center>

@@ Line 16: / Line 16: @@
      <center>
          <code>
-          rnx2qm.rndev RINEX-file -dir $procdir -interval 30
+          rnx2qm RINEX-file -dir $procdir -interval 30
          </code>
      </center>

@@ Line 2: / Line 2: @@
 <ul>
 <li>define subnet file (including clock site, a couple of non-kinematically estimated sites, at the ones you are really interested in)</li>
-<li>define namelist (nml) file (RANDOM-WALK!)</li>
+<li>define namelist (nml) file (RANDOM-WALK!), at best put them into /home/akda/Kinematic . That's also were examples live</li>
 <li>adapt script that calls solve (check whether you need a rapid solution -- when orbits aren't in yet)</li>
 <li>run solution</li>

@@ Line 24: / Line 24: @@
 <li>add the <code>-nosvclkfile</code> flag to your <code>solve</code> call, to make sure the satellite clocks are not used ...</li>
 <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>
 <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>
 </ul>

@@ Line 23: / Line 23: @@
 <li>copy the orbits for the repective day(s) into /gps/data/CAMPAIGN_NAME-interval/orbit</li>
 <li>add the <code>-nosvclkfile</code> flag to your <code>solve</code> call, to make sure the satellite clocks are not used ...</li>
-<li>or get high resolution clocks for the respective days from [ftp://sideshow.jpl.nasa.gov/pub/gipsy_products/hrclocks/] and copy those into /gps/data/CAMPAIGN_NAME-interval/orbit </li>
+<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>
 <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>
 </ul>

@@ Line 21: / Line 21: @@
 where $procdir=/gps/data/CAMPAIGN_NAME-interval, i.e. the campaign directory you just created.
 </li>
-<li>copy the orbits for the repective day(s) into /gps/data/CAMPAIGN_NAME-interval/orbits</li>
+<li>copy the orbits for the repective day(s) into /gps/data/CAMPAIGN_NAME-interval/orbit</li>
-<li>add the <code>-nosvclkfile</code> flag to your <code>solve</code> call, to make sure the satellite clocks are not used.</li>
+<li>add the <code>-nosvclkfile</code> flag to your <code>solve</code> call, to make sure the satellite clocks are not used ...</li>
 <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>
 </ul>