Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: pipe_base
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Team:Alert Production
Description
Per RFC-352, all Tasks (modulo approved exceptions; see the RFC for details) are expected to provide a run method as their primary point of entry, and may also provide runDataRef for operating on dataRefs. Please update the documentation in pipe_base to explain this requirement (and the procedure for obtaining an exemption).
Attachments
Issue Links
- is triggered by
-
RFC-352 Standardize the point of entry for all Tasks
- Adopted
Hey Kian-Tat Lim, could you please give https://github.com/lsst/pipe_base/pull/113 a quick review?
I'm unsure of how much of this documentation remains valid in the world of PipelineTask, and I note that this whole page has a big “needs to be edited” disclaimer on the top, so I'm not keen to spend significant effort on this. However, the existing text was causing confusion and encouraging the rule as per RFC-352, so I think these minimal edits are worthwhile.