Opened 10 days ago

Last modified 23 hours ago

#628 new flight processing

GB18_00, flight day 129/2018, Boresight

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

Description

Data location: /users/rsg/arsf/arsf_data/2018/flight_data/nerc-arf_internal/GB18_00-2018_129_Boresite_Calibration_Wooster

Data arrived from NERC-ARF via external hard disk on 15/05/18.

Scientific objective: Boresight

Priority: Urgent

PI: NERC-ARF

Sensors:

  • Fenix (requested)
  • OWL (requested)

Change History (10)

comment:1 Changed 10 days ago by mark1

Fenix and Owl are missing Specim timestamps. Have informed Gary and James.

Also, Owl line 1 is missing the nav file completely (but logsheet says lines 4 onwards are the ones to use)

comment:2 Changed 8 days ago by mark1

Basestation PPP processing:

Latitude: 52 04 27.10312
Longitude: -0 37 24.83725
Ell Height: 149.835m

comment:3 Changed 4 days ago by mark1

Ended up using the St Neots basestation rather than the ARF one as it was closer to the survey site.

comment:4 Changed 4 days ago by wja

Fenix Processing

Fenix line 10 has same starting time and ending time. Need to correct for or not process it.

comment:5 Changed 4 days ago by wja

Fenix processing

Also the same problem for fenix lines 06 and 11. Moving them to a dir called hyperspectral/problematic_lines for now (to show Will how to process - asm writing here).

comment:6 follow-up: Changed 4 days ago by wja

Fenix

For processing the boresight until the new cal is done, we have replaced the wavelenghts with the 2016 cal. Will use also this one for the calibration (asm)

comment:7 in reply to: ↑ 6 Changed 3 days ago by asm

Replying to wja:

Fenix

For processing the boresight until the new cal is done, we have replaced the wavelenghts with the 2016 cal. Will use also this one for the calibration (asm)

Correction, used the 2015 calibration (we did not fly on 2016).

comment:8 Changed 3 days ago by asm

Also run the unpacked checks:

-Fenix line 13: 2 incident with a total of 25 dropped frames
-Fenix line 14: 2 incident with a total of 59 dropped frames
-Fenix line 18: 2 incident with a total of 32 dropped frames
-fps differs from fps_qpf by 0.631 in file: fenix 14
-Owl lines 2 and 6 have 1 dropped frame incident
-No use owl nav as well
-No GPS starting point and ending point for Owl line 1

Last edited 23 hours ago by asm (previous) (diff)

comment:9 Changed 23 hours ago by asm

Fenix Processing

Added a calculated ending time for 6, 10 and 11 and put them with the others for processing (original headers are safe in the usual place). Recreated the APL config file, all looking good.

comment:10 Changed 23 hours ago by asm

Owl Processing

Added GPS Start Time to owl hdr 1 (it was there but it was not GPS time but only UTC start time). Recreated the APL config that now contais the owl sensor as well.

Note: See TracTickets for help on using tickets.