Details
-
Type:
Story
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: pipe_tasks
-
Labels:
-
Urgent?:No
Description
While working on finishing up the doxygen->numpydoc conversion, I noticed that CalibrateTask and CharacterizeImageTask (and likely others) have redundant names in their return structs. Eli Rykoff added docstrings to the `run()` `Returns` field noting that they are "for compatibility", but those are actually there for the gen3 runQuantum output connections, while the old names are "for compatibility".
I don't think we have a way to deprecate return struct names, but we can at least make the docstrings more informative as to which are used by the pipetask infrastructure, vs. which are the old names that could be phased out in the future. I don't know if there is anything else we can or should do about these.
Attachments
Issue Links
- relates to
-
DM-38546 Refactor characterizeImageTask and calibrateTask
- In Progress
-
RFC-892 Remove fpSets from return struct of SourceDetectionTask
- Implemented
-
DM-35670 Remove gen2 support from pipe_tasks
- Done
-
DM-35939 Convert pipe_tasks to numpydoc and task topics
- Done
-
DM-15554 Convert pipe_tasks to numpydoc status
- Invalid