Changes between Version 3 and Version 4 of ProcessingAtDAN/hyper_cal/bad_pixels


Ignore:
Timestamp:
May 10, 2012 3:15:10 PM (7 years ago)
Author:
adbe
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ProcessingAtDAN/hyper_cal/bad_pixels

    v3 v4  
    11= Hawk Bad Pixel Generation =
    22
    3 The Hawk sensor contains bad pixels which are usually constant throughout the whole season, so during the calibration of Hawk bad pixels are identified and are used later in apl to mask/interpolate over bad pixels. Here is an example of a bad pixel present in the calibration data set:[[BR]]
     3The Hawk sensor contains bad pixels which are usually constant throughout the whole season, so during the calibration of Hawk bad pixels are identified and are used later in apl to mask/interpolate over bad pixels. Here is an example of a bad pixel present in the calibration data set:[[BR]][[BR]]
    44[[Image(bad_pixel_example.png)]]
    55
    6 During calibration of the hawk sensor a noise and linearity measurement should have been taken, to identify these files look in the final capture spreadsheet under ~arsf/arsf_data/YEAR/misc/CAL_DAY, the entries that are used for the bad pixel generation are listed with a "Noise & Linearity" measurement.
     6During calibration of the hawk sensor a noise and linearity measurement should have been taken, to identify these files look in the final capture spreadsheet under ~arsf/arsf_data/YEAR/misc/CAL_DAY, the entries that are used for the bad pixel generation are listed with a "Noise & Linearity" measurement. The files should be something like: NO1H1113, and have an integration time listed in the row; there may be some with a blue filter these can also be used in the detection of bad pixels.
     7
     8There are 5 detection methods for finding a bad pixel:
     9
     10== Method A ==
     11'''__Constant Light Inconstant Response__'''
     12
     13
     14[[Image(bad_pixel_example.png)]]