Changes between Version 17 and Version 18 of Procedures/EndUserDelivery


Ignore:
Timestamp:
Dec 17, 2007 1:04:08 PM (12 years ago)
Author:
mggr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/EndUserDelivery

    v17 v18  
    11= Data Delivery =
    22
     3Stages:
     4 * Preparation
     5 * Verification (should be done by a different person)
     6 * Finalisation (burning, letter, trac and delivery)
     7
    38It may be worth printing this page out and ticking each item to ensure they're done.
     9------------------------
     10== Preparation ==
     11=== What should be included ===
     12 * level 1 data that has been mapped to level 3 successfully and verified as correctly geolocated (as far as possible).
     13 * a readme file describing the contents of the delivery
     14 * flight logsheet
     15 * screenshots (level 3)
     16   * one of each line (no vectors)
     17   * mosaic of all lines for a single sensor, one with and one without vectors overlaid
     18   * each screenshot should try to show typical or noteworthy characteristics of the image - e.g. any distortion or error, or a typical part of the scene
     19 * (2008?) a DEM file where we have one and can give it to the user
     20 * any ancillary files (spheroid separation grids for non-UK flights, OS GB correction factors, etc)
    421
    5 == Prerequisites ==
    6  * level 1 data that has been mapped to level 3 successfully and verified as correctly geolocated (as far as possible).
    7  * flight logsheet
     22There are delivery template directories available (copy these and populate):
     232006::
     24 ~arsf/arsf_data/in_progress/2006/delivery_template/
     252007::
     26 ~arsf/arsf_data/in_progress/2007/delivery_template/
    827
    9 === Screenshots ===
    10 One per line, with vectors overlaid?  ''Need to specify what we want to see in these.''
     28The delivery data should be created in the project directory named `delivery/YYYYMMDD/PROJECTCODE/...` (e.g. delivery/20071215/GB07-05 for a delivery of GB07-05 created on 15/Dec/2007).
    1129
     30=== Necessary comments to make in the readme file ===
     31 1. Update anything marked TODO in the template
     32 1. Appropriate pixel size
     33 1. Comments on the quality of the data (accuracy vs vectors, any bad bands, etc) and any specific problems encountered
     34 1. Include a tested example command to convert the data from level 1 to level 3
     35 1. Ensure the text file is in Windows format (run `unix2dos` on it if necessary)
     36 1. ''(list of other things to change)''
     37
     38------------------------
    1239== Verification ==
    1340
    1441Once a dataset has been prepared for burning and delivery, a second person should go over it and:
     42 1. Check against the logsheet that all data that should be present is.
    1543 1. Check for typos, etc in the documentation.
     44 1. Ensure the readme and other text files are Windows compatible (run `unix2dos ReadMe.txt`)
    1645 1. Test out the level 3 processing command for one or more of the level 1 files (definitely one per sensor).
    1746 1. All level 1 files should be looked at visually (ideally in all bands, though this is only practical for ATM and casi).
    18  1. Check against the logsheet that all data that should be present is.
    1947
    20 == Preparation of data for burning ==
    21 A template file structure for the 2006 data delivery is at ~arsf/arsf_data/2006/delivery_template/.  You need to create a copy on pmpc886 (where the DVD burner is).  The easiest way to do this is to use a little script.
     48------------------------
     49== Final steps ==
    2250
    23  1. `ssh pmpc886`
    24  1. `~arsf/usr/bin/delivery_prep_2006.sh PROJECTCODE JULIANDAY`
    25  1. change dir to the newly created delivery directory '''Note:''' ''this directory will be created in /tmp, which is automatically deleted after 3 days!''
    26  1. Copy in:
    27    1. the level-1 files to lev1/
    28    1. the logsheet to logsheet/
    29    1. the screenshots to screenshots/
    30  1. replace any Unix-upsetting characters (spaces, brackets, etc) in filenames
    31  1. edit the Read_Me.txt-MUST_EDIT file
    32    1. Appropriate pixel size
    33    1. Comments on the quality of the data and any specific problems encountered
    34    1. Ensure the text file is in Windows format (run `unix2dos` on it if necessary)
    35    1. ''(list of other things to change)''
    36  1. '''Verification''': get someone else to go through the verification steps in the section above
    37  1. copy the Read_Me.txt to the original project directory (~arsf/arsf_data/2006/...) as a backup and so we can refer to it later
    38  1. Burn the data
    39    1. create an iso image with `mkisofs -R -udf -verbose -o /tmp/dvd.iso -V <ARSF-PROJECTCODE-JULIANDAY> <delivery_directory>`
    40    1. test the iso with `sudo mount -o ro,loop /tmp/dvd.iso /mnt/tmp` - mounts to /mnt/tmp, go look at it, then unmount with `sudo umount /mnt/tmp` (yes, that is umount not unmount)
    41    1. if it's ok, burn to CD/DVD with `sudo cdrecord dev=/dev/dvdwriter -sao fs=100m driveropts=burnfree -v /tmp/dvd.iso`
    42    1. clean up with `rm /tmp/dvd.iso`
     51=== Burning the data ===
     52 1. create an iso image with `mkisofs -R -udf -verbose -o /tmp/dvd.iso -V <PROJECTCODE-JULIANDAY> <delivery_directory>`
     53 1. test the iso with `sudo mount -o ro,loop /tmp/dvd.iso /mnt/tmp` - mounts to /mnt/tmp, go look at it, then unmount with `sudo umount /mnt/tmp` (yes, that is umount not unmount)
     54 1. if it's ok, burn to CD/DVD with `sudo cdrecord dev=/dev/dvdwriter -sao fs=100m driveropts=burnfree -v /tmp/dvd.iso`
     55 1. clean up with `rm /tmp/dvd.iso`
     56 1. check the dvd on another machine (ideally Windows)
    4357
    44 == Final steps ==
    45  1. Get someone else to check the DVD
    46  1. Print out cover letter, instructions (Readme?)
    47  1. Post to user
    48  1. Create a trac support ticket noting that the data has been delivered and that we should contact the user in a week to ensure it's arrived and is ok
     58=== Cover letter ===
     59There should be a cover letter with all deliveries.  Templates can be found at:
     602006::
     612007::
     62 ~arsf/arsf_data/in_progress/2007/delivery_letter-2007-template.doc
    4963
     64=== Trac and website updating ===
     65
     66Add a comment on the trac ticket for this project that this data has been delivered (describe what was sent and when).  Also add a quicklook to the ticket.
     67