Changes between Version 26 and Version 27 of Procedures/EagleHawkProcessing


Ignore:
Timestamp:
Oct 22, 2010 10:35:34 AM (9 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/EagleHawkProcessing

    v26 v27  
    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 Config file ==
     5== Creating the Config file ==
    66
    77generate_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.
     
    4545Check these for errors (look for stars). Check the errors against the [#Problems example errors] below.
    4646
    47 Check against OS vectors.
     47Now you need to find and record the correct SCT value for each flightline. Look for wobbles in straight lines and try to correct them. Once you have a value for each flightline, enter this for the start and end sct variables in the config file for each flightline. Run once more and the script will no longer delete the lev1s. These are the final product to go in the delivery.
     48
     49Check against OS vectors if this is a UK project.
    4850
    4951=== Old-fashioned way ===