Changeset 37897 for trunk/doc/release.2015/ps1.analysis/analysis.tex
- Timestamp:
- Feb 5, 2015, 10:34:35 AM (11 years ago)
- File:
-
- 1 edited
-
trunk/doc/release.2015/ps1.analysis/analysis.tex (modified) (12 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/release.2015/ps1.analysis/analysis.tex
r37893 r37897 282 282 \begin{itemize} 283 283 \item {\bf Image preparation} Load data, characterize the image 284 background, load or construct noise and mask images.284 background, load or construct variance and mask images. 285 285 286 286 \item {\bf Initial object detection} Smooth, find peaks, measure basic … … 301 301 302 302 \item {\bf Output} Write out objects in selected format, write out 303 difference image, noise image, etc, as selected.303 difference image, variance image, etc, as selected. 304 304 \end{itemize} 305 305 … … 317 317 defining which pixels are valid and which should be ignored. The 318 318 signal and variance images are represented internally as 32-bit 319 floating point values. The noise and mask images may either319 floating point values. The variance and mask images may either 320 320 be provided by the user, or they may be automatically generated from 321 321 the input image, based on configuration-defined values for the image 322 322 gain, read-noise, saturation, and so forth. For the function-call 323 323 form of the program, the flux image is provided in the API, and 324 references to the mask and noise are provided in the configuration325 information. As in the stand-alone C-program, the noise and mask may324 references to the mask and variance are provided in the configuration 325 information. As in the stand-alone C-program, the variance and mask may 326 326 be constructed automatically by PSPhot. 327 328 \note{describe the use of the covariance image}329 \note{describe the difference between 'bad' and 'suspect' pixels}330 327 331 328 The mask is represented as 16-bit integer image in which a value of 0 … … 347 344 \code{XMIN}, \code{XMAX}, \code{YMIN}, \code{YMAX}. 348 345 349 The noise image, if not supplied is constructed by default from the 346 PSPhot (and other IPP) functions understand two types of masked 347 pixels: ``bad'' and ``suspect''. Bad pixels are those which should 348 not be used in any operations, while suspect pixels are those for 349 which the reported signal may be contaminated or biased, but may be 350 useable in some contexts. For example, a pixel with poor charge 351 transfer efficiency is likely to be too untrustworthy to use in any 352 circumstance, while a pixel in which persistence ghosts have been 353 subtracted might be useful for detection or even analysis of brighter 354 sources. \note{can I identify which functions respect which sets of masks} 355 356 The variance image, if not supplied is constructed by default from the 350 357 flux image using the configuration supplied values of \code{GAIN} and 351 358 \code{READ\_NOISE} to calculate the appropriate Poisson statistics for … … 355 362 if the input flux image is the result of an image stack with a 356 363 variable number of input measurements per pixel (due to masking and 357 dithering), it will be necessary to supply a noise image which 358 accurately represents the noise as a function of position in the 364 dithering), the variance cannot be calculated from the signal image 365 alone. It is necessary in such a case to supply a variance image which 366 accurately represents the variance as a function of position in the 359 367 image. 368 369 Some image processing steps introduce cross-correlation between pixel 370 fluxes. An obvious case is smoothing, but geometric transformations 371 which redistibute fractional flux between neighboring pixels also 372 introduces cross-correlations. In the noise model, it is necessary to 373 track the impact of the cross correlations on the per-pixel variance. 374 In the general case, this would require a complete covariance image, 375 consisting of the set of cross-correlated pixels for each image pixel. 376 Since a typical smoothing or warping operation may introduce 377 correlation between 25 - 100 neighboring pixels, the size of such a 378 covariance image is prohibitive. In practice, however, there are two 379 extreme cases which generally are relevant. \note{talk about the 380 covar matrix for a PSF} 381 382 \subsection{Background (Sky) Model} 360 383 361 384 \subsection{Initial Object Detection} … … 635 658 make a good guess for the centroid and shape parameters for the PSF 636 659 models. \note{still true? In order to minimize the impact of close 637 neighbors, the noise values used in the fit are enhanced by a660 neighbors, the variance values used in the fit are enhanced by a 638 661 fraction of the deviation of the particular pixel value from the 639 662 model guess.} Any objects which fail to converge in the fit are 640 663 flagged as invalid. 641 664 642 \note{does the noise enhancement introduce too much bias?}665 \note{does the variance enhancement introduce too much bias?} 643 666 644 667 \note{discuss the convergence criteria, model parameter guesses} … … 813 836 process modifies the image pixels (removing the fitted flux, though 814 837 not the locally fitted background) but does not modify the mask or the 815 noise images. The signal-to-noise ratio in the image after838 variance images. The signal-to-noise ratio in the image after 816 839 subtraction represents the significance of the remaining flux. If the 817 840 subtractions are sufficiently accurate models of the PSF flux … … 819 842 significance. In practice the cores of bright stars are poorly 820 843 represented and may have larger residual significance. \note{in future 821 work, we may choose to enhance the noise to minimize detection of844 work, we may choose to enhance the variance to minimize detection of 822 845 objects in the residuals of brighter objects}. 823 846 … … 880 903 the image as is done for the successful PSF model fits. Of course, 881 904 the background flux is retained, with the result that only the object 882 is subtracted from the image. Again, the noise image is (currently)905 is subtracted from the image. Again, the variance image is (currently) 883 906 not modified. 884 907 … … 897 920 this stage, the new peaks are detected on the image with the bright 898 921 objects subtracted. In this pass, the peak detection process uses the 899 noise image to test the validity of the individual peaks. All peaks922 variance image to test the validity of the individual peaks. All peaks 900 923 with a significance greater than a user-defined minimum threshold are 901 924 accepted as objects of potential interest. … … 943 966 \note{In the ideal case, if we were only interested in detecting PSFs, 944 967 and we had a good model for the PSF, we could optimally find the 945 sources by smoothing the image and the noise image with the PSF model.968 sources by smoothing the image and the variance image with the PSF model. 946 969 \em write out the description of Nick's optimal PSF finding}. 947 970 … … 1075 1098 \subsection{Difference Images} 1076 1099 1077 The noise map for a difference image must be generated from the two1100 The variance map for a difference image must be generated from the two 1078 1101 images use to construct the difference. Otherwise, the low sky level 1079 will automatically result in inconsistent interpretation of the noise.1102 will automatically result in inconsistent interpretation of the variance. 1080 1103 1081 1104 For a difference image, both positive and negative objects will be
Note:
See TracChangeset
for help on using the changeset viewer.
