Changes between Version 57 and Version 58 of Procedures/DeliveryChecking


Ignore:
Timestamp:
Oct 30, 2013, 10:44:31 AM (10 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryChecking

    v57 v58  
    1515 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
    1616 1. Check each of the screenshots
    17  1. Run proj_tidy.sh -c -p <path_to_project>. This will do a variety of tests, which should be checked.
     17 1. Run proj_tidy.sh -c -p <path_to_project>. Check if any of the problems listed apply to your delivery.
    1818 1. All level 1 files should be looked at visually using fastQC.
    1919  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)
     
    3030 1. Verify we have the correct PI (check against application, call Gloucester if unsure)
    3131 1. Check against the logsheet that all data that should be present is.
     32 1. Check that [wiki:Processing/FilenameConventions#Delivereddata all other folders] and contents are present.
    3233 1. Check for typos, etc in the documentation.
    3334 1. Only the PDF read me file should be present (no .tex, .out, .aux, .log files)
     
    4344 1. Check the projection used is correct - especially the correct UTM zone for the data
    4445 1. Check the screenshots look OK
    45  1. Run proj_tidy.sh -c -p <path_to_project>. This will do a variety of tests, which should be checked.
     46 1. Run proj_tidy.sh -c -p <path_to_project>. Check if any of the problems listed apply to your delivery.
    4647 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
    4748 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".
     
    6566 1. View one of the photographs to check it opens OK.
    6667 1. Check file sizes of photographs look reasonable (224M) and there are no _tmp photo files.
    67  1. Run proj_tidy.sh -c -p <path_to_project>. This will do a variety of tests, which should be checked.
     68 1. Run proj_tidy.sh -c -p <path_to_project>. Check if any of the problems listed apply to your delivery.
    6869 1. Open the kml file in googleearth and check it looks good and that thumbnails are displayed when the push pins are clicked.
    6970  * 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.