Data location: /data/larsenb1/scratch/arsf/vocals/vocals-Q/voc11-31508 (symlink in ~arsf/arsf_data/2008/flight_data/vocals/VOC_11-2008_315_Chile)

Data arrived from ARSF via SATA disk Q on 12th December 2008.

Scientific details: VOCALS cloud campaign

Priority:

PI: G. Vaughan

Sensors:

• Eagle
• Hawk

Quicklook

TBD.

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. 

Specim calibrated the Eagle and Hawk sensors at the start of the 2009 season. We need to validate the calibration as best we can - this will primarily require an independent verification by FSF.

Mismatches in the overlap region between Eagle and Hawk still exist, as in previous years: