Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Validation
-
Labels:None
-
Story Points:0.5
-
Team:Alert Production
Description
validate_drp will test more of our code if it uses default config parameters wherever possible. To that effect I would like to ask you to eliminate all config overrides that are not essential and document the reasons for the remaining overrides.
For DECam there are no overrides that are different than the defaults, so the file can simply be emptied (for now).
For CFHT there are many overrides that are different, and an important question is whether the overrides in this package are better for CFHT data than the overrides in obs_cfht; if so, please move them to obs_cfht.
As a heads up: the default star selector is changing from "secondMoment" to "objectSize" in DM-4692 and I hope to allow that in validate_drp, since it works better and is better supported.
Sorry for the incorrect component, but validate_drp is not yet a supported component in JIRA (see DM-5004)
I just pushed a change to obs_cfht master that tweaks a few params for improved performance. I carefully checked the output of validate_drp before doing this and it looks fine (though I encourage you to verify this). So at this point CFHT needs no config overrides on master.
I think the DECam overrides were already unnecessary, but again, I encourage you to verify that.
I suggest leaving a default override file around if you plan to keep offering the examples/runX scripts, to make it easier for users to try out the effects of temporary config overrides.
In my opinion this is a fairly important change, because it makes the results easier to understand.