Arrival of new flight data

This procedure should be followed on receipt of new flight data from ARSF.

If in any doubt about something (e.g. a dataset has two project codes), contact Gary.

Copy the data onto the system

• Data by SATA disk or DVD
• Data by network transfer

After successfully copying the data onto the system, email arsf-processing to confirm the data transferred ok (but hasn't yet been checked!).

Create entry on flight data status spreadsheet for each project

• Note time of disk arrival
• Currently located ~arsf/docs/flight_data_status/YYYY/flight_data_status_YYYY.xls

Move to permanent PML data storage

Check there is space in the repository for the project (du -hs ~arsf/arsf_data/YYYY/flight_data and du -hs location_of_project_to_unpack). If not then skip this bit and copy to the workspace instead, but put a comment in the ticket so we can rsync it to the repository later.

Move to appropriate location on the filesystem (~arsf/arsf_data/2009/flight_data/...)

• ensure the project directory names conform to the standard - PROJECTCODE-YYYY_JJJxx_SITENAME, e.g. GB07_07-2007_102a_Inverclyde, boresight-2007_198, etc

The next stage can be manual or semi-automatic:

Semi-scripted method

• in the directory above the new project directories (eg '../flight_data/unpacking/') run 'unpack_folder_structure.py'
  • by default, it runs safely in a dry-run mode and will output the commands it will run to the terminal. Check these look ok.
  • if happy, either re-run with --execute (and optionally --verbose)
  • Each project directory should be re-formatted to the current standard
• in each project directory run 'unpack_file_check.py -l <admin/logsheet.doc(.txt)>'
  • This will convert .doc logsheet to .txt, or use the .txt if one available. NOTE to convert to .doc requires ooffice macro
  • Will then do various checks of data against logsheet as listed below. Information will be output to terminal. Important (error) messages are printed again at the end.
    • Check file sizes against a 'suitable' size and also against header file (Eagle + Hawk)
    • Check number of files against logsheet
    • Check number of logsheets
    • Check GPS start/stop times in header file (Eagle + Hawk)
    • Check .raw, .nav, .log, .hdr for each Eagle + Hawk line
    • Check for nav-sync issues - THIS IS BASED ON A FALSE ASSUMPTION AND PROBABLY IS USELESS
• Copy project structure with sym links to ~arsf/workspace. You can either do this manually or with:

fastcopy_arsf_proj_dir.sh <source project directory> <target project directory>

Note: Be logged in airborne when you create the directory and the initial files in the workspace or you won't have write permission.

• Obsolete: Only do this to generate old-style scripts. For each project directory run 'generate_qsub.py -d <project directory>'
  • This will generate a qsub command script for use to submit processing of all eagle, hawk, atm and casi flight lines to the grid nodes.

Non-scripting method

• prune empty directories (check these aren't stubs for later data first) (use rmdir * in the project directory)
• rename any capitalised subdirectories
• remove any spaces, brackets or other Unix-upsetting characters in filenames
  • use find -regex '.*[^-0-9a-zA-Z/._].*' | ~arsf/usr/bin/fix_naughty_chars.py
  • gives suggested commands, but check before pasting commands!
• remove executable bit on all files
  • use find -type f -exec chmod a-x {} \;
• move DCALM* files to applanix/raw
• bzip lidar files
  • bzip lidar/*
• remove group & other write permission
  • chmod go-w . -R
• Convert the .doc logsheet to .pdf
  • ooffice -invisible "macro:///Standard.Module1.SaveAsPDF(FULL_PATH_TO_FILE)"

Verification

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.

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.

Check the filesizes of all data files (Eagle, Hawk, ATM, CASI) to make sure none are zero bytes (or obviously broken in some way).

In the base of the project directory run:
proj_tidy.sh .
This will check that the directory structures look sensible and tell you where they don't. Correct anything significant that gets flagged up.

Create subsidiary files

Run the DEM generating script if a UK flight. nextmapdem.sh

Create the calibration sym link. This is done automatically if the unpacking scripts have been run.

If the flight is outside the UK you'll need to process the LiDAR data first or use the SRTM dem (see ​http://arsf-dan.nerc.ac.uk/trac/wiki/Processing/SRTMDEMs)

(Not necessary any more) Run times4grafnav.py script to create a text file of time stamps and put the output into the applanix directory. May be of use for the GNSS processing.

Tickets and tracking

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

• ticket summary should be of the form BGS07/02, flight day 172/2007, Keyworth
• add short version of scientific purpose to guide processing (check ARSF application in ~arsf/arsf_data/2009/ARSF_Applications)
• note arrival time of data
• set priority of ticket from project grading (try Internal/ProjectGradings? or the application, or hassle ARSF-Ops)
• note any specific comments that might help with processing
• owner should be blank
• ticket body should contain:

  Data location: ~arsf/arsf_data/2009/flight_data/..... FILL IN
  
  Data arrived from ARSF 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
  
  Any other notes..
  
  == Sensors: ==
   * Eagle
   * Hawk
   * Leica LIDAR
  

When done, add details to the ​processing status page and to the processing order page.

Vectors

If the site is in the UK, check the requested OS vectors wiki page? to see if we have vectors for the site in question. If not then email ARSF-Ops (Gary) and ask for them, specifying the 4 corner points of the area covered, in OS BNG grid coordinates (use the generated nextmap DEM to get the range of tiles, then do the conversion). This can take a couple of weeks before we get the vectors.

Finally..

Email the PI to inform them that their data has arrived for processing. Sample text:

• fill in the 4 fields: <PI_NAME>, <PROJECT>, <TICKET_NO>, <DATE_OF_ARRIVAL>
  • the date of arrival should be when the disks arrived or when the download begun
• cc to arsf-processing
• set reply-to to arsf-processing
• subject: ARSF data arrival notification (<PROJECT>)

  Dear <PI_NAME>,
  
  This is a notification that your ARSF data for <PROJECT> is at the
  ARSF Data Analysis Node for processing (data received from ARSF 
  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/trac/wiki/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/status.php
    - general status page
  
   http://arsf-dan.nerc.ac.uk/trac/ticket/<TICKETNO>
    - our notes during processing (may be technical)
  
  If you would like any more information, please feel free to contact us at arsf-processing@pml.ac.uk
  
  Regards,