RG13/08, flight day 260a/2013, Ash_Die_1

[knpa]

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: ?

PI: David Coomes

Sensors:

Camera (23/10/2013)
Eagle (23/10/2013)
Hawk (23/10/2013)
LiDAR (23/10/2013)

[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.

[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.

[emca]

PPP results for the basestation SNEO:

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

[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/

[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

[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.

[emca]

Replying to emca:

looks like a corrupt file in ipas_honeywell/raw was causing the problem.

Corrupt files... raw files 02, 05, 06, 07 and 08.
Have replaced these with the data from 260b.

[emca]

Got better nav results using the IPAS20 data. Will process all data using the new nav results.

[emca]

Flightline	Eagle SCT	Hawk SCT
1	-0.02	-0.05
2	-0.02	-0.06
3	-0.02	-0.06
4	-0.02	-0.06
5	0.00	-0.05

[emca]

Hyperspectral data ready for delivery check. Waiting to hear from Gary re: vectors.

[tipo]

check_apl_cmd fails, typo in example commands?

[emca]

Recreated the hyperspectral readme - sample commands updated. Check_apl_cmd should work now.

[emca]

Camera data ready for delivery check

[tipo]

check_apl_cmd still fails:

/users/rsg/arsf/usr/bin/check_apl_cmd: line 294: 10780 Segmentation fault (core dumped) apltran -inproj latlong WGS84 -igm ../../tmp_cmd_check/e260a013b.igm -output ../../tmp_cmd_check/e260a013b_osng.igm -outproj osng /users/rsg/arsf/dems/ostn02/OSTN02_NTv2.gsb

The .igm file is created, but has no .hdr Does the script work for you? if so, it might be yet another Fedora 19 problem.

[tipo]

RCD delivery checked, no problems found.

[emca]

check_apl_cmd works fine for me - perhaps try on mark1's machine (he is away today)

[tipo]

Yep, running it from Marks's machine seems to work. I'll add the problem to the Fedora 19 issues page.
No other issues found with hyperspectral.

[emca]

Asked Ops to copy the raw lidar data (RawLaser) from the SSD's to Thelma. They did this and the lidar lines that we causing ALSPP to crash are now processing fine.

The data got lost/corrupt when copying from aircraft to thelma first time around.

Two of the lines suffer from range gate issues (line 2 and line 6)

[emca]

No obvious roll in the lidar data, but limited overlap so it is difficult to tell.

[emca]

Hyperspectral and RCD on disk 187 ready to deliver. Just waiting to hear from gary re: vectors.

[emca]

Finished processing LiDAR, ready for delivery check.

[stgo]

Beginning LiDAR D/C.

[stgo]

LiDAR D/C complete, no issues found.

[emca]

Data sent to D. Coomes 23/10/2013

[emca]

Email from Gary 30/10/2013 - Awaiting vector agreement form between OS and PI before vectors can be sent to us.