Changes between Version 17 and Version 18 of Procedures/EagleHawkProcessing


Ignore:
Timestamp:
Oct 14, 2010 3:24:46 PM (9 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/EagleHawkProcessing

    v17 v18  
    1010
    1111generate_runscripts.py -s s -n 5 -j 196 -y 2010 -l admin/196-10_Eufar10-03.txt
     12 
     13Beware that the method is not robust and may fill in the wrong data details, especially for the per-line information.
     14For unknown variables (global or flight line specific) a "?" will be inserted in the config file and should be replaced by hand.
    1215
    13 There are now some new ways to create run scripts for the Eagle and Hawk using the generate_runscripts.sh script. 
    14 If no log sheet is available, one can use the keywords on the command line to specify the global variables, such as:
     16If no log sheet is available, one can use the keywords on the command line to specify the global variables, using "" if requires a space within the name: 
    1517
    16  --PI="P.I. Name" --PROJCODE=EX09_01
     18generate_runscripts.py -s s -n 4 --JDAY=200 --YEAR=2009 --PI="P.I. Name" --SITE="Over There" --PROJCODE=EX01_99
    1719
    18 using "" if requires a space within the name.  For unknown variables (global or flight line specific) a "?" will be inserted in the script and should be replaced by hand. For a full list of keywords and their default values run: generate_runscripts.py -h
     20Adding keywords to the command line and using a logsheet results in the command line keywords taking precedent over the logsheet keyword.
     21For a full list of keywords and their default values run: generate_runscripts.py -h.
    1922
    20 EG:   generate_runscripts.py -s s -n 4 --JDAY=200 --YEAR=2009 --PI="P.I. Name" --SITE="Over There" --PROJCODE=EX01_99
    21 
    22 If a logsheet is available you can run the script as before, but beware that the method is not robust and may fill in the wrong data details, especially for the per-line information. 
    23 
    24 EG:   generate_runscripts.py -s s -n 4 --JDAY=200 --YEAR=2009 -l admin/logsheet.TXT
    25 
    26 To use the logsheet just for the global variables you can add to command line --NOPERLINELOG. This will then use the logsheet for global variables, but not for per flight line values. For the per flight line values it will use liblogwriter.py and the raw eagle/hawk header and sbet files to extract average values for the speed/altitude/direction. But using this method will not name the scripts by flight line order on the logsheet, but by the filename of the raw data.
    27 
    28 EG:   generate_runscripts.py -s s -n 4 --JDAY=200 --YEAR=2009 -l admin/logsheet.TXT --NOPERLINELOG
    29 
    30 Use the --NOPERLINELOG parameter if you wish to manually add the per line data to the config file.
     23To use the logsheet just for the global variables you can add to command line --NOPERLINELOG. This will then use the logsheet for global variables, but not for per flight line values. For the per flight line values it will use liblogwriter.py and the raw eagle/hawk header and sbet files to extract average values for the speed/altitude/direction. But using this method will not name the scripts by flight line order on the logsheet, but by the filename of the raw data. Use the --NOPERLINELOG parameter if you wish to manually add the per line data to the config file.
    3124
    3225Use the --EXCLUDE="n1 n2 n3 ... -1 m1 m2 m3... -1" parameter if you want to exclude line numbers from the config file.
    3326In this case -n linesNo, linesNo can be the number of lines with the previously specified ones excluded.
    34 
    35 '''NOTE:'''
    36 
    37 Adding keywords to the command line and using a logsheet results in the command line keywords taking precedent over the logsheet keyword.
    38 
    39 Always check for '?' within the script for missing information.
    4027
    4128== Processing the Lines ==