Opened 5 weeks ago

Last modified 4 days ago

#635 new flight processing

GB18/56, flight day 184b/2018, Harwell

Reported by: dac Owned by:
Priority: immediate Milestone:
Component: Processing: general Keywords:
Cc: Other processors:

Description (last modified by mark1)

Data location: /users/rsg/arsf/arsf_data/2018/flight_data/uk/GB18_56-2018_184b_Harwell

Data arrived from NERC-ARF hard drive on 13/07/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.

PI: Hartmut Boesch
BAS Project Code: D056

Issues identified from unpacking checks:

  • Owl capture data missing dark frames


  • Fenix (requested, flown)
  • OWL (requested, flown)
  • Phase One (not requested, flown)

Change History (9)

comment:1 Changed 4 weeks ago by mark1

Navigation Processing

Complete. Used Oxford (oxfr) basestation RINEX downloaded from OS. Used the daily brdc file downloaded from CDDIS for the .18n file.

Did basestation PPP verification and decided to use the values in the RINEX header as they are the precise coordinates and agreed to a few centimetres with the basestation PPP.

IpasTC processing complete with good results.

NOTE: this also covers the trajectory for flight 184a

comment:2 Changed 4 weeks ago by mark1

Fenix processing


line number SCT
1 1.00
2 2.00
3 1.00

comment:3 Changed 4 weeks ago by mark1

Fenix processing
Delivery created - ready for delivery check.

Last edited 3 weeks ago by mark1 (previous) (diff)

comment:4 Changed 4 weeks ago by mark1

  • Description modified (diff)

comment:5 Changed 3 weeks ago by wja

Fenix Delivery Check
Have conducted check Fenix delivery. Here are my comments:

-'Abstract' and 'Purpose' headings contain same text in project informtion XML.
-Text to be edited under 'Data Quality' heading of XML: "A report detailing issues with data quality. This is provided with the data:true". does not work as there is no 2018 regrex file. Manually checked that all data is present and no additional files are present.
-dac adds that the ReadMe should mention that some buildings are saturated, notably the Diamond Light Source synchrotron.

comment:6 Changed 3 weeks ago by mark1

  • Abstract and purpose are the same because the summary and objective are the same in our database.
  • Don't think the "'Data Quality' heading of XML" is a problem - the XML looks fine, it's probably the stylesheet that's missing a space or something.
  • proj_tidy is an old script that shouldn't be used anymore.
  • Read me has been changed to add that the source of overflowed pixels is mainly rooftops.

comment:7 Changed 3 weeks ago by wja

Fenix Delivery

Fenix data delivered via FTP on 01/08/2018. E-mail notification has been sent to PI.

comment:8 Changed 4 days ago by wja

Owl Processing

Initial check:

  • 5 flightlines
  • Dark frames missing.
  • Flightline 5 missing T2 calibration file.

comment:9 Changed 4 days ago by wja

Owl Processing

Generating Level1b Products:

  • Flightlines 1 & 2 are small (length of 927 & 586 lines, respectively).
  • Warning: "Error in proctool_owl_2_6_2 (line 412)" in all logs.
  • Flightline 1 is noisy (in all bands) - will investigate.
  • Flightline 5 missing T2 calibration file. Will try to process using flightline 4's T2.
Note: See TracTickets for help on using tickets.