Changes between Version 91 and Version 92 of Procedures/NewDataArrival


Ignore:
Timestamp:
Sep 30, 2009 3:05:59 PM (10 years ago)
Author:
emca
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NewDataArrival

    v91 v92  
    8888 * In some cases, the flight crew may fly two projects back-to-back but enter all the data onto a single logsheet.  If so, you may need to split the project directory into two, particularly if there's a large time gap (navigation needs separate processing) or the PIs are different (different delivery addresses/tracking).  If you do need to split a project, ensure both copies have copies of common files (logsheets, rinex, etc), but that non-common files are not duplicated (ie. don't include hawk data for part 1 in part 2..).  Also note in the ticket what was done for tracking purposes.
    8989
    90 Verify the details on the logsheet (esp. PI) are correct by cross-referencing against the ARSF application form.  If we do not have the application, call Kidlington to verify.
     90Verify the details on the logsheet (esp. PI) are correct by cross-referencing against the ARSF application form.  If we do not have the application, call Gloucester to verify.
    9191
    9292Check the filesizes of all data files (Eagle, Hawk, ATM, CASI) to make sure none are zero bytes (or obviously broken in some way).