Changes between Version 16 and Version 17 of Procedures/EndUserDelivery


Ignore:
Timestamp:
Nov 13, 2007 7:16:10 PM (11 years ago)
Author:
mggr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/EndUserDelivery

    v16 v17  
    1212== Verification ==
    1313
    14 Once a dataset has been prepared for burning and delivery, a second person should go over it, checking for typos, etc.  They should also test out the level 3 processing command for one or more of the level 1 files and confirm it works.  All level 1 files should be looked at visually (ideally in all bands).
    15 
    16 ''Fill in the other stuff we do/should do here''
    17  * replace any Unix-upsetting characters (spaces, brackets, etc) in filenames
     14Once a dataset has been prepared for burning and delivery, a second person should go over it and:
     15 1. Check for typos, etc in the documentation.
     16 1. Test out the level 3 processing command for one or more of the level 1 files (definitely one per sensor).
     17 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.
    1819
    1920== Preparation of data for burning ==
     
    2728   1. the logsheet to logsheet/
    2829   1. the screenshots to screenshots/
     30 1. replace any Unix-upsetting characters (spaces, brackets, etc) in filenames
    2931 1. edit the Read_Me.txt-MUST_EDIT file
    3032   1. Appropriate pixel size
     
    3234   1. Ensure the text file is in Windows format (run `unix2dos` on it if necessary)
    3335   1. ''(list of other things to change)''
    34  1. Check against the logsheet that all data that should be present is
    3536 1. '''Verification''': get someone else to go through the verification steps in the section above
    3637 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