| | 1 | == Background == |
| | 2 | |
| | 3 | The IPP automatic processing of PS1/GPC1 data is currently blocked by |
| | 4 | excessive false positive rate in Magic for short exposures. The |
| | 5 | assessment by Paul Sydney as of late May was that Magic is able to |
| | 6 | detect satellite streaks, but that the effort has reached the limit of |
| | 7 | its ability to distinguish real streaks from other contaminating |
| | 8 | sources. |
| | 9 | |
| | 10 | At the time, the top candidate for the contaminating source was the |
| | 11 | correlated read noise seen especially in certain chips. This signal |
| | 12 | has the appearance of positive or negative trend in the bias for |
| | 13 | each row, with a small amount of correlation between neighboring |
| | 14 | rows. The cause of this signal has been extensively investigated by |
| | 15 | the camera group, and is apparently due to the interaction between the |
| | 16 | video signal of multiple chips readout at the same time on the same |
| | 17 | flex-print circuilt. Without going too much into the underlying |
| | 18 | electronic issues, the signal consists of a row-by-row offset in the |
| | 19 | effective bias of the row, along with a possible slow drift of that |
| | 20 | bias. The camera software currently subtracts a row-by-row constant |
| | 21 | bias to make a first-order correction for this effect. However, the |
| | 22 | (unpredictable) slope results in a slow drift for each row from this |
| | 23 | corrected value. As a result, the cells & chips which suffer most |
| | 24 | from this effect have a generally good appearance on the end of the |
| | 25 | row, trending to significal offsets for the beginning of the row. The |
| | 26 | amplitude of the effect (the 'streakies') varies from chip to chip and |
| | 27 | from cell to cell within a chip. Although the row-by-row amplitude |
| | 28 | varies and is unpredicatble, the range of tilts for a given cell |
| | 29 | appears to stay consistent over many reads and many nights. |
| | 30 | |
| | 31 | The camera group is studying possible mitigations in the hardware, |
| | 32 | including use of the pedestal signal and/or measuring a pre-scan bias |
| | 33 | level as well as a post-scan bias level. Both mitigataions will |
| | 34 | require research in the lab with the test setup, though it is |
| | 35 | reasonable to expect that a solution can be implemented without |
| | 36 | removing the camera from the telescope -- the implementation would be |
| | 37 | completely in software. However, because of the research needed (and |
| | 38 | finite available labor by the camera group) no such implementation can |
| | 39 | be expected for 2-4 months. In addition, any hardware mitigation will |
| | 40 | only allow for future improvements; none of the data taken would be |
| | 41 | addressed by this work. To this end, we have been working in two |
| | 42 | veins to implement a solution in the processing, even if such a |
| | 43 | solution would be less that the perfect solution. |
| | 44 | |
| | 45 | The two processing fixes we have been pursuing attempt in one case to |
| | 46 | correct (remove) the signal and in the other case to incorporated the |
| | 47 | effect into a more complete description of the noise model. |
| | 48 | |
| | 49 | In the first case, John Tonry has implemented a program called |
| | 50 | 'tiltystreak' which attempts to subtract the slope from each row, |
| | 51 | while at the same time attempting to avoid contamination from real |
| | 52 | signals in the data. This program takes the difference between the |
| | 53 | image and a 1 pixel shifted version, in order to avoid sensitivity to |
| | 54 | gradients in the input image. What is left is the 1st derivative of |
| | 55 | ths signal. The program attempts to determine the row-by-row slope. |
| | 56 | It attempts to reduce further the impact of real sources by performing |
| | 57 | the analysis on all 8 cells in a row at once. It has the option of |
| | 58 | only applying the fitted trend to a specified subset of cells. The |
| | 59 | IPP team has incorporated 'tiltystreak' into the IPP pipeline, and |
| | 60 | defined recipes that allow the analysis to be turned on optionally, |
| | 61 | and for the desired cells and chips to be specified for processing. |
| | 62 | |
| | 63 | The second processing mitigation we have pursued is at attempt to |
| | 64 | model more accurately the effective readnoise introduced by this |
| | 65 | structure. By default, the camera reports a single read-noise value |
| | 66 | for each cell. We have created a tool (ppNoiseMap) to measure a |
| | 67 | robust variance for collections of pixels in a grid across each cell. |
| | 68 | This measurement can be made on a number of (eg) very short dark |
| | 69 | exposures, with a single high-quality measurement generated from the |
| | 70 | median of the multiple measurements. The resulting information can be |
| | 71 | used as a more accurate model of the read noise, with the noise level |
| | 72 | modeled on the subcell level. We have added an option to the standard |
| | 73 | processing to use this noise model to determine the noise |
| | 74 | characteristics of any given science image (combining in quadrature |
| | 75 | for each pixel the read noise from the model and the contribution from |
| | 76 | the poisson noise). |
| | 77 | |
| | 78 | == Testing == |
| | 79 | |
| | 80 | We have preformed a series of tests applying each of the two |
| | 81 | mitigations to the same collection of data. The input data for this |
| | 82 | test consisted of a series of short g-band exposures for which the |
| | 83 | Magic analysis had previously given very poor results. Unfortunately, |
| | 84 | as discussed below, these tests show that neither of these two |
| | 85 | mitigations is sufficient, though it appears that they substantially |
| | 86 | improve the situation. |
| | 87 | |
| | 88 | We have run 3 tests with the g-band sequence. In the first test |
| | 89 | (noise.20090618), we only applied the resolved noise model; In the |
| | 90 | second test (tilty.20090619), we only applied the 'tiltystreak' |
| | 91 | correction. The critical measurement of success or failure is the |
| | 92 | number of streaks detected by magic. Both tests result in 1000 - 2000 |
| | 93 | streaks detected. Since there are only at most a few real streaks in |
| | 94 | these images, the vast majority of these are false positives. (HOW |
| | 95 | MUCH DID it improve relative to neither applied??). The |
| | 96 | tilty.20090619 test gave marginally better results than the |
| | 97 | noise.20090618 test, but both were clearly unacceptable. We ran a |
| | 98 | third test in which both the noise model and 'tiltystreak' were |
| | 99 | applied, in addition to a somewhat modified static mask, as discussed |
| | 100 | below. This third test (noise.20090620) was again a modest |
| | 101 | improvement over tilty.20090619, but the number of detected streaks |
| | 102 | was still too high (approaching 2000). |
| | 103 | |
| | 104 | == Detailed Inspection. == |
| | 105 | |
| | 106 | Below are a series of plots and images which illustrate the noise |
| | 107 | properties of the GPC1 images and how they are affected by the |
| | 108 | mitigations discussed above. The first series shows the evolution of |
| | 109 | the noise properties of a detrended chip from a single image in the |
| | 110 | native chip pixel coordinate system. All three plots show the |
| | 111 | log(Npixels) as a function of the predicted signal-to-noise |
| | 112 | (background subtracted). A Gaussian has been fitted to the core of |
| | 113 | this distribution, and is over-plotted in blue. If the noise model |
| | 114 | and background subtraction were perfect, the fit would result in a |
| | 115 | Gaussian with sigma 1.0 and a mean of 0.0, and the profile would |
| | 116 | follow the fitted curve all the way down. This image is a positive |
| | 117 | image of the night-time sky, so we expect pixels with high |
| | 118 | significance due to the presence of stars. |
| | 119 | |
| | 120 | The first plot shows the result for noise.20090618, which only the |
| | 121 | noise model applied. The second plot shows the result for |
| | 122 | tilty.20090619, with only tiltystreak applied. The third shows the |
| | 123 | result for noise.20090620, with both applied and the additional |
| | 124 | masking. This chip is known to have significant correlated |
| | 125 | read-noise. |
| | 126 | |
| | 127 | The set of images below show the S/N image used for the measurements |
| | 128 | above. In the first image, the correlated read noise is evident. In |
| | 129 | the second, tiltystreak has improved the correlated read noise, but |
| | 130 | has introduced an artifact on the first and last few rows of the |
| | 131 | chip. We noticed that this effect was a typical result from |
| | 132 | tiltystreak, so for the third experiment (noise.20090620), we extended |
| | 133 | the static mask by a few rows on each cell. This was an attempt to |
| | 134 | make a crude fix, with the intention of doing a better job if the |
| | 135 | impact seemed promising. Figure NN shows that this additional masking |
| | 136 | was not quite sufficient in all cases. |
| | 137 | |
| | 138 | The next set of plots and images are equivalent to the above set, but |
| | 139 | for the warped images generally corresponding to the above chips. The |
| | 140 | goal is to show that the warping does not significantly affect the |
| | 141 | noise predictions, and indeed it does not seem to have an adverse |
| | 142 | impact. |
| | 143 | |
| | 144 | The final set of plots and images shows the equivalent to the above |
| | 145 | for the difference images for this exposure. The critical difference |
| | 146 | between this set at the warped version is that the real astronomical |
| | 147 | source should be subtracted, so that the high end deviations should be |
| | 148 | removed. It is quite clear that in all cases, the amount of signal at |
| | 149 | the high end is reduced. There is also an increase in the effective |
| | 150 | noise level. Although the third experiment (noise.20090620) is the |
| | 151 | best of the three, it still has a noise level which is unexpectedly |
| | 152 | high (sigma = 1.24). |
| | 153 | |
| | 154 | Although the elevated Gaussian noie is a concern, and needs to be |
| | 155 | studies further, the observed magic-detected streaks do not seem to be |
| | 156 | the result of poorly estimated Gaussian noise. Figure NN shows the |
| | 157 | location of the detected streaks, along with small segements |
| | 158 | corresponding to the pixels responsible for the streaks. These |
| | 159 | streaks are not randomly distributed across the focal plane as would |
| | 160 | be expected if they were caused by Gaussian noise. Closer examination |
| | 161 | of the images shows that other remaining linear features are at least |
| | 162 | partially responsible for triggering magic. |
| | 163 | |
| | 164 | It seems that the static mask current in place is not sufficiently |
| | 165 | conservative. The next few images show some of the types of features |
| | 166 | which are not covered by the static mask. The first shows the |
| | 167 | vignetted edge of the focal plane. The next shows a glowing pixels |
| | 168 | around a bad cell. The third shows some hot columns. Our next step |
| | 169 | is to improve the mask by examining a set of processed science |
| | 170 | images as shown here and to manually mark poor pixels where were not |
| | 171 | caught in the intial mask creation. |
| | 172 | |
| | 173 | At this point, I conclude both 'tiltystreak' and the noise model are |
| | 174 | needed to produce generally well-characterized images, but that two |
| | 175 | possible remaining issues are contributing to the poor behavior of |
| | 176 | magic: |
| | 177 | |
| | 178 | 1) insufficiently conservative masking of some features in the camera. |
| | 179 | |
| | 180 | 2) excessive Gaussian noise in the difference images relative to the warps. |
| | 181 | |
| | 182 | The former can be addressed with ~1 day of work by the IPP team in |
| | 183 | manually reviewing the static masks. The latter needs some |
| | 184 | additional investigation, and may be due to a software error, or may |
| | 185 | simply be a result of the correlated noise properties of the pixels in |
| | 186 | this camera. |