Possible bad pixels or calibration for Hawk

[benj]

Some Hawk pixels appear to either be bad or to have bad calibration. Spectrum spikes seem to occur in the raw data. If you take two points in the raw data from the same pixel on different scan lines they both have very similar spikes, suggesting bad pixels for specific bands on the sensor itself, eg:

If you take two points in the raw data from different pixels on the same scan line, they both have spikes but in different places:

This suggests that most spatial pixels on the Hawk CCD have at least one bad spectral pixel (or that the calibration is bad on at least one spectral pixel per spatial pixel), but that it's not always the same spectral pixel that is bad.

This arose from ticket #106.

[benj]

8-pixel average over-water spectra from the same pixel on two different scan lines (raw data)

[benj]

Spectra from different pixels on the same scan line (8-pixel average, raw data)

[mggr]

Bill says it's simple to manually add bad pixels to the bad pixel table (~arsf/calibration/2007/hawk/SN300011_150207_NUC1.bad), if we can figure out a way to detect them (the hard part).

[mggr]

Given iopa's work on this, can we consider the ticket closed or do we need to do some follow up work (given it has some odd results at times)?

[benj]

I don't think we finished this - Ioannis did a lot of work on detecting bad pixels, but the results weren't entirely consistent from run to run (think that's the sensor, not Ioannis' code) and I seem to remember it either didn't get them all or marked ones that seemed OK.

Basically, since we weren't happy enough to use the bad pixel file, I don't think we can call this closed.