Opened 15 years ago

Last modified 8 years ago

#265 closed flight processing

GB08/08, flight day 252b/2009, Wytham woods — at Version 7

Reported by: mark1 Owned by:
Priority: alpha 4 high Milestone: 2009 Data processing completion
Component: Archiving Keywords:
Cc: Other processors:

Description (last modified by mark1)

Data location: ~arsf/arsf_data/2009/flight_data/uk/GB08_08-2009_252b_Wytham_woods

Data arrived from ARSF via SATA disk L on 7th October 2009.

Scientific objective: see ~/arsf/arsf_data/in_progress/2008/ARSF_Applications/GB_and_NL/GB08-08 Science Case.pdf

Priority: alpha-4-High

PI: Richard Harding

Sensors:

  • Eagle
  • Hawk
  • Leica LIDAR
  • RCD images (12/02/2010)

Change History (7)

comment:1 Changed 15 years ago by mark1

Still awaiting flight logsheet for this project.

Also, DEM creation gave errors when reading in tiles to grass but still output a DEM. Check it is OK when processing.

comment:2 Changed 15 years ago by mark1

Have moved original eagle files into boresight_252a and moved the eagle files from boresight_252a into this project.

comment:3 Changed 15 years ago by mark1

  • Milestone set to 2009 Data processing completion

comment:4 Changed 15 years ago by mark1

logsheet arrived and unpacked

comment:5 Changed 15 years ago by mggr

Re: #281 (Hawk frame rates are double what they should be), the following lines are affected and the .hdr file will need to be edited to halve the fps number:

arsf_internal/boresight_2009-252a_little_riss/hawk/SWIR252a_09-10.hdr: predicted length half recorded length, frame rate doubling problem?
arsf_internal/boresight_2009-252a_little_riss/hawk/SWIR252a_09-11.hdr: predicted length half recorded length, frame rate doubling problem?
arsf_internal/boresight_2009-252a_little_riss/hawk/SWIR252a_09-12.hdr: predicted length half recorded length, frame rate doubling problem?
arsf_internal/boresight_2009-252a_little_riss/hawk/SWIR252a_09-13.hdr: predicted length half recorded length, frame rate doubling problem?
arsf_internal/boresight_2009-252a_little_riss/hawk/SWIR252a_09-2.hdr: predicted length half recorded length, frame rate doubling problem?
arsf_internal/boresight_2009-252a_little_riss/hawk/SWIR252a_09-3.hdr: predicted length half recorded length, frame rate doubling problem?
arsf_internal/boresight_2009-252a_little_riss/hawk/SWIR252a_09-4.hdr: predicted length half recorded length, frame rate doubling problem?
arsf_internal/boresight_2009-252a_little_riss/hawk/SWIR252a_09-6.hdr: predicted length half recorded length, frame rate doubling problem?
arsf_internal/boresight_2009-252a_little_riss/hawk/SWIR252a_09-7.hdr: predicted length half recorded length, frame rate doubling problem?
arsf_internal/boresight_2009-252a_little_riss/hawk/SWIR252a_09-8.hdr: predicted length half recorded length, frame rate doubling problem?
arsf_internal/boresight_2009-252a_little_riss/hawk/SWIR252a_09-9.hdr: predicted length half recorded length, frame rate doubling problem?
arsf_internal/boresight_2009-252a_little_riss/hawk/SWIRdataCube.hdr: predicted length half recorded length, frame rate doubling problem?

comment:6 Changed 15 years ago by mark1

Photograph delivery created and checked. No log file to tag images with.

comment:7 Changed 15 years ago by mark1

  • Description modified (diff)

Photography data dispatched to PI on 12/02/2010

Note: See TracTickets for help on using tickets.