Changes between Version 4 and Version 5 of Processing/BadATMScans


Ignore:
Timestamp:
Sep 3, 2008 2:31:40 PM (11 years ago)
Author:
anee
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/BadATMScans

    v4 v5  
    1010 * Once the bil files have been created, run '''''atm_bad_scans.py -f <filename> -t <pixel_threshold> -m <multiple> -b <bands>'''''.
    1111   * -f file to scan
    12    * -t number of pixels which have to be bad for a line to be considered bad
    13    * -m if a pixel in the current line is -m times larger or smaller than a pixel in previous the line it is considered bad
    14 
    15 This will read band 7 of all the bil files and returns all the bad scan lines it finds (and writes these into a txt file with the same name as the bil file for easy copy and paste into the scripts). Currently these are just lines which contain significant numbers of 0 values or complete lines of high values. Other, harder to detect bad scans may exist so it is worth keeping an eye out for these.
     12   * -t number of pixels which have to be bad for a line to be considered bad (good starting point ~120)
     13   * -m if a pixel in the current line is -m times larger or smaller than a pixel in previous the line it is considered bad (good starting point ~3)
     14This will read all the bands in the bil file and returns all the bad scan lines it finds (and writes these into a txt file with the same name as the bil file for easy copy and paste into the scripts). The bad scans are high values and 'slipped scans'. All zero value scans (and most of the slipped scans) should be removed automatically by the az* software.
    1615
    1716 * Copy the bad scan line numbers from the txt files into the corresponding scripts after the -eds option. The lines numbers entered into the scripts will be marked as bad in the hdfs after running the scripts. These will still be visible when viewing the hdfs but will not be present in the level 3 GeoTIFFs.