Opened 3 years ago

Last modified 3 years ago

#526 assigned flight processing

GB14/00, flight day 141/2014, Little Rissington

Reported by: knpa Owned by: stgo
Priority: immediate Milestone: 2014 data processing completion
Component: Processing: LIDAR Keywords: Boresight
Cc: Other processors:

Description (last modified by stgo)

Data location: /users/rsg/arsf/arsf_data/2014/flight_data/arsf_internal/GB14_00-2014_182_Little_Riss

Data arrived from ARSF via SATA disk LETTER OR network transfer on 01/07/2014

GB14/00 Scientific objective: Boresight

GB14/00 Priority: urgent

PI: ARSF

Notes: Lidar Boresight processed with urgency.

Sensors:

Camera (Not requested by PI)
LiDAR (Requested)

Change History (26)

comment:1 Changed 3 years ago by knpa

Using ppp result from day 144 as can't do ppp on the basestation today (no clk/sp3 files available yet).

lat 51 44 21.03248
long -2 18 02.77824
height 76.373

comment:2 Changed 3 years ago by knpa

Done nav processing.

comment:3 Changed 3 years ago by knpa

Scan Angle Correct value (-10340) does not match current values which have an average of ~-9200.

Updating Scan Angle Correct to -9200, need to notify ops about this (according to the wiki).

comment:4 Changed 3 years ago by knpa

Chose the following 6 lines for attune:

High
2 x orthog: 0628 (N) + 0645 (E)
1 x opposing: 0633 (S)
1 x offset: 0638 (E)*

Mid
2 x orthog 0657 (N) + 0705 (E)

  • it has W in it's name but says is going East. Though this might be 30% overlapped with the opposing westbound line rather than the eastbound 0645. In this case I don't know what to do if there aren't any offset lines going in the same direction.

comment:5 Changed 3 years ago by stgo

Having some issues processing using attune. It can't find the autoboresight program and won't explain how to point to it, will post a fix on the wiki if I find one.

comment:6 Changed 3 years ago by stgo

Fix is to run attune from the program folder rather than start menu or a shortcut.

comment:7 Changed 3 years ago by stgo

IBRC is being recognised as invalid.

comment:8 Changed 3 years ago by stgo

I have overcome the IBRC problem by processing on linux. I have no explaination why it will not work on the windows machine.

comment:9 Changed 3 years ago by stgo

Attune crashes on attempt to reduce tie points, reprocessing to check if lack of IBRC is the reason.

comment:10 Changed 3 years ago by stgo

I am replacing 0633 with 0650 as the opposed line. Lasground is rejecting 0633, it would be worth investigating why.

comment:11 Changed 3 years ago by stgo

Fixed Attune, presumably the problem is linked to changing the line and reprocessing with IBRC. I will make a note in the wiki.

comment:12 Changed 3 years ago by stgo

Found pitch roll and heading values that work consistently:

pitch: -0.001157190
heading: 0.000185120
roll low: -0.003859930
roll medium: -0.003959930
roll high: -0.004297930

Last edited 3 years ago by stgo (previous) (diff)

comment:13 Changed 3 years ago by stgo

Currently processing range offsets, lascontrol ouputs based on 36 control points:
abs: 2.06434
rms: 2.09265
stddev: 1.02766

skew is 3.32942

Actual elevation error is -1.8309713861

comment:14 Changed 3 years ago by stgo

Range offsets using only low altitude lines:

Range offset A1: -1.83097
Range Offset A2: -1.822
Range Offset A3: -1.793
Range Offset A4: -1.838

Using all lines:

Range offset A1: -1.83097
Range Offset A2: -1.823
Range Offset A3: -1.793
Range Offset A4: -1.840

Range Offset B1: -1.831
Range Offset B2: -1.828
Range Offset B3: -1.834
Range Offset B4: -1.811

comment:15 Changed 3 years ago by stgo

Above values returned errors of 30 cm. Have reprocessed removing three more GCPs to get the following:

Based on 33 of 33 control points.
abs: 2.12336
rms: 2.12359
stddev: 0.0316578
Skew is 0.861423.

Actual range offset (after calculating myself): -2.1233593939

Range offsets:

Range offset A1: -2.123359
Range Offset A2: -2.115
Range Offset A3: -2.085
Range Offset A4: -2.132

Range Offset B1: -2.123
Range Offset B2: -2.120
Range Offset B3: -2.127
Range Offset B4: -2.103

Results from lascontrol on low lines using these values:
abs: 0.0248971
rms: 0.0290698
stddev: 0.0290275
skew is 0.511644.

Actual abs is -0.00529.

comment:16 Changed 3 years ago by stgo

High lines lascontrol output:

abs:0.0267191
rms:0.0332766
stddev:0.0316438
skew is -0.0724064.

actual abs is 0.0116767839

Last edited 3 years ago by stgo (previous) (diff)

comment:17 Changed 3 years ago by stgo

Now calibrating FW

comment:18 Changed 3 years ago by stgo

Above TPR correction: 9700
Below TPR: 6400

comment:19 Changed 3 years ago by stgo

Averaged roll value: -0.004039263

comment:20 Changed 3 years ago by stgo

Following discovery the scan angle correct value was wrong I am reprocessing, new initial range offsets:

Range offset A1: 0
Range Offset A2: 0.008
Range Offset A3: 0.038
Range Offset A4: -0.009

Range Offset B1: 0.000
Range Offset B2: 0.003
Range Offset B3: -0.003
Range Offset B4: 0.020

Movement of the scan angle correct appears to have shifted all roll values -0.00183(ish). This saved time finding the new values. I will run range correction after I have checked the pitch/roll values found.

comment:21 Changed 3 years ago by stgo

Range calibration results:
sampled TIN at 42 of 42 control points.
abs: 2.11563
rms: 2.11579
stddev: 0.0267907

skew is 0.815626.

actual abs value is -2.1156283333

comment:22 Changed 3 years ago by stgo

Range offsets from rangecardcal:

Range offset A1: -2.1156283333
Range Offset A2: -2.107
Range Offset A3: -2.078
Range Offset A4: -2.125

Range Offset B1: -2.116
Range Offset B2: -2.112
Range Offset B3: -2.119
Range Offset B4: -2.095

comment:23 Changed 3 years ago by stgo

Lascontrol output on low lines:
abs: 0.0279141
rms: 0.0344954
stddev: 0.0312297

skew is 0.0239848.

actual abs is -0.0154227988

comment:24 Changed 3 years ago by stgo

Range results for high lines:
abs: 0.0592026
rms: 0.0927723
stddev: 0.0870097

skew is 1.19856.

actual abs is 0.0348751529

Final pitch roll and heading values are:
Heading: 0.000185120
Pitch: -0.000857190
Roll low: -0.005839263
Roll medium: -0.005839263
Roll high: -0.006089263

Averaged roll is −0.005922596

Last edited 3 years ago by stgo (previous) (diff)

comment:25 Changed 3 years ago by stgo

  • Component changed from Processing: photos to Processing: LIDAR
  • Description modified (diff)
  • Keywords Boresight added
  • Owner set to stgo
  • Status changed from new to assigned

comment:26 Changed 3 years ago by stgo

Last edited 3 years ago by stgo (previous) (diff)
Note: See TracTickets for help on using tickets.