Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:4
-
Epic Link:
-
Sprint:DRP S19-6b
-
Team:Data Release Production
Description
The new jointcal and obs_lsst functionality was great this past week. It was like you built us a bunch of toys and then let me be the first to play with them. (Will show you tomorrow). Only thing I've noticed is missing:
Three configs for jointcal or processCcd reruns:
Declination diff all looks very different as it should for 3 reruns:
https://lsst-web.ncsa.illinois.edu/~yusra/QA_DC2/processCcd/i/tract-3633/visit-204706/plot-v204706-matches_dec-psfMagHist.png
https://lsst-web.ncsa.illinois.edu/~yusra/QA_DC2/jointcal_default/i/tract-3633/visit-204706/plot-v204706-matches_dec-psfMagHist.png
https://lsst-web.ncsa.illinois.edu/~yusra/QA_DC2/jointcal_simple_3_1mas/i/tract-3633/visit-204706/plot-v204706-matches_dec-psfMagHist.png
But distance all looks the same.
From same runs of visit analysis (behold timestamps). Repos are clean.
https://lsst-web.ncsa.illinois.edu/~yusra/QA_DC2/processCcd/i/tract-3633/visit-204706/plot-v204706-matches_distance-psfMagHist.png
https://lsst-web.ncsa.illinois.edu/~yusra/QA_DC2/jointcal_default/i/tract-3633/visit-204706/plot-v204706-matches_distance-psfMagHist.png
https://lsst-web.ncsa.illinois.edu/~yusra/QA_DC2/jointcal_simple_3_1mas/i/tract-3633/visit-204706/plot-v204706-matches_distance-psfMagHist.png
I don't really know how this would be possible, except that they're not using jointcal.
Another great observation from Yusra AlSayyad! I’ll have to dig a bit deeper to confirm, but a cursory glance leads me to believe this “distance” is just taken from the persisted match catalog from the processCcd.py stage...i.e. your intuition was bang on. It may be best just to get rid of these plots altogether (clearly, I’ve never paid them much heed...)