Using the -mTMS flag in azgcorr to denote southern-hemisphere processing causes either a segfault or north-south inverted results. Have had a couple of potential fixes exchanged with Bill (not quite right yet though), raising this mostly to go with the work order.

Attempting to re-interpolate the nav/scan timing on CASI data for flight 97/14 using aznav, the program seems to edit the HDF files correctly but then doesn't release the file lock (gives error "There are still open AIDs" on closing). Everything seems fine but then it causes azgcorr to hang part-way through. It is believed this is because the old data is HDF 3.3 format (rather than HDF 4) and there are compatibility problems.

Data location: /data/larsenb1/scratch/arsf/vocals/VOC_04-2008_305_Chile (symlink in ~arsf/arsf_data/in_progress/2008/flight_data/vocals/VOC_01-2008_305_Chile/)

Data arrived from ARSF via SATA disk Linex Backup 2 on 12th December 2008.

Scientific details: VOCALS cloud campaign

Priority:

PI: Hugh Coe

Sensors:

• Eagle
• Hawk

Quicklook

TBD.