Opened 10 months ago

Last modified 8 months ago

#648 new flight processing

CA18/00, flight day 223a/2018, Red Lake, Ontario, Canada

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

Description

Data location: /users/rsg/arsf/arsf_data/2018/flight_data/canada/CA18_207-2018_224a_Ontario

Data arrived from NERC-ARF via hard driver on 12/09/2018

Scientific objective: Boresight Flight for Canada

PI: NERC-ARF

  • Missing navigation synchronisation data
  • Framerate not recorded correctly
  • Missing log files for Fenix

Sensors:

  • Fenix (requested, flown)
  • Owl (requested, flown)

Change History (9)

comment:1 Changed 10 months ago by asm

Extra checks

-No use of nav files
-Great differences of fps and fps_qpf for Fenix
-Only 3 owl lines and the 3rd does not have T2.

comment:2 Changed 10 months ago by asm

Owl processing

Started. Symlinked T2 files from owl line 2 for owl line 2. Processed owl to level1b.

comment:3 Changed 10 months ago by wja

Nav Processing
Basestation PPP identified as:

Latitude51°04'01.40120"
Longitude-93°48'14.26919"
Ellipsoid Height346.797

Looks like the same data as 2018 224a.

comment:4 Changed 10 months ago by wja

Nav Processing
Sol file produced from GNSS/IMU with IPAS TC.
Data quality looks good. Position separation had a few narrow peaks that exceed -+0.05m.

comment:5 Changed 10 months ago by asm

Owl processing

It looks the sol file does not cover times for this data, it covers the data for 223b rather than "a". There was not ipas20 for this sortie, will ask operations.

comment:6 Changed 10 months ago by asm

General processing

Also, the flightlines in sortie "b" were flown before flightlines in sortie "a"

comment:7 Changed 8 months ago by wja

Last edited 8 months ago by wja (previous) (diff)

comment:8 Changed 8 months ago by wja

Last edited 8 months ago by wja (previous) (diff)

comment:9 Changed 8 months ago by wja

Owl/Fenix Processing
Ignore my previous comments (which I have deleted). I mistook this ticket for 233a.
Apologies for any confusion.

Note: See TracTickets for help on using tickets.