Changes between Version 31 and Version 32 of Procedures/DeliveryCreation/Hyperspectral

Timestamp:

Jun 8, 2012, 10:36:26 AM (12 years ago)

Author:

mark1

Comment:

--

Procedures/DeliveryCreation/Hyperspectral

@@ -2 +2 @@
 
 Once the data has been processed, it needs to be put into a delivery directory. This is the final file structure in which it will be sent to the customer.
+
+== Scripted procedure ==
+
+Use the make_hyper_delivery.py script to make the delivery directory. Run it from within the main project directory. By default it runs in dry run mode. Make sure the only lev3's in the georeferencing/mapped directory are the sct correct versions.
+
+Use --final if happy with what it says it will do. Use -m <config> to generate screenshots and mosaics
+
+Note: this script automatically moves over the contents of the DEM directory. You will need to revert this if this is a nextmap DEM as these shouldn't be delivered, and include an ASTER DEM instead.
+
+==== Making the Readme ====
+
+To make the readme first generate the readme config file using
+
+`generate_readme_config.py -d <delivery directory> -r hyper -c <config_file>`
+
+The readme config file will be saved as hyp_genreadme-airbone.cfg in the processing directory, do not delete this file as it is required for delivery checking. Check all the information in the readme config file is correct, if not change it.  
+
+Then create a readme tex file using: `create_latex_hyperspectral_apl_readme.py -f <readme_config_file>`
+
+Finally run `latex <readme_tex_file>` to create the PDF readme. This readme should be placed in the main delivery folder.  
+
+== Manual procedure ==
+
+The following is a more manual procedure that is only required if the scripts above fail.
 
  1. Create quicklook jpegs.