Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: verify
-
Story Points:1
-
Epic Link:
-
Sprint:AP S20-1 (December)
-
Team:Alert Production
Description
lsst.verify.tasks.PpdbMetricTask must take a single database as input, but may compute a more fine-grained metric. Therefore, its run method takes the output data ID as a keyword argument. Create a custom runQuantum method to support this argument; it should be identical to PipelineTask.runQuantum except for the extra keyword.
Possibly blocked by
DM-21877. The issue is being able to test the new runQuantum; for this I need some kind of Gen 3 dataset, but not necessarily the production one (e.g., the Gen 2 PpdbMetricTask uses a fictitious dataset that exists only in the test suite).Maybe Jim Bosch can comment on exactly how much environment is needed to run runQuantum?