Fix Version/s: None
Currently validate_drp uses some manual crude addition of calibration information and constructs new schemas to store this information. This is essentially what TransformTask is meant for. Using this would simplify the code, make it less fragile, and ideally eventually integrate more transparently with future calibration improvements or redefinitions of how zeropoints are tracked..
1. Learn how to use TransformTask. Note
DM-4948 is the doc task for this.
2. Adapt the code.
3. Verify unchanged results on existing validation_data_decam and validation_data_cfht.
- is blocked by
DM-4948 Please improve the documentation for TransformTask and derivatives
As far as I can tell, this is not still relevant. Closing as invalid. Please comment if we should still be doing something about this.
Jim Bosch Is this ticket to use a TransformTask for validate_drp still relevant?