Opened 2 weeks ago

Last modified 4 days ago

#727 new flight processing

FIDEXII/23, flight day 231/2023, Canada

Reported by: asm Owned by:
Priority: immediate Milestone:
Component: Processing: general Keywords:
Cc: Other processors:

Description

Data location: /users/rsg/arsf/arsf_data/2023/flight_data/canada/FIDEXII-2023_231_Canada

Data arrived from NERC-ARF via hard drive September/October 2023
PI: Martin Wooster
Sensors:
Fenix1k (priority)
IBIS (priority)
OWL
PhaseOne

Change History (6)

comment:1 Changed 2 weeks ago by asm

Unpacking

Complete. This is a long flight with 29 lines. The ibis failed collection for 5 lines and have been moved to sif/no_data_ibis/ to avoid problems.

comment:2 Changed 11 days ago by mark1

Have edited the GPS Stop Time to be 21:08:00.000 for flight line FENIX231-23-23

comment:3 Changed 9 days ago by asm

Had to edit the GPS Start Time for line fenix 1 as it was reading as 00:00:00 and has renamed the files again (this file should be now the penultimate line).

Last edited 5 days ago by asm (previous) (diff)

comment:4 Changed 4 days ago by asm

Had to edit the GPS Start Time for line owl 1 as it was reading as 00:00:00 and has renamed the files again. The files could not be renamed as the scripts could not handle this and it will be sorted manually later on.

comment:5 Changed 4 days ago by asm

Fenix1k

Ready for delivery check. There were low illumination conditions and hence the data has a lot of underflows but have noted this in the Readme.

comment:6 Changed 4 days ago by asm

Ibis

Ready for delivery check. There were a number of lines that failed to record darkframes so I had to point to other files to process the data. This had as a result that there is no data recorded over water and there are overflows on the entire spectral range for those flightlines but this might still be useful data. I have included a table pointing to the darkframes used for each flightline.

Worth noting that a few lines were flown much lower both for Fenix1k and Ibis and therefore data have been processed with according pixel sizes.

Note: See TracTickets for help on using tickets.