Opened 11 years ago

Last modified 10 years ago

#520 closed flight processing

RG12/09, flight day 088/2014, Wessex — at Version 13

Reported by: stgo Owned by:
Priority: alpha 5 Milestone: 2014 data processing completion
Component: Archiving Keywords:
Cc: Other processors:

Description (last modified by benj)

Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/RG12_09-2014_088_Wessex

Data arrived from ARSF via network transfer on 31/03/2014

Scientific objective: Unknown

Priority: Alpha 5 - high

PI: France Gerrard

Sensors:

  • Fenix (requested)
  • Leica LIDAR (requested)
  • RCD (requested)

Change History (13)

comment:1 Changed 11 years ago by stgo

Navigation processing started, basestation ppp results:

Lat 51 24 15.45178
Long -1 30 50.16899
Ell. Height 183.434

comment:2 Changed 11 years ago by stgo

Solution using ipas honeywell is poor, will continue trying to improve it but I'm going to process the alternate navigation at the same time to see if that is better.

comment:3 Changed 10 years ago by stgo

Got 10 cm or less position accuracy on the flightline area using ipas honeywell.

comment:4 Changed 10 years ago by stgo

Initial inspection of the flightlines indicates a uniform roll error. Testing the first 4 lines with new values.

comment:5 Changed 10 years ago by benj

Starting Fenix processing

comment:6 Changed 10 years ago by benj

There are fifteen lines in the logsheet but only ten Fenix data files (and line 10 has a raw file but nothing else). Instrument may have failed.

comment:7 Changed 10 years ago by benj

...actually they are all there, just the file numbering is slightly confused (logsheet says the instrument crashed, I assume hence the slightly messed-up numbering and presumably the extra partial raw file).

comment:8 Changed 10 years ago by stgo

Values used for lines 104713 and 110158:

Roll -0.004001414
Pitch 0.00113716
Heading 0.00056484

comment:9 Changed 10 years ago by benj

Fenix data do not contain dark frames. We had hoped to use dark frames from a different flight (similar to what we did for VOCALS in 2009) but looks like this is not a valid approach for Fenix at least. Checked dark frames from day 2014-152a (some of which have the same settings) and the dark frames vary by a factor of 3-4, so cannot say what the appropriate dark values to use for these flights would be. Marking Fenix blocked until we come up with another way to deal with that (if we can).

comment:10 Changed 10 years ago by stgo

Currently checking to see if there is in fact a variable roll error or if I was just over confident with my values for 104713 and 110158.

comment:11 Changed 10 years ago by stgo

Values for 104713 and 110158 are not applicable to other flightlines, 111834 on to 120318 use -0.003918414. will continue getting values.

comment:12 Changed 10 years ago by stgo

Summary of roll values for lines:

104713 -0.004001414
110158 -0.004001414
111834 -0.003918414
113247 -0.003918414
114837 -0.003918414
120318 -0.003918414
121714 -0.003918414
123103 -0.003840414
124534 -0.003918414
130021 -0.003840414
131301 -0.003918414
132548 -0.003840414
133714 -0.004058414
134912 -0.003748414
140505 -0.003848414

Now classifying.

comment:13 Changed 10 years ago by benj

  • Description modified (diff)

Updated arrival date and location in ticket header - hadn't been entered to start with.

Note: See TracTickets for help on using tickets.