Opened 11 years ago

Last modified 9 years ago

#501 assigned flight processing

RG13/08, flight day 260a/2013, Ash_Die_1 — at Version 7

Reported by: knpa Owned by:
Priority: alpha 4 medium Milestone: 2013 data processing completion
Component: Processing: general Keywords:
Cc: Other processors:

Description (last modified by emca)

Data location: /users/rsg/arsf/arsf_data/2013/flight_data/uk/RG13_08-2013_260a_Ash_Die_1

Data arrived from ARSF via network transfer on 18/09/2013

RG13/08 Scientific objective: unknown

RG13/08 Priority: a4m

PI: David Coomes

Sensors:

Camera
Eagle
Hawk
LiDAR

Change History (7)

comment:1 Changed 11 years ago by emca

Problems with the IPAS Honeywell, large gaps in the data collected.

Trying to use the IPAS20 but not getting good results. Waiting for confirmation of lever arms values before going any further.

Processed the raw camera image -> tiff.

comment:2 Changed 11 years ago by emca

Processed the navigation with slightly better results. Still waiting for confirmation from Ops in relation to the User Frame values for the IPAS20 (litton).

Using the dodgy nav to process the hyperspectral data in order to calculate the sct values. Will need to be reprocessing later when/if we get better nav results.

Will hold off on the lidar processing for now.

comment:3 Changed 11 years ago by emca

PPP results for the basestation SNEO:

Lat: 52 11 07.32797
Long: -0 06 44.97284
Elev: 120.092

comment:4 Changed 11 years ago by emca

The Eagle was processed with binning 4 so created a new qc failures file
eagle_110001_bin4_visualbadpixels.txt

Added this file to /users/rsg/arsf/calibration/2013/eagle/

comment:5 Changed 11 years ago by emca

Processed the LiDAR lines. Couple of problems:
Line 1 has a large blank down the middle, looks like its a range gate issue
Line 4 has only processed partly, about one third, not sure why as ASLPP does not show any errors
Line 5 does not process at all, ALSPP crashes when I load it in

comment:6 Changed 11 years ago by emca

Processed the IPAS honeywell nav data for 260b - which was fine. After checking further looks like a corrupt file in ipas_honeywell/raw was causing the problem. It is the same on thelma so must have been a problem when downloading from the aircraft. Replaced corrupt nav file with the one from day 260 b.

comment:7 Changed 11 years ago by emca

  • Description modified (diff)
Note: See TracTickets for help on using tickets.