Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#54 closed flight processing (fixed)

GB2007/05, flight day 116a/2007, Windermere

Reported by: mggr Owned by: mggr
Priority: alpha 5 Milestone: 2007 data processing completion
Component: Archiving Keywords: GB2007/05
Cc: Other processors:

Description (last modified by anee)

Data location: ~arsf/arsf_data/in_progress/2007/flight_data/uk/GB2007_05-2007_116a_Windermere

Data arrived from ARSF via initial SATA disk transfer in June.

Scientific details: Data to inform models of potentially toxic cyanobacterial blooms in lakes. See ~arsf/arsf_data/in_progress/2007/ARSF_Applications-GB_2007/GB07-05_*pdf

Related tickets: (this is one of several lakes overflown)

Sensors

  • ATM (Delivered 23/April/2008)
  • Eagle (Delivered 19/March/2008)
  • Hawk (Delivered 23/April/2008)

Change History (38)

comment:1 Changed 11 years ago by mggr

  • Summary changed from GB2007/05, flight day 103c/2007, Windermere to GB2007/05, flight day 116a/2007, Windermere

Corrected summary text.

comment:2 Changed 11 years ago by mggr

Note that I've guessed which of 116a & 116b is Windermere and which is Esthwaite - when we process, we need to check to make sure and rename if required.

comment:3 Changed 11 years ago by mggr

  • Owner changed from mggr to anee

comment:4 Changed 11 years ago by anee

There appear to be no satellites tracked between GPS time 381300 – 385800. This is in the important part of the flight path at the observation site.

comment:6 Changed 11 years ago by anee

1st eagle nav file 0 bytes. No other eagle nav files present. Using hawk nav files in place of eagle.

comment:7 Changed 11 years ago by anee

not all eagle raw and hdr files present

comment:8 Changed 11 years ago by anee

Windermere and Esthwaite data are taken over one site.

comment:9 Changed 11 years ago by anee

All hawk and atm data processed, some timing offsets probably required.

comment:10 Changed 11 years ago by anee

GTPOFF for atm line 3, ~1.

comment:11 Changed 11 years ago by anee

All atm and hawk data processed, no eagle lines processed because much of the required data is not present in the eagle directory.

comment:12 Changed 11 years ago by mggr

Can't get access to daphne (ARSF fileserver) over several days, so sending an email asking.

Sidenote for the record: the gap in the applanix was actually due to the plane landing and didn't affect the relevant parts of the flightline for processing.

comment:13 Changed 11 years ago by mggr

ARSF confirm that flightline 1 of Eagle is destroyed (possibly happened during QC?) and that the hdr files they have are also 0 bytes - we'll have to try and figure out how to work around this. I believe Bill has outlined a method in the azspec processing guide, but we may need an updated azspec program to do it - need to test.

For now, suspend this job. We'll reevaluate in a few weeks once we've gone through the 'easy' jobs and have the boresight sorted. At that point, we may just deliver the data we have and come back to the Eagle later.

comment:14 Changed 11 years ago by mggr

Vectors available at ~arsf/vectors/from_akw/windermere

comment:15 Changed 11 years ago by mggr

Could you reprocess the ATM with the updated boresight and ensure the DEM is used? Peter Hunter asked if we could deliver this soon.

comment:16 Changed 11 years ago by anee

All ATM lines processed.

comment:17 Changed 11 years ago by mggr

Holding while we complete the 2007 ATM radiometric calibration..

comment:18 Changed 11 years ago by mggr

Please confirm status of Eagle reconstruction to Andrew Tyler in two weeks time.

comment:19 Changed 11 years ago by anee

Successfully processed lines 2 and 3 using hdr files produced by taking Eagle files for the equivalent lines on flight 116b and editing the GPS time fields to match the Hawk hdr fields for day 116a. The lines and autodarkstartline fields were also corrected.

comment:20 Changed 11 years ago by anee

Eagle line 3 GPTOFF ~ -0.2

comment:21 Changed 11 years ago by anee

Processed Eagle flight data (lines 2 and 3 only) located in: /users/rsg/anee/scratch_space/GB2007_05-2007_116a_Windermere

Delivery directory created and filled

comment:22 Changed 11 years ago by anee

  • Owner changed from anee to benj

comment:23 Changed 11 years ago by anee

directory renamed to /users/rsg/anee/scratch_space/GB2007_05-2007_116a_Windermere_Esthwaite needs to be updated in arsf directory too

comment:24 Changed 11 years ago by benj

  • Owner changed from benj to anee

Not entirely happy with Eagle imagery (roads are too blue, rest of image seems too dark and too green), but checking as best I can against ATM, Eagle from other flights and processing through Caligeo doesn't show up anything wrong with it so I can't say it's actually wrong.

Rsynced to ~arsf/arsf_data/in_progress/2007/flight_data/uk/GB2007_05-2007_116a_Windermere_Esthwaite

comment:25 Changed 11 years ago by anee

Eagle data sent to Andrew Tyler on disk 5.

comment:26 Changed 11 years ago by anee

  • Owner changed from anee to benj

Processed ATM flight data located in:
/users/rsg/anee/scratch_space/GB2007_05-2007_116a_Windermere_Esthwaite

Delivery directory created (20080403)

comment:27 Changed 11 years ago by benj

  • Owner changed from benj to anee

Checked and rsynced to ~arsf/arsf_data/in_progress/2007/flight_data/uk/GB2007_05-2007_116a_Windermere_Esthwaite

