Changes between Version 106 and Version 107 of Procedures/DeliveryChecking


Ignore:
Timestamp:
Aug 24, 2017 9:14:23 AM (19 months ago)
Author:
dac
Comment:

Updated to use headings and changed status page link to new URL.

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryChecking

    v106 v107  
    33Once a dataset has been prepared for delivery, a second person should go over it and perform the checks below. These should be performed as your own user (rather than arsf or airborne), except where necessary. This minimises the chances of data being unintentionally overwritten or deleted.
    44
    5 === Note: if this is your first time doing a delivery check, please get a third (experienced) person to perform a second check when you're done ===
     5'''Note: if this is your first time doing a delivery check, please get a third (experienced) person to perform a second check when you're done'''
    66
    7 '''For Hyperspectral Data'''
     7== Hyperspectral Data ==
    88
    9  1. Verify we have the correct PI (check against application, call Gloucester if unsure)
     9 1. Verify we have the correct PI (check against application, call Opps if unsure)
    1010 1. Check against the logsheet that all data that should be present is.
    1111  * Number of files and sensible file sizes
     
    3131  1. Make sure that all bands have been mapped (not just 3). You can use {{{check_num_bands.py *bil}}} to check the number of bands for all files.
    3232 1. Check the projection used is correct - especially the correct UTM zone for the data
    33  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".
     33 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".
    3434 1. If everything is ready to deliver, i.e. no more changing of ReadMe files, then in the sensor delivery directory run the script `zip_mapped.sh`.
    35   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 `arsf-code@pml.ac.uk`. You should also '''check the log files named zip* in <project directory>/logfiles before delivering the data'''.
     35  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'''.
    3636 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.
    3737
    38 '''For LIDAR Data'''
    39  1. Verify we have the correct PI (check against application, call Gloucester if unsure)
     38== LiDAR Data ==
     39 1. Verify we have the correct PI (check against application, call Opps if unsure)
    4040 1. Check against the logsheet that all data that should be present is.
    4141 1. Check that [wiki:Processing/FilenameConventions#Lidardeliveries all other folders] and contents are present.
     
    5858 1. Run proj_tidy.sh -c -p <path_to_project>. Check if any of the problems listed apply to your delivery.
    5959 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
    60  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".
     60 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".
    6161 [[BR]]'''Full waveform deliveries only'''[[BR]]
    6262 1.  Check some of the full waveform LAS files. Either:
     
    6868 1. Use lasinfo to check the AGC value has been saved in the 'user_data' field (min and max values should be non-zero).
    6969
    70 '''For Digital Photography Data'''
     70== Digital Photography Data ==
    7171 
    72  1. Verify we have the correct PI (check against application, call Gloucester if unsure)
     72 1. Verify we have the correct PI (check against application, call Opps if unsure)
    7373 1. Check against the readme that all data that should be present is.
    7474 1. Check that [wiki:Processing/FilenameConventions#Photographicdeliveries all other folders] and contents are present.
     
    8585 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.
    8686 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.
    87  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".
     87 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".
    8888
    8989