Changes between Version 190 and Version 191 of Procedures/NewDataArrival

Timestamp:

Feb 3, 2017, 12:15:24 PM (8 years ago)

Author:

asm

Comment:

--

Procedures/NewDataArrival

@@ -3 +3 @@
 This procedure should be followed on receipt of new flight data from NERC-ARF.
 
-If in any doubt about something (e.g. a dataset has two project codes), contact Gary.
+If in any doubt about something (e.g.: a dataset has two project codes), contact NERC-ARF Operations.
 
 == Project Set Up ==
-'''Warning''': proj_tidy.sh is becoming deprecated so use this instructions instead -> [wiki:Procedures/NewDataArrival/ProjectSetUp]
+A semi-automated procedure -> [wiki:Procedures/NewDataArrival/ProjectSetUp]
 
 
-== Verification ==
 
-=== Manual checks ===
+=== Logsheet and Remaining Steps===
 
- * 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.
- * Check the filesizes of all data files (Eagle, Hawk, ATM, CASI) to make sure none are zero bytes (or obviously broken in some way).
- * Verify the details on the logsheet (esp. PI) by calling/emailing NERC-ARF 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. Get the alpha grading as well.
-
-
-== Generate Logsheet ==
+ * Look at the logsheet included 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 write in the ticket any changes made for tracking purposes.
+ * Verify the details on the logsheet (esp. PI) by calling/emailing NERC-ARF Ops - the application form and logsheet are not sufficient proof, nor do they track any changes in PI over the lifetime of the application.
 
 Make a logsheet that is suitable for delivery to end users. Use the {{{generateLogsheet.py}}} script and follow instructions from:
@@ -61 +56 @@
 
 = Sensors: =
- * Eagle (requested)
- * Hawk  (requested)
- * Leica LIDAR (not requested but flown anyway)
- * RCD (requested)
+ * Fenix (requested/not requested, flown/not flown)
+ * Leica LIDAR (requested/not requested, flown/not flown)
+ * OWl (requested/not requested, flown/not flown)
+ * RCD (requested/not requested, flown/not flown)
 }}}
 
@@ -77 +72 @@
 == Vectors ==
 
-If the site is in the UK, check the [wiki:vectors vector page] to see if we have vectors for the site in question. If not then email NERC-ARF-Ops (Gary) and ask for them, specifying the corner points of the area covered, in OS BNG grid coordinates. Use bounding_box.py (needs to be ran in the project directory) or use the generated nextmap DEM (below) to get the range of tiles, then do the conversion. It can take a couple of weeks before we get the vectors.
+If the site is in the UK, check the [wiki:vectors vector page] to see if we have vectors for the site in question. If not, then email NERC-ARF-Ops and ask for them specifying the corner points of the area covered  in OS BNG grid coordinates. Use bounding_box.py (needs to be run in the project directory) or use the generated nextmap DEM (below) to get the range of tiles, then do the conversion. It can take a couple of weeks before we get the vectors.
 
 == E-mail PI ==
 
-Email the PI to inform them that their data has arrived for processing.  Sample text:
+Email the PI to inform them that their data has arrived to the Data Analysis Node for processing.  Sample text:
  * fill in the 7 fields: <PI_NAME>, <PROJECT>, <EUFAR ID> <TICKET_NO>, <DATE_OF_ARRIVAL>, <USERNAME>, <PASSWORD>, <INSERTWEBLINKHERE>
    * the date of arrival should be when the disks arrived or when the download begun