|
Run 2.2 validationStephane Plaszczynski On this page... (hide)
previously:
1. Size
cumulative cuts (except mag_i vs mag_i_cModel) measured Area (nside=2048) =304.1 deg^2 2. tracts/patches
should have 49 patches each but on the borders : ideed (in red non 49 ones) ![]() 3. density
(nside=2048)
pb on a single patch for v1 seems fixed: see https://github.com/LSSTDESC/DC2-production/issues/408 4. cosmoDC2 galaxies
using the run2.2 footprint,on cosmoDC2:
around 3 more galaxies/pixel in run2, slightly more peaked.
Note I changed the color range to have similar dynamic. So there is an excess of ~3 galaxies/pixel in run2 with the structure shown above. Not clear what it is 5. starshere is the stars density that has been injected (truth)
there is a gradient due to the milky way drection and here histograms of mag_i compared to run2 sources (good+clean+extendedness=0) ![]() some are missed around 20. They have been probably flagged as EXTENDED and might represent teh object excess, which explains the residual gradient. Is this due to blending? I don't known: here my galactic choice includes a samll blendedeness so blended stars should be removed.... 6. Photometry6.1 stars cross-match
The left tail comes from mag_i~16 and was also present in run2.1. ![]() probably saturated stars not properly flagged. testing the errorhistgram of the pull ie. \Delta(mag)/magg\_err note : I cut above mag_star_i>17 to avoid the tail. (in blue expected normal distribution). since it is know mags are not (at all) gaussian same with flux
![]() Error too low by a factor 2-3, better at high mag. 6.2 galaxies (cosmoDC2 cross-match)run2 quality cuts:
=>19.2M Cross-match with r<1 arcsec + single candidate => 14.4M (75% , slightly low maybe due to border tracts) SNR higher than in run2.1, still breach at 10 due to multiband switch. ![]()
resolutionwith SNR>10 and i<24 (waring in mmags and mag_i("true")/mag_i_cModel("rec") have been switched) ![]()
pullwith SNR>10 and i<24 ![]() that's bad. supposed to have stdev~1 : meaning errors are underestimate dby a factor ~5-7 (depending on how you count) 7. Astrometrycross-match with CosmoDC2 (SNR>1) 7.1 astrometric resolutionWhen cross-matching catalogs one can reconstruct the \Delta x,y positions in the transverse plane. The bidim is log scale, not the single dx one:
Amazing precision (better than 0.1 arcsec) , no bias. 7.2 mean PSFThis astrometric resolution is related to the PSF by (\Delta x)^2 \simeq 2 \frac{PSF^2}{SNR^2} (seeLupton's note) so that we can reconstruct the PSF map
![]() Plotting the bidim histogram wrt r=\sqrt{PSF_x^2+PSF_y^2} and normalizing the zero point to 1 ![]() one measures (half) the FWHM by drawing the horizontal line at 0.5 : we obtain 0.6 so <FWHM>=1.2 And here is what is in the catalog (drawing the vertical line at 1.2) ![]() (warning this is the "object" PSF not the model one, its name will change) mean is 1.14: very nice. 7.3 sample PSFOne can also test the estimated psf by sample. Here is how:
r_{max}=\frac{a}{\sqrt{2\beta-1}} with a= \frac{fwhm}{2\sqrt{2^{1/\beta}-1}}) which is 0.44 fwhm for \beta=2.5
![]() The mode is slightly higher (0.55) but given the various approximations (sqrt(2) factor from gaussian, poor Moffat fit at low r) this is quite fair. NEW A more accurate way to test the error is to reconstruct the pdf of the rescaled variable R=\frac{r}{a} (a is the classical Moffat normalization realted to the FWHM by a= \frac{fwhm}{2\sqrt{2^{1/\beta}-1}}). If the FWHM is properly estimated the pdf should be: f(R)=2(\beta-1)R\left(1+R^2\right)^{-\beta} 8. Summary
|