IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Changes between Initial Version and Version 1 of PS1_GPC1_Magic_And_Short_Exposures


Ignore:
Timestamp:
Jun 21, 2009, 4:59:09 PM (17 years ago)
Author:
eugene
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PS1_GPC1_Magic_And_Short_Exposures

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