Changes between Version 33 and Version 34 of Procedures/OwlProcessing


Ignore:
Timestamp:
Aug 2, 2018, 11:56:46 AM (6 years ago)
Author:
asm
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Procedures/OwlProcessing

    v33 v34  
    4141
    4242Original Owl data should not be modified, nor scripts ran by ARSF in the raw directories. Use the batch script stitch_all_owl.py with a config file to automatically stitch desired files into the processing/owl/flightlines/stitched directory. The config files should be a text file with each flight line and each file to be stitched on a new line separated by a comma e.g:
    43 
    44 1, T1_OWL274-15_0844.raw [[BR]]
    45 2, T1_OWL274-15_0844.raw [[BR]]
    46 3, T1_OWL274-15_0853.raw [[BR]]
    47 
     43{{{
     441, T1_OWL274-15_0844.raw
     452, T1_OWL274-15_0844.raw
     463, T1_OWL274-15_0853.raw
     47}}}
    4848The script stitchOwl.py may be used for individual lines.
    4949
    … …  
    6666Use the -s flag if the raw files did not have dark frames and have been stitched into the processing/owl/flightlines/stitched directory.
    6767
    68 If T1 and T2 files are in different directories to the raw data a config file should be used to specify which files to use. This is formatted like this:
     68'''If T1 and T2 files are in different directories to the raw data,''' the new directories should have been named with the hour and minute recorded in their hdr. Its format will be OWLjjjs-yy_Thhmm (h: hour and m: minute) An example of this will be:
     69{{{
     70OWL135-18-1
     71├── capture
     72│   ├── DARKREF_OWL135-18-1.hdr
     73│   ├── DARKREF_OWL135-18-1.log
     74│   ├── DARKREF_OWL135-18-1.raw
     75│   ├── OWL135-18-1.hdr
     76│   ├── OWL135-18-1.log
     77│   ├── OWL135-18-1.nav
     78│   └── OWL135-18-1.raw
     79├── manifest.xml
     80├── metadata
     81│   ├── OWL135-18-1.xml
     82│   └── OWL135-18-1.xsl
     83└── properties.xml
     84
     85OWL135-18_T1150/
     86├── capture
     87│   ├── T1_OWL135-18_T1150.hdr
     88│   ├── T1_OWL135-18_T1150.log
     89│   ├── T1_OWL135-18_T1150.raw
     90│   ├── T2_OWL135-18_T1150.hdr
     91│   ├── T2_OWL135-18_T1150.log
     92│   └── T2_OWL135-18_T1150.raw
     93├── manifest.xml
     94├── metadata
     95│   ├── OWL135-18_T1150.xml
     96│   └── OWL135-18_T1150.xsl
     97└── properties.xml
     98}}}
     99
     100In this case a config file should be used to specify which calibration files have to be used to process each owl flightline. This is formatted like this:
     101{{{
     102[owl_-1]
     103black_body = 0853
    69104[owl_-2]
    70105black_body = 0853
    71 [owl_-3]
    72 black_body = 0853
    73 
     106}}}
    74107Currently this is generated manually, but will soon be automated based on GPS timestamps. The config file is specified using the -t flag to processOWL.py.
    75108