Changes between Version 34 and Version 35 of Procedures/EagleHawkProcessing


Ignore:
Timestamp:
Jul 4, 2011 11:41:13 AM (8 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/EagleHawkProcessing

    v34 v35  
    5252=== Problems ===
    5353
    54 '''Sync'''
    55 
    56 If you get something in the log file like:
    57 
    58 ** End of POSATT file with NO Specim sync found
    59 ** no sync within 5.00 secs of raw file header time: 49915.66
    60 
    61 then there is no sync info in the nav file for that line and and the range of possible sct values will increase (up to a few seconds). You will need to include 'has_sync = false' in the config file line entry and input a wider range of scts, e.g.
    62 
    63 [hawk_-11]
    64 ...
    65 ...
    66 ...
    67 has_sync = false
    68 sctend = -1
    69 sctincrement = -0.1
    70 sctstart = 1
    71 
    72 [hawk_-12]
    73 ...
    74 
    75 A less likely reason for the above output is that the raw header file in question contains invalid GPS times (either start time or end time) and therefore also results in not lying within the times of the .nav file. If both GPS Starting Position and GPS Start Time are missing (accordingly for End Position/End Time) then the best guess is to replace the invalid time/position with the raw header file from the other sensor (eagle/hawk), making sure that it is the correct corresponding flightline. If only one of the two are missing, time or position, then the navigation files should be used to find the missing data, this is easier done when the position is missing (open .gpb file from applanix/extract) but still possible when the time is missing (.gpb again, but will have to track position).
    76 
    77 '''Turns'''
    78 
    79 If you get something in the log file like:
    80 
    81 ** flight line may have a turn in it **
    82 ** heading spread over approximately: 120 degs **
    83 
    84 ** run terminated due to turn **
    85 
    86 then there is a bend in the line that is too sharp. You need to add a -bend flag to the azcorr arguments for the line entry in the config file, e.g.
    87 
    88 [eagle_-7]
    89 ...
    90 ...
    91 ...
    92 azgcorr_args_extra = -bend
    93 
    94 [eagle_-8]
    95 ...
    96 
    97 Once processed, it is best to exclude the lines which are causing the problems by including a -l flag in azspec followed by the line numbers delineating the part of the line you want to keep, then reprocessing. E.g. if the bend is at the start of the line:
    98 
    99 [eagle_-7]
    100 ...
    101 ...
    102 ...
    103 azgcorr_args_extra = -bend
    104 azspec_args_extra = -l 50 2000
    105 
    106 will exclude the first 50 lines. Make sure the second value takes into account dark frames: the number of lines given in the header file will include dark frames and if you want to process to the end of the line you should therefore specify the line number before the figure given in 'autodarkstartline' (also in the header file).
     54[wiki:Processing/problemsHS This] page details common problems in hyperspectral processing, and how to resolve them.
    10755
    10856=== Making a delivery ===