Fix Version/s: None
At present validate_drp has a lot of duplication between the various yaml files, including nearly identical twins for normal and quick examples. Much of the duplication could be eliminated by making the validation code a normal task and saving the configuration parameters as a normal config. Advantages include:
- Properties that appear may be camera-specific, such as brightSnr, medianAstromscatterRef and medianPhotoscatterRef, can be set in the usual way: using a config override in the appropriate obs_ package. That said, in many cases reasonable defaults exist based on the quality of our algorithms. The current values used for CFHT and DECam are identical; if those are good values then no overrides are needed for those cameras.
- It uses our standard for processing data, including standard methods of specifying data and configuration.
Yes, absolutely. Making validateDrp a task is