Changes between Version 5 and Version 6 of Procedures/EagleHawkProcessing

Timestamp:

Aug 4, 2010, 12:51:25 PM (14 years ago)

Author:

knpa

Comment:

--

Procedures/EagleHawkProcessing

@@ -75 +75 @@
  1. Check against OS vectors
 
+== Problems ==
+
+'''Sync'''
+
+If you get something in the log file like:
+
+** End of POSATT file with NO Specim sync found[[BR]]
+**     no sync within 5.00 secs of raw file header time: 49915.66
+
+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. 
+
+[hawk_-11] [[BR]]
+...[[BR]]
+...[[BR]]
+...[[BR]]
+has_sync = false[[BR]]
+sctend = -1[[BR]]
+sctincrement = -0.1[[BR]]
+sctstart = 1[[BR]]
+
+[hawk_-12][[BR]]
+...
+
+'''Turns'''
+
+If you get something in the log file like:
+
+** flight line may have a turn in it **[[BR]]
+** heading spread over approximately:  120 degs **
+
+** run terminated due to turn **
+
+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.
+
+[eagle_-7][[BR]]
+...[[BR]]
+...[[BR]]
+...[[BR]]
+azgcorr_args_extra = -bend
+
+[eagle_-8][[BR]]
+...
+
+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:
+
+
+[eagle_-7][[BR]]
+...[[BR]]
+...[[BR]]
+...[[BR]]
+azgcorr_args_extra = -bend[[BR]]
+azspec_args_extra = -l 50 2000
+
+will exclude the first 50 lines.
+
 ----