Changes between Version 68 and Version 69 of Procedures/DeliveryChecking

Timestamp:

Sep 2, 2014, 11:01:00 AM (10 years ago)

Author:

knpa

Comment:

--

Procedures/DeliveryChecking

@@ -8 +8 @@
  1. Check against the logsheet that all data that should be present is. 
  1. Check that [wiki:Processing/FilenameConventions#HyperspecDel all other folders] and contents are present
-  1. Check that there are ASCII view vector files in the sensor FOV dirs for each sensor (multiple ones if different binning has been used)
-  1. Note that there should not be a flightlines/fodis directory for 2013 deliveries
+  * 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
  1. Check for typos, etc in the documentation.
- 1. Only the PDF read me file should be present (no .tex, .out, .aux, .log files)
  1. Ensure the text files are Windows compatible (use the 'file' command on the .txt files: they should be ASCII with CRLF terminators)
  1. Test out the readme level 3 processing command for all of the level 1 files, run check_apl_cmd -c <path to hyp_genreadme config file> in delivery directory, outputs tif files to tmp_cmd_check directory, check tif files in gtviewer
@@ -30 +30 @@
  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.
- 1. Check that [wiki:Processing/FilenameConventions#Lidardeliveries all other folders] and contents are present. 
+ 1. Check that [wiki:Processing/FilenameConventions#Lidardeliveries all other folders] and contents are present.
+  * Only the PDF read me file should be present (no .tex, .out, .aux, .log files) 
  1. Check for typos, etc in the documentation.
- 1. Only the PDF read me file should be present (no .tex, .out, .aux, .log files)
  1. Ensure the text files are Windows compatible (use the 'file' command on the .txt files: they should be ASCII with CRLF terminators) 
  1. Check all the LIDAR files open/load, look OK and fit together horizontally and vertically. Either:
@@ -62 +62 @@
  1. Verify we have the correct PI (check against application, call Gloucester if unsure)
  1. Check against the readme that all data that should be present is.
- 1. Check that [wiki:Processing/FilenameConventions#Photographicdeliveries all other folders] and contents are present. 
+ 1. Check that [wiki:Processing/FilenameConventions#Photographicdeliveries all other folders] and contents are present.
+  * Only the PDF read me file should be present (no .tex, .out, .aux, .log files)
  1. Check for typos, etc in the documentation.
- 1. Only the PDF read me file should be present (no .tex, .out, .aux, .log files)
  1. View all of the thumbnail images. Look for any that are very over/under exposed or not relevant to the project. This could include: very bright images, very dark images, images of the instrument bay door, images not overlapping with any of the Eagle/Hawk data
  1. Check one (or more) of the photographs for tagging information: `exiftool photographs/FILENAME`