Details
-
Type:
Story
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: verify
-
Story Points:4
-
Epic Link:
-
Sprint:AP S21-3 (February)
-
Team:Alert Production
-
Urgent?:No
Description
The existing upload script (dispatch_verify.py) assumes that metric values have been persisted in Job objects. Once we can store metric values in Gen 3 repositories, we need to be able to read those as part of the upload process.
Story point value assumes that using Gen 3 Butler inside something that's not a PipelineTask is difficult.
Attachments
Issue Links
- blocks
-
DM-21888 Stand up Gen3 version of ap_verify HiTS (2015) CI test
- To Do
- is blocked by
-
DM-21875 Add StorageClass and Formatter support necessary to persist lsst.verify.Measurement in Gen3 repos
- Done
- relates to
-
DM-21885 Convert concrete MetricTasks to PipelineTasks
- Done
-
DM-25507 Tooling to report to SQuaSH
- Done
-
DM-12549 ap_pipe must call AssociationTask in a reproducible order
- To Do
-
DM-24262 Run HSC AP processing in CI using Gen 3
- Done
- mentioned in
-
Page Loading...
I assumed the script in metric-pipeline-tasks was a workaround for this issue. Or do you plan for the Job class to always be required as a sort of intermediate step?