Changes between Version 71 and Version 72 of Procedures/DeliveryChecking

Timestamp:

Sep 5, 2014, 5:26:10 PM (10 years ago)

Author:

mark1

Comment:

--

Procedures/DeliveryChecking

@@ -7 +7 @@
  1. Verify we have the correct PI (check against application, call Gloucester if unsure)
  1. Check against the logsheet that all data that should be present is. 
+  * Number of files and sensible file sizes 
  1. Check that [wiki:Processing/FilenameConventions#HyperspecDel all other folders] and contents are present
   * Only the PDF read me file should be present (no .tex, .out, .aux, .log files)
   * Check that there are ASCII view vector files in the sensor FOV dirs for each sensor (multiple ones if different binning has been used)
-  * Note that there should not be a flightlines/fodis directory for 2013 deliveries
+  * '''Note that there should not be a flightlines/fodis directory for 2013 deliveries'''
  1. Check for typos, etc in the documentation.
  1. Ensure the text files are Windows compatible (use the 'file' command on the .txt files: they should be ASCII with CRLF terminators)
@@ -19 +20 @@
   1. If any pixels appear to be constantly bad (c.f. 2009? dust on lens problems) then return to processor for re-processing calibration using a list of additional bad pixels to mask (see aplcal -qcfailures)
   1. In this case additional information should be added into read me to explain why they are being masked
- 1. Check a selection of the lev3 mapped files open and look OK (don't need to go through all the bands)
+ 1. Check all of the lev3 mapped files open and look OK (don't need to go through all the bands)
   1. Make sure that all bands have been mapped (not just 3)
  1. Check the projection used is correct - especially the correct UTM zone for the data