Opened 9 days ago

Last modified 7 days ago

#630 new flight processing

GB18/56, flight day 135/2018, Suffolk, Nottinghamshire and Lincolnshire

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

Description

Data location: ~arsf/arsf_data/2018/flight_data/uk/GB18_56-2018_135_Methane_Sites

Data arrived via USB hard drive on a LETTER on 11/June/2018.

Scientific objective: Investigate well-defined local methane emission sources in the UK to apply and evaluate the hyperspectral processing method currently developed at the University of Leicester.

Priority: High for Fenix, medium for Owl

PI: Hartmut Boesch

Sensors:

  • Fenix (requested, flown)
  • OWL (requested, flown)
  • PhaseOne (not requested, flown)

Change History (3)

comment:1 Changed 9 days ago by asm

Unpacking.

Project unpacked. Problems found so far:
-Owl has not been renamed for now as the GPS starting time is not recorded in the files.
-No owl darkframes recorded
-Calibration files also placed in different directories (will need to identify each one by the time)
-No timestamps for the nav files.
-All fenix f98 are empty.
-A few dropped frames incidents for the Fenix:
There has been 2 incidents on different lines with a total of 34 dropped frames recorded on file FENIX135-18-14.log
There has been 2 incidents on different lines with a total of 39 dropped frames recorded on file FENIX135-18-7.log
There has been 2 incidents on different lines with a total of 32 dropped frames recorded on file FENIX135-18-1.log
There has been 2 incidents on different lines with a total of 33 dropped frames recorded on file FENIX135-18-5.log

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

comment:2 Changed 8 days ago by asm

Unpacking.

-Renamed Owl files as the time in the header (not GPS but internal) will help processing. Will need to add GPS Starting time to process
-The owl lines do not have darkframes so will need to use the calibration files. Match each calibration with each file and stitch them. Time consuming, specially combined with no navigation files to use and the GPS timing issue.
No KML created yet or logsheet but project but otherwise the unpacking is done.

comment:3 Changed 7 days ago by asm

Navigation Processing

Started in order to assess if the fps problem with the Fenix still persists. Needed to use teqc:
teqc -st 180515094209 -e 180515150330 +nav /tmp/teqc_135_2018/135_2018.nav > /tmp/teqc_135_2018/135_2018.18o

Done basestation verification:
Lat: 52 04 27.12178
Lon: -0 37 24.79006
EllHeight: 151.206 m

Done navigation as well. Good results, accuracy is always better than 0.2m in lat and lon sepparation and with ambiguity fix 2. All parameters looking good, best results we have in a long time. Copying files across and navigation will be finished.

Note: See TracTickets for help on using tickets.