comment:28 Changed 11 years ago by anee

  • Owner changed from anee to mark1

Processed Hawk data located in: /users/rsg/anee/scratch_space/GB2007_05-2007_116a_Windermere_Esthwaite

Delivery directory created (20080410)

comment:29 Changed 11 years ago by mark1

  • Owner changed from mark1 to anee

Has been checked with some minor corrections made to Read_me.txt (using bands 30 15 7 not 5 3 2). Example commands have been checked (without a DEM) and look ok. Data has been copied over to ~arsf/arsf_data/in_progress/2007/flight_data/uk/GB2007_05-2007_116a_Windermere_Esthwaite/

Ready to deliver.

comment:30 Changed 11 years ago by anee

ATM and Hawk data sent to PI.

comment:31 Changed 11 years ago by anee

  • Description modified (diff)

comment:32 Changed 11 years ago by mggr

Prepared for archiving (DTG, NEODC), moved to archive area (~arsf/arsf_data/complete-ready_to_archive/).

comment:33 Changed 11 years ago by anee

  • Owner changed from anee to mggr

comment:34 Changed 10 years ago by benj

Eagle lines 1-3 seem to be missing dark frames, see #218

comment:35 Changed 10 years ago by mggr

  • Priority changed from medium to high

Data already sent to NEODC for archiving.. oh dear.

comment:36 Changed 10 years ago by mggr

  • Resolution set to fixed
  • Status changed from new to closed

Belay that, line 3 has dark frames. Lines 1 & 2 are zero bytes, so obviously won't have any. The .hdr files were missing, hence being detected as not having dark frames.

comment:37 Changed 10 years ago by mggr

  • Component changed from Processing: general to Archiving

comment:38 Changed 10 years ago by mggr

Specim lines reprocessed for internal testing with new azspec, azimport and azgcorr. Timing offsets for line 3 are SCT 1.5 for Eagle, SCT 0.0 for Hawk.

Missing Eagle line 3 hdr file should be:

 VNIRse20071116a-3.hdr 
ENVI
description = {
File Imported into ENVI }
file type = ENVI
sensor type = AISA HS Instrument, SW ver 2.800
acquisition date = DATE(dd-mm-yyyy): 26-04-2007
GPS Start Time = UTC TIME: 09:26:18.5313
GPS Stop Time = UTC TIME: 09:29:30.4688
GPS Starting point = {54.441795, -3.023854}
GPS Ending point = {54.324921, -2.967976}

interleave = bil
samples = 1024
lines   = 3820
bands   = 126
autodarkstartline   = 3777
default bands = { 94, 63 , 32 }
header offset = 0
data type = 12
byte order = 0
x start = 0
y start = 0

fps =  20.00
binning = {4, 1}
vroi = {1, 126}
hroi = {2, 1024}
vimg = {1, 126}
sensorid = 100022

tint = 39.4000
himg = {72, 1024}
fodis = {28, 32}

errors = {recover}

Wavelength = { 
 986.95,
 982.07,
 977.19,
 972.31,
 967.43,
 962.56,
 957.68,
 952.80,
 947.92,
 943.04,
 938.16,
 933.29,
 928.41,
 923.53,
 918.65,
 913.77,
 908.90,
 904.04,
 899.18,
 894.32,
 889.46,
 884.59,
 879.73,
 874.87,
 870.01,
 865.14,
 860.28,
 855.42,
 850.56,
 845.70,
 840.83,
 835.97,
 831.11,
 826.25,
 821.37,
 816.50,
 811.63,
 806.75,
 801.88,
 797.01,
 792.13,
 787.26,
 782.38,
 777.51,
 772.64,
 767.76,
 762.89,
 758.02,
 753.14,
 748.31,
 743.53,
 738.75,
 733.98,
 729.20,
 724.42,
 719.64,
 714.86,
 710.08,
 705.30,
 700.53,
 695.75,
 690.99,
 686.24,
 681.48,
 676.72,
 671.97,
 667.21,
 662.45,
 657.70,
 652.94,
 648.19,
 643.43,
 638.67,
 633.92,
 629.18,
 624.43,
 619.68,
 614.93,
 610.18,
 605.43,
 600.68,
 595.93,
 591.18,
 586.43,
 581.68,
 576.93,
 572.18,
 567.43,
 562.68,
 557.93,
 553.18,
 548.43,
 543.77,
 539.20,
 534.62,
 530.04,
 525.47,
 520.89,
 516.32,
 511.74,
 507.17,
 502.59,
 498.01,
 493.44,
 488.86,
 484.29,
 479.71,
 475.14,
 470.56,
 465.98,
 461.41,
 456.83,
 452.26,
 447.68,
 443.11,
 438.53,
 434.03,
 429.64,
 425.24,
 420.85,
 416.45,
 412.06,
 407.67,
 403.27,
 398.88,
 394.48
}
fwhm= { 
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.88,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.86,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.87,
   4.79,
   4.78,
   4.78,
   4.78,
   4.78,
   4.78,
   4.78,
   4.78,
   4.78,
   4.78,
   4.78,
   4.76,
   4.76,
   4.76,
   4.76,
   4.76,
   4.76,
   4.76,
   4.76,
   4.76,
   4.76,
   4.76,
   4.76,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.75,
   4.74,
   4.59,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.58,
   4.57,
   4.41,
   4.39,
   4.39,
   4.39,
   4.39,
   4.39,
   4.39,
   4.39,
   4.39,
   4.39
}
Note: See TracTickets for help on using tickets.