Changes between Version 17 and Version 18 of Procedures/EndUserDelivery

Timestamp:

Dec 17, 2007, 1:04:08 PM (17 years ago)

Author:

mggr

Comment:

--

Procedures/EndUserDelivery

@@ -1 +1 @@
 = Data Delivery =
 
+Stages:
+ * Preparation
+ * Verification (should be done by a different person)
+ * Finalisation (burning, letter, trac and delivery)
+
 It may be worth printing this page out and ticking each item to ensure they're done.
+------------------------
+== Preparation ==
+=== What should be included ===
+ * level 1 data that has been mapped to level 3 successfully and verified as correctly geolocated (as far as possible).
+ * a readme file describing the contents of the delivery
+ * flight logsheet
+ * screenshots (level 3)
+   * one of each line (no vectors)
+   * mosaic of all lines for a single sensor, one with and one without vectors overlaid
+   * 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
+ * (2008?) a DEM file where we have one and can give it to the user
+ * any ancillary files (spheroid separation grids for non-UK flights, OS GB correction factors, etc)
 
-== Prerequisites ==
- * level 1 data that has been mapped to level 3 successfully and verified as correctly geolocated (as far as possible).
- * flight logsheet
+There are delivery template directories available (copy these and populate):
+2006::
+ ~arsf/arsf_data/in_progress/2006/delivery_template/
+2007::
+ ~arsf/arsf_data/in_progress/2007/delivery_template/
 
-=== Screenshots ===
-One per line, with vectors overlaid?  ''Need to specify what we want to see in these.''
+The 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).
 
+=== Necessary comments to make in the readme file ===
+ 1. Update anything marked TODO in the template
+ 1. Appropriate pixel size
+ 1. Comments on the quality of the data (accuracy vs vectors, any bad bands, etc) and any specific problems encountered
+ 1. Include a tested example command to convert the data from level 1 to level 3
+ 1. Ensure the text file is in Windows format (run `unix2dos` on it if necessary)
+ 1. ''(list of other things to change)''
+
+------------------------
 == Verification ==
 
 Once a dataset has been prepared for burning and delivery, a second person should go over it and:
+ 1. Check against the logsheet that all data that should be present is.
  1. Check for typos, etc in the documentation.
+ 1. Ensure the readme and other text files are Windows compatible (run `unix2dos ReadMe.txt`)
  1. Test out the level 3 processing command for one or more of the level 1 files (definitely one per sensor).
  1. All level 1 files should be looked at visually (ideally in all bands, though this is only practical for ATM and casi).
- 1. Check against the logsheet that all data that should be present is.
 
-== Preparation of data for burning ==
-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.
+------------------------
+== Final steps ==
 
- 1. `ssh pmpc886`
- 1. `~arsf/usr/bin/delivery_prep_2006.sh PROJECTCODE JULIANDAY`
- 1. change dir to the newly created delivery directory '''Note:''' ''this directory will be created in /tmp, which is automatically deleted after 3 days!''
- 1. Copy in:
-   1. the level-1 files to lev1/
-   1. the logsheet to logsheet/
-   1. the screenshots to screenshots/
- 1. replace any Unix-upsetting characters (spaces, brackets, etc) in filenames
- 1. edit the Read_Me.txt-MUST_EDIT file
-   1. Appropriate pixel size
-   1. Comments on the quality of the data and any specific problems encountered
-   1. Ensure the text file is in Windows format (run `unix2dos` on it if necessary)
-   1. ''(list of other things to change)''
- 1. '''Verification''': get someone else to go through the verification steps in the section above
- 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
- 1. Burn the data
-   1. create an iso image with `mkisofs -R -udf -verbose -o /tmp/dvd.iso -V <ARSF-PROJECTCODE-JULIANDAY> <delivery_directory>`
-   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)
-   1. if it's ok, burn to CD/DVD with `sudo cdrecord dev=/dev/dvdwriter -sao fs=100m driveropts=burnfree -v /tmp/dvd.iso`
-   1. clean up with `rm /tmp/dvd.iso`
+=== Burning the data ===
+ 1. create an iso image with `mkisofs -R -udf -verbose -o /tmp/dvd.iso -V <PROJECTCODE-JULIANDAY> <delivery_directory>`
+ 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)
+ 1. if it's ok, burn to CD/DVD with `sudo cdrecord dev=/dev/dvdwriter -sao fs=100m driveropts=burnfree -v /tmp/dvd.iso`
+ 1. clean up with `rm /tmp/dvd.iso`
+ 1. check the dvd on another machine (ideally Windows)
 
-== Final steps ==
- 1. Get someone else to check the DVD
- 1. Print out cover letter, instructions (Readme?)
- 1. Post to user
- 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
+=== Cover letter ===
+There should be a cover letter with all deliveries.  Templates can be found at:
+2006::
+2007::
+ ~arsf/arsf_data/in_progress/2007/delivery_letter-2007-template.doc
 
+=== Trac and website updating ===
+
+Add 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.
+