Version 21 (modified by mark1, 16 years ago) (diff)

--

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.

Permissions fixing

Ensure permissions on the SATA disk are correct and all files readable ("chmod a+rX /mnt/satadisk" as root)

Copying to PML data storage

Copy to appropriate location on the filesystem (~arsf/arsf_data/in_progress/2007/flight_data/...)

  • when copying from the source media, preserve timestamps with cp -a or rsync -av
  • ensure the directory name conforms to the standard - PROJECTCODE-YYYY_JJJxx_SITENAME, e.g. GB07_07-2007_102a_Inverclyde, boresight-2007_198, etc
  • rename any capitalised subdirectories
  • remove any spaces, brackets or other Unix-upsetting characters in filenames
  • move DCALM* files to applanix/Raw
  • prune empty directories (check these aren't stubs for later data first) use rmdir *

Verification

Look at the logsheet and verify that we have copies of all relevant data mentioned there.

Tickets and tracking

Raise a trac ticket (type 'flight processing') for the new data, then add details to the processing status page.

  • ticket summary should be of the form BGS07/02, flight day 172/2007, Keyworth
  • add scientific summary (check ARSF application in ~arsf/arsf_data/in_progress/2007/ARSF_Applications-GB_2007)
  • note arrival time of data
  • note any specific comments that might help with processing
  • ticket body should contain:
    Data location: ~arsf/arsf_data/in_progress/2007/flight_data/uk/GB04_19-2007_102b_Nigg_Bay
    
    Data arrived from ARSF via initial SATA disk transfer in June.
    
    Scientific details: (details of 2004 applications not available at PML)
    
    PI: A. N. Other
    
    Any other notes..
    
    == Sensors: ==
     * ATM
     * CASI
     * Eagle
     * Hawk
    
    == Quicklook ==
    
    TBD.