| 1 | == Thermal Data Delivery == |
| 2 | |
| 3 | 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. |
| 4 | |
| 5 | == Delivery Script == |
| 6 | |
| 7 | From the base directory of the project generate the structure using: |
| 8 | |
| 9 | {{{ |
| 10 | make_arsf_delivery.py --projectlocation $PWD \ |
| 11 | --deliverytype owl --steps STRUCTURE |
| 12 | }}} |
| 13 | If everything looks OK run again with `--final` |
| 14 | |
| 15 | Once the structure has been generated run the other steps using: |
| 16 | {{{ |
| 17 | make_arsf_delivery.py --projectlocation $PWD \ |
| 18 | --deliverytype owl --notsteps STRUCTURE |
| 19 | }}} |
| 20 | Again pass in `--final` if the output all looks OK. |
| 21 | |
| 22 | See the [wiki:Procedures/DeliveryCreation/pythonlibrary delivery library guide] for more details on advanced options. |
| 23 | |
| 24 | == Readme Generation == |
| 25 | |
| 26 | To make the readme first generate the readme config file using |
| 27 | |
| 28 | {{{ |
| 29 | generate_readme_config.py -d <delivery directory> -r hyper -c <config_file> |
| 30 | }}} |
| 31 | |
| 32 | The readme config file will be saved as hyp_genreadme-airbone_owl.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. |
| 33 | |
| 34 | Then create a readme tex file using: |
| 35 | {{{ |
| 36 | create_latex_hyperspectral_apl_readme.py -f hyp_genreadme-airbone_owl.cfg |
| 37 | }}} |
| 38 | |
| 39 | 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. |