Changes between Version 25 and Version 26 of Procedures/DeliveryChecking

Timestamp:

Jun 21, 2011, 10:45:47 AM (13 years ago)

Author:

knpa

Comment:

Removed proj tidy mentions until that is fixed for new project structure

Procedures/DeliveryChecking

@@ -14 +14 @@
  1. Check each of the screenshots
  1. All level 1 files should be looked at visually using fastQC.
- 1. Run proj_tidy.sh on the project using delivery mode (-d flag) and look for any errors.
  1. Check level 1 files have correct read/write permissions. ` chmod 644 lev1/* `
  1. If the delivery is ready to deliver, update the dataset on the [http://arsf-dan.nerc.ac.uk/status/edit/edit.php Processing status page] to "Ready to deliver".
@@ -38 +37 @@
    * To view the DEM in envi, make a copy of it and run sed -i -e "1d" dem_copy.dem (this removes the azgcorr header)
  1. Check the screenshots look OK
- 1. Run proj_tidy.sh on the project using delivery mode (-d flag) and look for any errors.
  1. If the delivery is ready to deliver, update the dataset on the [http://arsf-dan.nerc.ac.uk/status/edit/edit.php Processing status page] to "Ready to deliver".
 
@@ -69 +67 @@
   * If thumbnails are not visible open the kml file in a text editor. Check image source is the thumbnails directory and that image filenames are correct.
  1. Check filenames correspond. If more than one project has been flown check that julian day has the letter after it (e.g. 298b). This will be in photograph, thumbnail and eventfile directories. Also check filenames in the eventfile have the julian day letter included.
- 1. Run proj_tidy.sh on the project using delivery mode (-d flag) and look for any errors.
  1. If the delivery is ready to deliver, update the dataset on the [http://arsf-dan.nerc.ac.uk/status/edit/edit.php Processing status page] to "Ready to deliver".