Opened 11 years ago

Closed 10 years ago

#197 closed flight processing (fixed)

VOC_03, flight day 304/2008, Chile

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

Description (last modified by benj)

Data location: /data/larsenb1/scratch/arsf/vocals/VOC_03-2008_304_Chile (symlink in ~arsf/arsf_data/in_progress/2008/flight_data/vocals/VOC_03-2008_304_Chile/)

Data arrived from ARSF via SATA disk (no letter) on 7th November 2008.

Scientific details: VOCALS Cloud Campaign

Priority:

PI: G. Vaughan

Sensors:

  • Eagle
  • Hawk

Quicklook

TBD.

Change History (25)

comment:1 Changed 11 years ago by mark1

Eagle Data: 14 lines, all with all files!

Hawk Data: 3 lines with all files (1,7,14), 11 lines without .log files (is this important from a processing point of view)

comment:2 Changed 11 years ago by mark1

  • Description modified (diff)

no flight log sheet

comment:3 Changed 11 years ago by jatt

  • Owner set to jatt

comment:4 Changed 11 years ago by jatt

  • Owner changed from jatt to mark1

flight log sheet received

Delivery directory created at ~jatt/scratch/ARSF/VOC_03-2008_304_Chile

comment:5 Changed 11 years ago by mark1

  • Owner changed from mark1 to jatt

Delivery checked and mostly looks ok. Made a few changes to Read_me (projection information for example command explanation). Before rsync just wanted to check that the table at the top of the read_me is consistent with other vocals projects: EG site details and project code (I know these are from the logsheet but are they correct - is this how the other ones were named?).

Also, the hawk screenshots...do you think its worth while re-doing them at different bands or not? If its not much work I'd suggest it, but if its gonna take a while then maybe not worth it.

comment:6 Changed 11 years ago by mark1

  • Description modified (diff)

comment:7 Changed 11 years ago by jatt

Table at the top of the read_me is consistent with the other vocals projects.

Hawk screenshots have been redone with different bands and are now easier to view.

Rsynced to ~arsf/arsf_data/2008/flight_data/vocals/VOC_02-2008_304_Chile

comment:8 Changed 11 years ago by mark1

correction to above path: Rsynced to ~arsf/arsf_data/2008/flight_data/vocals/VOC_03-2008_304_Chile

comment:9 Changed 11 years ago by jatt

New header files created for the following flight lines. These have updated GPS start and stop times to correct sync errors, the original header files have been renamed by adding -old to the filename.

  • SWIRshvoc03_30408-4.hdr
  • SWIRshvoc03_30408-6.hdr
  • SWIRshvoc03_30408-11.hdr
  • SWIRshvoc03_30408-12.hdr


comment:10 Changed 11 years ago by benj

  • Description modified (diff)

Moved data to larsenb

comment:11 Changed 11 years ago by jatt

Following an update to azspec, the sync errors went away, so all original header files have been reinstated.

comment:12 Changed 11 years ago by jatt

  • Owner changed from jatt to benj

Delivery directory created at ~arsf/arsf_data/2008/flight_data/vocals/VOC_03-2008_304_Chile/delivery/20090408/VOC03

comment:13 Changed 11 years ago by benj

Data quality report needs updating before delivery

comment:14 Changed 11 years ago by benj

Eagle and Hawk line 1 seem to have a lot of omitted pixels? Eagle has 1800(ish), Hawk has 37k(!). I can't find the processing logs so I can't check what happened during the original processing run, but that's what I get during delivery checking.

comment:15 Changed 11 years ago by benj

Sorry, omitted lines, not pixels.

comment:16 Changed 11 years ago by benj

Eagle line 1, if you look at RGB bands 216, 166 and 80 (or 7), there seems to be a blue stripe down the middle of the line (as opposed to a more purple colour at the edges). Have talked to Steve, he thinks it's probably OK - to do with relative amounts of scattering from the different viewing angles with the sun directly overhead (as it would have been for that line).

comment:17 Changed 11 years ago by benj

The level 1 file in the delivery directory for Eagle line 13 is only 470k and is inconsistent with the claimed number of lines (header claims 38761 lines, 252 bands, 953 pixels per band, should give a size of about 18GB). Needs to be looked at before this can be delivered.

comment:18 Changed 11 years ago by benj

Rest looks fine, ready for delivery once the issue with eagle line 13 is sorted out.

comment:19 Changed 11 years ago by benj

  • Owner changed from benj to jatt

comment:20 Changed 11 years ago by jatt

All data delivered on 18th May 2009.

comment:21 Changed 11 years ago by jatt

Flight lines 1, 2 and 14 are CM 69.
Flight lines 3-13 are CM 75.

The pitch, roll and heading values used for this flight are:-

Sensor: Eagle

Flight Line Pitch Roll Heading
01-14 -0.2 -0.45 -0.5

Sensor: Hawk

Flight Line Pitch Roll Heading
01 0.224 0.171 0.877
02 -0.243 0.142 0.777
03 -0.248 0.125 0.657
04 -0.195 0.118 0.744
05 -0.237 0.112 0.837
06 -0.233 0.13 0.757
07 -0.27 0.32 0.66
08 -0.157 0.124 0.818
09 -0.215 0.34 0.758
10 -0.262 0.155 0.982
11 0.374 0.307 0.783
12 -0.306 0.314 0.843
13 -0.247 0.324 0.732
14 -0.234 0.304 0.715

comment:22 Changed 11 years ago by mggr

Requested archiving by Sandra.

comment:23 Changed 10 years ago by mggr

  • Component changed from Processing: general to Archiving
  • Owner changed from jatt to mggr

Archived locally by DTG on 15/Jun/2009. Ready to go to NEODC.

comment:24 Changed 10 years ago by benj

Copied to USB disk 41 10/2/2010 ready for delivery to NEODC.

comment:25 Changed 10 years ago by benj

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

Disk posted to NEODC 18/02/2010

Note: See TracTickets for help on using tickets.