Changes between Version 21 and Version 22 of Procedures/NewDataArrival
- Timestamp:
- May 19, 2008, 5:39:16 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/NewDataArrival
v21 v22 12 12 * when copying from the source media, preserve timestamps with `cp -a` or `rsync -av` 13 13 * 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) 14 15 * rename any capitalised subdirectories 15 16 * 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 {} \; 16 19 * 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` 18 22 23 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. 19 24 == Verification == 20 25 Look at the logsheet and verify that we have copies of all relevant data mentioned there. 26 27 Check the filesizes of all data files (Eagle, Hawk, ATM, CASI) to make sure none aer 21 28 22 29 == Tickets and tracking ==