Changes between Version 21 and Version 22 of Procedures/NewDataArrival


Ignore:
Timestamp:
May 19, 2008 5:39:16 PM (11 years ago)
Author:
mggr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NewDataArrival

    v21 v22  
    1212 * when copying from the source media, preserve timestamps with `cp -a` or `rsync -av`
    1313 * ensure the directory name conforms to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB07_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc
     14 * prune empty directories (check these aren't stubs for later data first) (use `rmdir *` in the project directory)
    1415 * rename any capitalised subdirectories
    1516 * remove any spaces, brackets or other Unix-upsetting characters in filenames
     17   * use `find -regex '.*[^-0-9a-zA-Z/._].*' | ~arsf/usr/bin/fix_naughty_chars.py` to give suggested commands, but check before pasting commands!
     18 * remove executable bit on all files -> find -type f -exec chmod a-x {} \;
    1619 * move DCALM* files to applanix/Raw
    17  * prune empty directories (check these aren't stubs for later data first) use `rmdir *`
     20 * bzip lidar files, `bzip lidar/*`
     21 * remove group & other write permission, `chmod go-w . -R`
    1822
     23In 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. 
    1924== Verification ==
    2025Look at the logsheet and verify that we have copies of all relevant data mentioned there.
     26
     27Check the filesizes of all data files (Eagle, Hawk, ATM, CASI) to make sure none aer
    2128
    2229== Tickets and tracking ==