Changes between Version 101 and Version 102 of Procedures/NewDataArrival


Ignore:
Timestamp:
Feb 10, 2010 2:09:26 PM (10 years ago)
Author:
mark1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NewDataArrival

    v101 v102  
    6666Look at the logsheet and verify that we have copies of all relevant data mentioned there.
    6767 * 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.
     68
     69Edit the logsheet flight line numbers to be in an increasing order.
    6870
    6971Verify the details on the logsheet (esp. PI) by calling/emailing ARSF-Ops (probably Gary) - the application form and logsheet are not reliable enough, nor do they track any changes in PI over the lifetime of the application.