Changes between Version 38 and Version 39 of Procedures/DeliveryCreation/Hyperspectral
- Timestamp:
- Aug 22, 2017, 8:41:52 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/DeliveryCreation/Hyperspectral
v38 v39 9 9 Example: `check_processed_hyperspectral_data_is_ready.py --fenixonly` 10 10 11 == Scripted procedure==11 == Delivery Script == 12 12 13 See the guide at [wiki:Procedures/DeliveryCreation/pythonlibrary delivery library] 13 From the base directory of the project generate the structure using: 14 14 15 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. 15 {{{ 16 make_arsf_delivery.py --projectlocation $PWD \ 17 --deliverytype hyperspectral --steps STRUCTURE 18 }}} 19 If everything looks OK run again with `--final` 16 20 17 ==== Making the Readme ==== 21 Once the structure has been generated run the other steps using: 22 {{{ 23 make_arsf_delivery.py --projectlocation $PWD \ 24 --deliverytype hyperspectral --notsteps STRUCTURE 25 }}} 26 Again pass in `--final` if the output all looks OK. 27 28 See the [wiki:Procedures/DeliveryCreation/pythonlibrary delivery library guide] for more details on advanced options. 29 30 == Readme Generation == 18 31 19 32 To make the readme first generate the readme config file using … … 27 40 Finally run `pdflatex <readme_tex_file>` to create the PDF readme (you probably need to run this twice). This readme should be placed in the main delivery folder. 28 41 29 == Manual procedure ==42 == Manual procedure (if above fails) == 30 43 31 44 The following is a more manual procedure that is only required if the scripts above fail.