Opened 7 years ago

Last modified 7 years ago

#316 new flight processing

Boresight, flight day 060/2010, Little rissington

Reported by: emca Owned by:
Priority: immediate Milestone: 2010 data processing completion
Component: Processing: general Keywords:
Cc: Other processors:

Description

Data location: ~arsf/arsf_data/2010/flight_data/arsf_internal/GB10_00_2010_060_boresight

Data arrived from ARSF via network transfer on 1st March 2010

Scientific objective: boresight

Priority: boresight

PI: internal

Change History (7)

comment:1 Changed 7 years ago by emca

Not enough disk space available for raw full waveform data to be saved to ~arsf/arsf_data/2010...
RawWFD folder has been rsync'ed to ~airborne/workspace/GB10_00-2010_060_boresight/leica/ but will need to be saved in arsf_data once space is available.

comment:2 Changed 7 years ago by benj

  • Milestone set to 2010 data processing completion

comment:3 Changed 7 years ago by emca

Raw Full Waveform data has been saved to the repository

comment:4 Changed 7 years ago by emca

This data sets suffer from the variable roll issue - see ticket #257

comment:5 Changed 7 years ago by benj

Timing offsets as follows (from when this was processed back in March). Note Hawk appears not to have had all its offsets established correctly.

Line Eagle Offset Hawk Offset
1 0.03 ?
2 0.07 ?
3 0.01 0.03
4 0.06 ?
5 0.00 ?
6 0.05 0.5?
7 0.04 0.01
8 0.02 0.03
9 0.02 0.03
10 0.04 -0.02
11 0.04 ?
12 0.02 ?
13 0.03 ?
14 0.03 ?

comment:6 Changed 7 years ago by mggr

A few extra from Ben's email to support.aisa@… on 24/March:

Line    Eagle_offset    Hawk_offset
1    0.03        -0.01
2    0.07        0.00
3    0.01        0.03
4    0.06        -0.01
5    0.00       
6    0.05        0.5
7    0.04        0.01
8    0.02        0.03
9    0.02        0.03
10    0.04       
11    0.04        -0.02
12    0.02        0.02
13    0.03        0.03
14    0.03        0.00 

comment:7 Changed 7 years ago by emca

Due to the unavailability of adequate base station data for this flight we were unable to complete the range correction for the lidar calibration.
The resulting calibration therefore uses the the range correction values from calibration flight day 096/2010 - see ticket #348

Note: See TracTickets for help on using tickets.