Opened 10 years ago

Last modified 8 years ago

#99 new flight processing

IPY07/06, flight day 217b/2007, Green Box

Reported by: mggr Owned by: mggr
Priority: alpha 4 high Milestone: 2007 data processing completion
Component: Archiving Keywords: IPY
Cc: Other processors:

Description (last modified by benj)

Data location: ~arsf/arsf_data/in_progress/2007/flight_data/ipy/IPY07_06-2007_217b_Green_Box

Data arrived from ARSF via SATA disk transfer in August, with post-processed GPS arriving in December following Kidlington visit.

Scientific details: (details of IPY applications not currently available at PML)

PI: Adrian Luckman

No Bill post-processed GPS for this one - ask Mike before processing this (we probably should check with Bill that he's not got anything, or why this station wasn't post-processed).

Sensors:

  • ATM (Delivered 20/05/08)
  • CASI (Delivered 13/05/08)
  • Eagle (Delivered 13/05/08)
  • Hawk (Delivered 13/05/08)

Quicklook

TBD.

Attachments (1)

Green_Box_line9.png (985.3 KB) - added by benj 10 years ago.
Mosaic of lines from Green Box

Download all attachments as: .zip

Change History (14)

comment:1 Changed 10 years ago by benj

GPS data seems OK, proceeding with processing

comment:2 Changed 10 years ago by mark1

Eagle data file numbers appear to be offset by 1. eg for line 1 use file 2.

comment:3 Changed 10 years ago by mark1

Eagle data for line 4 causes problems processing. See ticket 116.

comment:4 Changed 10 years ago by mark1

No suitable Eagle data for flight line 9 - (2 possible data files...10 and 11). Data file 10 has very little data and wont process, and data file 11 is the turning flight path of the plane.

Also Eagle data file 17 has not been processed since it doesn't appear to contain any usable data.

Changed 10 years ago by benj

Mosaic of lines from Green Box

comment:5 Changed 10 years ago by benj

Line 9 just seems to be broken for both Eagle and Hawk. Both have a very small data file 10 and a larger 11 that seems to be on a curve. If you look at a mosaic of the images (see below), you can see that the coastline visible on the curved line lines up with that visible on the ATM line, suggesting that it's not just a nav problem (the line is actually correctly located, it just isn't where line 9 should have been). It's likely that the actual line 9 data for Eagle and Hawk should have been in the destroyed/corrupt/incomplete/otherwise useless file 10s.

Mosaic of various ATM lines with Eagle line from data file 11 (curved line):
Mosaic of lines from Green Box

comment:6 Changed 10 years ago by benj

  • Owner changed from mggr to anee

Delivery directory created and filled at ~benj/scratch/IPY07_06-2007_217b_Green_Box/delivery/20080502/IPY07-06

comment:7 Changed 10 years ago by anee

  • Owner changed from anee to benj

Minor changes to read-me - ready to deliver. Not rsynced as there isn't sufficient disk space available.

comment:8 Changed 10 years ago by anee

Delivery now rsynced to: /users/rsg/arsf/arsf_data/in_progress/2007/flight_data/ipy/IPY07_06-2007_217b_Green_Box

comment:9 Changed 10 years ago by benj

  • Description modified (diff)
  • Owner changed from benj to mark1

ATM delivery directory created and filled at ~benj/scratch/IPY07_06-2007_217b_Green_Box/delivery/20080515/IPY07-06

comment:10 Changed 10 years ago by mark1

  • Owner changed from mark1 to benj

Delivery has been checked and looks ok. Example commands tested.

Rsynced to /users/rsg/arsf/arsf_data/in_progress/2007/flight_data/ipy/IPY07_06-2007_217b_Green_Box

comment:11 Changed 9 years ago by benj

  • Owner changed from benj to mggr

ATM delivered May 20th 2008. Ready for archiving.

comment:12 Changed 9 years ago by benj

  • Description modified (diff)

comment:13 Changed 8 years ago by mggr

  • Component changed from Processing: general to Archiving

Data held for overflow checking.

Note: See TracTickets for help on using tickets.