Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: jointcal
-
Labels:None
-
Story Points:15
-
Epic Link:
-
Sprint:AP S21-3 (February)
-
Team:Alert Production
-
Urgent?:No
Description
The approach I took to writing the gen3 jointcal pipetask in DM-19470 won't work. See this discussion on Slack for the details. This ticket will build on the testing framework and data input cleanups developed on that ticket, and will implement VisitSummary and VisitCatalog Connections for the input data, which should solve the "what visits to read" question once and for all.
Attachments
Issue Links
- is blocked by
-
DM-19470 Create jointcal PipelineTask (version 0: tests)
- Done
-
DM-28756 Create VisitSummary tables for testdata_jointcal
- Done
- is triggering
-
DM-27843 add anyFilterMapsToThis support to ReferenceObjectLoader
- Done
-
DM-28863 Add metrics output and tests to gen3 jointcal
- Done
-
DM-29049 jointcal gen3 fixes for running RC2
- Done
-
DM-29535 Create gen3 cfht testdata_jointcal repos
- Done
-
DM-28991 Fix gen3 jointcal refcat area
- Won't Fix
-
DM-32584 Create gen3 decam testdata_jointcal repo
- Won't Fix
-
DM-29012 Create obs_subaru gen3 jointcal pipeline file
- Invalid
- mitigates
-
DM-28200 Reduce jointcal info log verbosity
- Done
- relates to
-
DM-28583 Update fitsExposure formatter to fill in filterLabel from dataId
- Done
Jenkins: https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/33606/pipeline