Changes between Version 121 and Version 122 of Procedures/NewDataArrival

Timestamp:

Sep 29, 2010, 1:00:39 PM (14 years ago)

Author:

knpa

Comment:

--

Procedures/NewDataArrival

@@ -65 +65 @@
 Look at the logsheet and verify that we have copies of all relevant data mentioned there.
  * 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.
-
-(Please ignore this - we are currently unsure how to handle out of order flightline numbers) Edit the logsheet flight line numbers to be in an increasing order.
 
 Verify 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.