Changes between Version 20 and Version 21 of Procedures/DeliveryCreation/Hyperspectral

Timestamp:

Oct 28, 2010, 5:19:17 PM (14 years ago)

Author:

iopa

Comment:

--

Procedures/DeliveryCreation/Hyperspectral

@@ -34 +34 @@
    * For non-UK flights, copy in ~arsf/dems/geoid-spheroid/sphsep15lx.grd UNLESS we supply a LIDAR DEM in which case they will not need this file.
  1. If the script has not done so, copy the mosaics and jpegs of flightlines created above into the screenshots directory
- 1. Ensure that the filenames of the level 1 files and flightline jpegs are correct - they should be [eh]JJJaff1b.*, where [eh] is e for eagle or h for hawk, JJJ is the julian day of the flight, a is a flight letter if appropriate (usually a, b or occasionally c), and ff is the flightline number. There should be one level 1 file (or set of files, if there are .bil and .bil.hdr files in addition to the HDF) per flightline. If any are missing for particular sensors (eg. because the sensor failed), this should be explained in the readme file.  
  1. '''New style read me is largely untested - expect some errors - let mark1 know so he can fix the scripts.'''
   1. Create a config file for the read me using the generate_readme_config.py script. Use a command such as `generate_readme_config.py -d <delivery_directory> -r hyper` 
@@ -43 +42 @@
    1. line_numbering should contain a space separated list of line names linking the logsheet to the processed files.
    1. All "compulsory" items should contain data
+ 1. Step 7 below has been '''provisionally''' scripted in full but still might require fixing and feedback (to iopa)
+   1. If the filled in config file is put in the delivery directory then
+   1. To fix filenames, generate TeX and PDF use `deliverProject.sh -d <main project directory> -p <project code> -i <PI name>` to display what will be executed
+   1. If everything seems in order then add '-x' to execute it all.
+ 1. Fix file names and use the config file above to generate the readme Tex and PDF
+  1. Ensure that the filenames of the level 1 files and flightline jpegs are correct - they should be [eh]JJJaff1b.*, where [eh] is e for eagle or h for hawk, JJJ is the julian day of the flight, a is a flight letter if appropriate (usually a, b or occasionally c), and ff is the flightline number. There should be one level 1 file (or set of files, if there are .bil and .bil.hdr files in addition to the HDF) per flightline. If any are missing for particular sensors (eg. because the sensor failed), this should be explained in the readme file.
   1. Create a TeX file. Use the script `create_latex_hyperspectral_readme.py -f <config filename>`
    1. This file can be reviewed and edited in any text editor if needed.