DM-40556: Add LATISS color terms and turn on by default in initial calibration. #470
Conversation
| config.photoCal.match.referenceSelection.magLimit.fluxField = "r_flux" | ||
| colors = config.photoCal.match.referenceSelection.colorLimits | ||
| colors["g-r"] = ColorLimit(primary="g_flux", secondary="r_flux", minimum=0.4, maximum=2.0) |
There was a problem hiding this comment.
It looks like the fit is pretty sparse at g-r of 2 should the max be 1.4? (I dont feel strongly about this)
Also, do we need an r-i color limit?
There was a problem hiding this comment.
It's sparse, but the color term is defined there and I don't want to get too thin on the ground or else some rapid processing might have trouble.
As for r-i, I went back and forth on this in my mind; I think that the g-r color range will make sure these are all well-behaved stars, but I guess we might need the other cut to make sure they don't have 🤪 i-band observations. Thoughts?
There was a problem hiding this comment.
Got it, I am in favor of rapid processing working.
I think it would be best if when calibrating r/i band data we reject stars beyond the range where that color term is defined but I imagine this will not effect latiss calibrations too much.
There was a problem hiding this comment.
The challenge is that we don't have the ability to do per-band configs. So it's all or nothing. 😬 I'm going to leave it like this; these aren't the most critical cuts (and there's outlier rejection anyway), and the "real" calibration with fgcmcal will be put into the pipeline very soon.
No description provided.