Changes between Version 38 and Version 39 of Procedures/DeliveryCreation/Hyperspectral


Ignore:
Timestamp:
Aug 22, 2017 8:41:52 AM (21 months ago)
Author:
dac
Comment:

Added delivery commands and general tidy up.

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/DeliveryCreation/Hyperspectral

    v38 v39  
    99Example: `check_processed_hyperspectral_data_is_ready.py --fenixonly`
    1010
    11 == Scripted procedure ==
     11== Delivery Script ==
    1212
    13 See the guide at [wiki:Procedures/DeliveryCreation/pythonlibrary delivery library]
     13From the base directory of the project generate the structure using:
    1414
    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{{{
     16make_arsf_delivery.py --projectlocation $PWD \
     17                      --deliverytype hyperspectral --steps STRUCTURE
     18}}}
     19If everything looks OK run again with `--final`
    1620
    17 ==== Making the Readme ====
     21Once the structure has been generated run the other steps using:
     22{{{
     23make_arsf_delivery.py --projectlocation $PWD \
     24                      --deliverytype hyperspectral --notsteps STRUCTURE
     25}}}
     26Again pass in `--final` if the output all looks OK.
     27
     28See the [wiki:Procedures/DeliveryCreation/pythonlibrary delivery library guide] for more details on advanced options.
     29
     30== Readme Generation ==
    1831
    1932To make the readme first generate the readme config file using
     
    2740Finally 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. 
    2841
    29 == Manual procedure ==
     42== Manual procedure (if above fails) ==
    3043
    3144The following is a more manual procedure that is only required if the scripts above fail.