| 5 | | Three different patterns that can arise from burntool. The first has a bright streak that burntool should have removed. The second has the burn from a star on a previous image oversubtracted either due to a bad fit or the images being processed in the wrong order. The third shows an oversubtraction of the burn. |
| | 5 | "Burns" are the result of bright sources landing on the detector in the image under consideration, or a recent image, causing trails along the detector columns. It seems that lots of excess charge upsets the pixels. When this charge is clocked out, some of it remains, causing a burn trail that goes upward (away from the amplifier) in the image with a bright source. Then in subsequent exposures, the angry pixels slowly leak charge, causing burn trails that go downward (towards the amplifier). |
| | 6 | |
| | 7 | 'burntool' has been developed by the Camera group (specifically, John Tonry) to attempt to remedy these artifacts in software. Since it requires operation on images in the order in which they were observed, it must be run on data in the IPP after registration but before the chip stage is executed (output is named *.burn.fits, set rawImfile.user_1 = 1.0, and then turn on USE.DEBURNED.IMAGE in the PPIMAGE recipe). Efforts are underway in the Camera group to fix these artifacts in hardware. |
| | 8 | |
| | 9 | Three different artifact patterns can arise from burntool. The first has a bright streak that burntool should have removed but didn't. The second has the burn from a star on a previous image oversubtracted either due to a bad fit or the images being processed in the wrong order. The third shows an oversubtraction of the burn. |