Changes between Version 126 and Version 127 of Procedures/NewDataArrival


Ignore:
Timestamp:
Oct 1, 2010 12:26:37 PM (9 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NewDataArrival

    v126 v127  
    2626    * If happy, either re-run with --execute (and optionally --verbose)
    2727    * Each project directory should be re-formatted to the current standard
    28   * In each project directory run 'unpack_file_check.py -l <admin/logsheet.doc(.txt)>'
    29     * This will convert .doc logsheet to .txt, or use the .txt if one available. NOTE to convert to .doc requires ooffice macro
    30     * 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.
    31       * Check file sizes against a 'suitable' size and also against header file (Eagle + Hawk)
    32       * Check number of files against logsheet
    33       * Check number of logsheets
    34       * Check GPS start/stop times in header file (Eagle + Hawk)
    35       * Check .raw, .nav, .log, .hdr for each Eagle + Hawk line
    36       * Check for nav-sync issues - THIS IS BASED ON A FALSE ASSUMPTION AND PROBABLY IS USELESS
    3728
    3829=== Non-scripting  method ===
     
    5243== Verification ==
    5344
     45= Unpack File Check =
     46
     47In each project directory run 'unpack_file_check.py -l <admin/logsheet.doc(.txt)>'
     48  * This will convert .doc logsheet to .txt, or use the .txt if one available. NOTE to convert to .doc requires ooffice macro
     49  * 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.
     50    * Check file sizes against a 'suitable' size and also against header file (Eagle + Hawk)
     51    * Check number of files against logsheet
     52    * Check number of logsheets
     53    * Check GPS start/stop times in header file (Eagle + Hawk)
     54    * Check .raw, .nav, .log, .hdr for each Eagle + Hawk line
     55    * Check for nav-sync issues - THIS IS BASED ON A FALSE ASSUMPTION AND PROBABLY IS USELESS
     56
     57= proj_tidy.sh  =
     58
     59In the base of the project directory run proj_tidy:[[BR]]
     60`proj_tidy.sh -d ./ -e`[[BR]]
     61This will check that the directory structures look sensible and tell you where they don't. Correct anything significant that gets flagged up.
     62
     63= Final manual checks =
     64
    5465Look at the logsheet and verify that we have copies of all relevant data mentioned there.
    5566 * 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.
     
    5869
    5970Check the filesizes of all data files (Eagle, Hawk, ATM, CASI) to make sure none are zero bytes (or obviously broken in some way).
    60 
    61 In the base of the project directory run proj_tidy:[[BR]]
    62 `proj_tidy.sh -d ./ -e`[[BR]]
    63 This will check that the directory structures look sensible and tell you where they don't. Correct anything significant that gets flagged up.
    6471
    6572== Move to permanent PML data storage ==
     
    73802. Copy project structure with sym links to ~arsf/workspace. You can either do this manually or with:
    7481
    75       fastcopy_arsf_proj_dir.sh <source project directory> <target project directory>
     82   fastcopy_arsf_proj_dir.sh <source project directory> <target project directory>
     83
    7684   Note: Be logged in airborne when you create the directory and the initial files in the workspace or you won't have write permission.
    7785   * '''Obsolete: Only do this to generate old-style scripts.''' For each project directory run 'generate_qsub.py -d <project directory>'
     
    8290Run the DEM generating script if a UK flight. `nextmapdem.sh`
    8391
     92If 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)
     93
    8494Create the calibration sym link. This is done automatically if the unpacking scripts have been run.
    85 
    86 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)
    8795
    8896(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.