Initial contact from Abdulwasey, who was having problems processing atmospheric corrected versions of his data.

Project is GB06-07_241a_Silverflowe (Eagle, Hawk, ATM, though he may not be using Hawk?). See ticket #63 for processing/delivery info.

Descriptive email from Ben to Bill (4/Mar/2009):

We were (still) trying to track down our Vocals offset problem and we think we stumbled across something else. We used CaliGeo to process a line that had had a timing error in it when we'd processed it using the az suite, and CaliGeo didn't produce a timing problem.

We noticed that in the bit where Caligeo is looking for sync the message it finds has a time delay of 548ms, which matches the 548 in the "Navsync Timing" line on the line 5 header file. The previous sync message it found (and discarded) had a time delay of 119ms, which matches the Navsync Timing for line 4. Azimport for that line found a specim sync message offset of 0.119, which suggests to me that it actually picked up the sync message for line 4 rather than 5. Can you take a look at this when you get a chance please? Let me know if I can send you any additional test data. 

Data location: ~arsf/arsf_data/2009/flight_data/arsf_internal/boresight_2009-131_little_riss

Data arrived from ARSF via SATA disk F on 12th May 2009.

Boresight flight

Sensors:

• Eagle
• Hawk