Changes between Version 29 and Version 30 of Procedures/NewDataArrival


Ignore:
Timestamp:
Jul 29, 2008 12:20:37 PM (11 years ago)
Author:
mark1
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NewDataArrival

    v29 v30  
    1010== Copying to PML data storage ==
    1111Copy to appropriate location on the filesystem (~arsf/arsf_data/in_progress/2007/flight_data/...)
     12
     13=== Scripting  method ===
     14  * when copying from the source media, preserve timestamps with `cp -a` or `rsync -av`
     15  * in the directory above the new project directories (eg '../flight_data/unpacking/') run 'folder_structure.py --dry-run'
     16    * using --dry-run will output the commands it will run to the terminal to check it looks ok
     17    * if happy, either re-run without --dry-run or cut/paste commands
     18    * Each project directory should be re-formatted to the current standard
     19  * in each project directory run 'file_check.py -l <admin/logsheet.doc(.txt)>'
     20    * This will convert .doc logsheet to .txt, or use the .txt if one available
     21    * 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.
     22      * Check file sizes against a 'suitable' size and also against header file (Eagle + Hawk)
     23      * Check number of files against logsheet
     24      * Check number of logsheets
     25      * Check GPS start/stop times in header file (Eagle + Hawk)
     26      * Check .raw, .nav, .log, .hdr for each Eagle + Hawk line
     27=== Non-scripting  method ===
    1228 * when copying from the source media, preserve timestamps with `cp -a` or `rsync -av`
    1329 * ensure the directory name conforms to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB07_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc