Opened 9 years ago

Last modified 9 years ago

#540 new flight processing

HS2-AF14H789, flight day 245/2014, Blom Lichfield

Reported by: knpa Owned by: knpa
Priority: alpha 5 Milestone: 2014 data processing completion
Component: Processing: general Keywords:
Cc: Other processors:


Data location: /users/rsg/arsf/arsf_data/2014/flight_data/blom/HS2-AF14H789-litchfield

Data arrived from Blom via disk Friday 5th September

Scientific objective:

Priority: Immediate

PI: Blom [Travis Mayne, Hamish Grierson]

Any other notes..


Fenix (Requested)

Change History (10)

comment:1 Changed 9 years ago by knpa

SCT values appear to be around -14.1

Last edited 9 years ago by knpa (previous) (diff)

comment:2 Changed 9 years ago by knpa


No wobbles and large time range so not as confident about values as normal. *starred ones are best guesses. The first one was particularly hard, there's no sharp wobbles and no other lines around it to gauge against. We also don't have any vectors for this project.

-01: -13.9* not sure about this one
-02: -14.40*
-03: -13.72
-04: -12.71
-05: -13.54
-06: -14.23*
-07: -14.12
-08: -13.14
-09: -12.76
-10: -14.84
-11: -14.02
-12: -13.64*
-13: dark frames/fps problem
-14: -14.00
-15: -14.60
-16: -13.68
-17: -12.69
-18: -13.38
-19: -13.39
-20: -13.00

Last edited 9 years ago by knpa (previous) (diff)

comment:3 Changed 9 years ago by knpa

Problem processing line 13 - aplcal claims over 50% of lines are dark frames.

comment:4 Changed 9 years ago by knpa


Command line used to run: /users/rsg/arsf/usr/bin/aplcal -input /data/visuyan2/scratch/arsf/2014/flight_data/blom/HS2-AF14H789-litchfield/hyperspectral/fenix/FENIX245-14-13.raw -calfile /users/rsg/arsf/arsf_data/2014/flight_data/blom/HS2-AF14H787-Boresight/Calibration_Petri/Radiometric_calibration_8x2_1x1_LC -output /tmp/7540894.1.arsf.q/arsf-j9eQO9/flightlines/level1b/f245131b_n_sct-13.00.bil -sensor f
Sensor has no FODIS region defined.

More than half the number of scan lines are dark frames - seems a bit odd.

########## ERROR #########
A BinaryReader Exception has occurred.
ReadCell has failed...row/col out of bounds: row: 14674 col: 0

########## ERROR #########

comment:5 Changed 9 years ago by knpa

The fps_qpf on this file (LichfieldRun16_0102-1216.hdr) was a crazy figure.

Also, the dark frames value was equally crazy.

This line is only 277 scans, plus it looks like it was reflown (LichfieldRun16_0102-1216-3.raw), so am going to discard this line.

comment:6 Changed 9 years ago by tec

Starting blom delivery

comment:7 Changed 9 years ago by tec

Ran delivery script, need to generate screenshots (mosiac for both flights or individual ones), need to verify XML as it will be missing things as there is no database entry.

gmd:abstract EMPTY example Improve lake remote sensing algorithms
gmd:purpose EMPTY example Improve lake remote sensing algorithms
gmd:individualName EMPTY example Peter Hunter
gmd:description EMPTY example Loch Lomond

comment:8 Changed 9 years ago by lah

Fenix Delivery Check - Problems to address:

  • DEM: should Manchester be in name or usual naming convention?
  • No data quality report in doc folder
  • Style sheets missing from line info folder
  • No logsheet folder or logsheet, but is specified in ReadMe
  • No mosaic with vectors screenshot
  • I have changed ascii file to clrf terminated
  • sensor_FOV_vectors wrongly named. I have renamed them so check_apl_cmd will run without errors.
  • This is my first Fenix DC, so someone else should do a second check, particularly for bad pixels in level 1 files.
  • proj_tidy throws up large difference between fps_set and fps_qpf, but I'm guessing that's no surprise.

comment:9 Changed 9 years ago by tec

Changed SCT Values

Line SCT
14 13.95
15 14.57
17 15.57
18 13.35
2 14.28
3 13.70
4 12.65
8 13.15
11 13.95

comment:10 Changed 9 years ago by lah

Delivery check on hold as user wants smaller files...

Note: See TracTickets for help on using tickets.