Changes between Version 27 and Version 28 of Procedures/EagleHawkProcessing

Timestamp:

May 24, 2011, 3:20:40 PM (14 years ago)

Author:

knpa

Comment:

--

Procedures/EagleHawkProcessing

@@ -53 +53 @@
 If you're unlucky and the automated script fails for some reason, you may need to do at least some of the processing the old-fashioned way.
 
- 1. cd to the project directory in the workspace.
+ 1. cd to the project directory.
  1. Ensure that directories called "logs", "dem", "lev1" and "lev3" have been created.
  1. If there isn't one already, create a "calibration" symlink to the calibration data: `ln -s ~arsf/calibration/<year> calibration`.
@@ -61 +61 @@
    1. `ln -s Proc/sbet_01.out apa<year><jday>.sbet`
    1. `cd ..`
- 1. Copy the sample config file from ~arsf/sample_scripts/<year> to the project directory in the workspace - you need specim_qsub.py, process_specim_line.py and template_specim_config.cfg.
+ 1. Copy the sample config file from ~arsf/sample_scripts/<year> to the project directory - you need specim_qsub.py, process_specim_line.py and template_specim_config.cfg.
  1. Comparing the .cfg file with the logsheet, replace the entries that need to be replaced as appropriate. You should be able to see which bits these are in the sample scripts because they'll have keywords instead of values. You will need to create one cfg file section flightline per sensor.
    * Note that dates must be of the form DD/MM/YY or DD/MM/YYYY (must use / as a separator)