Changes between Version 16 and Version 17 of Procedures/EagleHawkProcessing


Ignore:
Timestamp:
Oct 14, 2010 2:48:50 PM (9 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/EagleHawkProcessing

    v16 v17  
    33Once the [wiki:Procedures/NewDataArrival data have been unpacked] and the [wiki:Procedures/ProcessingChainInstructions/NavigationProcessing nav data have been processed], the Eagle/Hawk data need to be run through the [wiki:Processing/Flow AZ Systems processing chain] (primarily azspec, azimport, aznav and azgcorr).
    44
    5 == Create the processing scripts ==
     5== Create the Config file ==
    66
    7 To use generate_runscripts.py the navigation must first be processed and an sbet file located in the applanix/proc directory.   
    8 There are now some new ways to create run scripts for the Eagle and Hawk using the generate_runscripts.sh script.  If no log sheet is available, one can use the keywords on the command line to specify the global variables, such as:
     7generate_runscripts.py is the script used to create the config file, which is in turn used to process the eagle and hawk lines. Before beginning, make sure the raw files are present as well as a processed navigation (sbet) file in applanix/proc and a suitable dem (see below). You may also need to create a text version of the logsheet.
     8
     9Run with -h flag to get full usage help. An example command is below:
     10
     11generate_runscripts.py -s s -n 5 -j 196 -y 2010 -l admin/196-10_Eufar10-03.txt
     12
     13There are now some new ways to create run scripts for the Eagle and Hawk using the generate_runscripts.sh script. 
     14If no log sheet is available, one can use the keywords on the command line to specify the global variables, such as:
    915
    1016 --PI="P.I. Name" --PROJCODE=EX09_01
     
    3238
    3339Always check for '?' within the script for missing information.
    34 
    3540
    3641== Processing the Lines ==