Arrival of new flight data

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 NERC-ARF Operations.

Project Set Up

A semi-automated procedure -> Procedures/NewDataArrival/ProjectSetUp

Logsheet and Remaining Steps

• 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:

• Run from top level - writes into 'admin' dir. You may wish to rename this dir before running to prevent any accidental overwriting.
• Fill in the yellow boxes with information from supplied logsheet.
• Blue boxes should be automatically filled in when you start the program but check the values are correct.
• Click 'fill post manual'. This will calculate the values for the green fields based on the values you have entered into the yellow fields. You should also check that these fields look correct. If the flight was flown over midnight, you may need to correct them.

Tickets and tracking

Status Page

Add details to the ​processing status page. Under 'Data location' use the full path to the project and do NOT include server name (e.g use /users/rsg/arsf/... and not /data/visuyuan/...).

Ticket

Raise a ​new trac ticket (type 'flight processing') for the new data.

• Ticket summary should be of the form EU10/03, flight day 172/2011, Dennys Wood
• Add short version of scientific purpose to guide processing (check NERC-ARF application)
• Note arrival time of data
• Set priority of ticket from project grading (try the grades subpages on Projects)
• Note any specific comments that might help with processing
• Owner should be blank
• Verify the sensors that were requested in the application (primary) and those that weren't (secondary). Note in the ticket which these were.
• Ticket body should contain:

  Data location: ~arsf/arsf_data/2011/flight_data/..... FILL IN
  
  Data arrived from NERC-ARF via SATA disk LETTER OR network transfer on DATE.
  
  Scientific objective: FILL IN FROM APPLICATION (just enough to guide processing choices)
  
  Priority: FILL IN FROM APPLICATION/WIKI PAGE (e.g. alpha-5 low), set ticket priority appropriately
  
  PI: A. N. Other
  EUFAR Project ID:
  CAFAM code: 
  
  Any other notes..
  
  = Sensors: =
   * 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)
  

Create KML overview

When happy the directory is unpacked correctly run make_kmloverview.py. This will generate the web page and quicklooks of the data that are made available to the user. It will also generate a password which should be included in the email below. Check the username and password works by commenting out the following line:

Allow from env=internal_proxy

from processing/kml_overview/.htaccess as this means a password isn't required for internal access. Remember to uncomment once you have finished.

Vectors

If the site is in the UK, check the 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 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
  • the username and password are available in the .htaccess file in processing/kml_overview or ~arsf/usr/share/kmlpasswords.csv. Note that make_kmloverview.py will need to have been run to create a password first unless the project code already exists for previous data.
• cc to nerc-arf-processing
• also cc to neodc@rl.ac.uk
• set reply-to to nerc-arf-processing
• subject: NERC-ARF data arrival notification (<PROJECT> [<EUFAR ID>])

  Dear <PI_NAME>,
  
  This is a notification that your NERC-ARF data for <PROJECT> [<EUFAR ID>], flown on
  <CALENDAR_DAY(S)>, are at the NERC-ARF Data Analysis Node for processing (data
  received from NERC-ARF Operations on <DATE_OF_ARRIVAL>).
  
  We aim to deliver as quickly as possible - our current processing 
  priority order can be found at http://arsf-dan.nerc.ac.uk/status/order/ 
  though please note that this queue is subject to change.
  
  You can follow progress at the following webpages:
  
   http://arsf-dan.nerc.ac.uk/status/progress/
    - general status page
  
   http://arsf-dan.nerc.ac.uk/trac/ticket/<TICKETNO>
    - our notes during processing (may be technical)
  
  Also available are KML (Google Earth) files that will allow you to view flight data 
  coverage. These files are updated as the data are processed and more information 
  becomes available. Click the following link and enter username and password details as 
  below:
  
  <INSERTWEBLINKHERE>
  
  username: <USERNAME>
  password: <PASSWORD>
  
  Further information on KML previews:
  
   http://arsf-dan.nerc.ac.uk/trac/wiki/ProcessingAtDAN/KMLoverview
  
  If there are any specific processing requirements, or if you have additional data that may help with the processing (e.g. GPS basestation data, ground or atmospheric measurements), please contact us directly so we can take account of this before beginning processing.
  
  If you would like any more information, please feel free to contact us at arsf-processing@pml.ac.uk
  
  Regards,
  
  

Once the PI has been emailed commit the updated KML password file to ~arsf/live_git_repos/config_files/ (no need to push changes).

Basestation

Check there is basestation data for the flight. If not, ask ops if they have some or if we need to download it.