Changes between Version 109 and Version 110 of Procedures/DeliveryChecking

Timestamp:

Aug 24, 2017, 12:09:16 PM (7 years ago)

Author:

dac

Comment:

Added owl specific info

Procedures/DeliveryChecking

@@ -6 +6 @@
 
 == Hyperspectral Data ==
+
+Includes, Eagle, Hawk, Fenix and Owl
 
  1. Verify we have the correct PI (check against application, call Ops if unsure)
@@ -35 +37 @@
   1. This should zip each mapped file and its header into a zip file. This will be done on the grid. If it fails, an email will be sent to `nerc-arf-code@pml.ac.uk`. You should also '''check the log files named zip* in <project directory>/logfiles before delivering the data'''.
  1. Add a comment on the ticket saying what problems there are / things that need resolving / things that you have resolved yourself / whether the data is ready to deliver.
+
+=== Additional Checks for Owl data ===
+
+* Currently there are no badpixelmethod files generated for the owl.
+* Also check that detector response is stable across the entire flight by examining the calibration (.rad) files (These are also bil files). If there are dramatic changes in the calibration curves for a particular flight line, make sure that it is not used to calibrate a different flight line. You will also need to double check that the data processed for that flight line look correctly calibrated.
 
 == LiDAR Data ==
@@ -87 +94 @@
  1. If the delivery is ready to deliver, update the dataset on the [https://nerc-arf-dan.pml.ac.uk/status/edit/edit.php Processing status page] to "Ready to deliver".
 
-
--------------------------------------