Changes between Version 6 and Version 7 of ProcessingAtDAN/hyper_cal/bad_pixels

Timestamp:

May 10, 2012, 3:58:45 PM (13 years ago)

Author:

adbe

Comment:

--

ProcessingAtDAN/hyper_cal/bad_pixels

@@ -4 +4 @@
 [[Image(bad_pixel_example.png)]]
 
-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. 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.
+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. 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. Type of files to choose- no filter: integration time 1 and above, blue filter: integration time 2 and above.
 
 There are 5 detection methods for finding a bad pixel:
@@ -27 +27 @@
 
 == Method C ==
+'''__Linear Input Non-Linear Response__'''
+
+In the capture spreadsheet it should say the integration time for the file, this is used in this method. If the integration time against value is not above a certain threshold then it is considered bad, ideally it should be approaching 1.
+
+