Changes between Version 27 and Version 28 of Procedures/OwlProcessing


Ignore:
Timestamp:
Aug 1, 2017 11:47:08 AM (23 months ago)
Author:
lah
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/OwlProcessing

    v27 v28  
    124124
    125125== Readme ==
    126 
    127 There is no separate owl option for make a readme. Generate a config file for the Fenix and manually edit it for the Owl. If you just edit the tex file you will have to run autoqc on the command line, but if there are no overflows and underflows just remove the table from the readme and state it in a sentence instead.
     126Generate the readme as you would for the fenix (with -r hyper). The correct entries for the owl will be automatically filled in. Expect there to be overflows in the highest bands (near 100) only.
    128127
    129128== Checking ==
    130129
    131 Follow the Fenix delivery checking procedure.
     130Follow the Fenix delivery checking procedure. Currently there are no badpixelmethod files generated for the owl.
    132131
    133132Also check that detector response is stable across the entire flight by examining the calibration (.rad) files (These are also bil files). If there are dramatic changes in the calibration curves for a particular flight line, make sure that it is not used to calibrate a different flight line. You will also need to double check that the data processed for that flight line look correctly calibrated.