Details
-
Type:
Story
-
Status: Won't Fix
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: afw, meas_deblender, pipe_tasks
-
Labels:None
-
Story Points:8
-
Epic Link:
-
Sprint:Science Pipelines DM-W15-4
-
Team:Data Release Production
Description
We have a new multi-band processing scheme for coadds on the HSC side, encompassing changes in afw, meas_deblender, and pipe_tasks. These should be transferred to the LSST side, with RFCs for any backwards incompatible changes.
Changes to the Footprint classes may only be temporary, as we plan to refactor those classes soon anyway, but they're still worth doing now to support the higher-level changes.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Team | Princeton [ 10301 ] |
| Rank | Ranked higher |
| Story Points | 2 | 8 |
| Assignee | Jim Bosch [ jbosch ] | Paul Price [ price ] |
| Rank | Ranked higher |
| Watchers | Dustin Lang, Jim Bosch, Robert Lupton [ Dustin Lang, Jim Bosch, Robert Lupton ] | Jim Bosch, Robert Lupton [ Jim Bosch, Robert Lupton ] |
| Description |
We've recently made a number of changes to the deblender and persistence of its outputs on the HSC side. This includes both DM-340 and DM-407 (see also Tract #3168). We should clean this up and push it back to the LSST repositories. |
We have a new multi-band processing scheme for coadds on the HSC side, encompassing changes in afw, meas_deblender, and pipe_tasks. These should be transferred to the LSST side, with RFCs for any backwards incompatible changes. Changes to the Footprint classes may only be temporary, as we plan to refactor those classes soon anyway, but they're still worth doing now to support the higher-level changes. |
| Summary | transfer recent deblender fixes from HSC | transfer multiband processing changes from HSC |
| Sprint | Science Pipelines DM-W15-4 [ 120 ] |
| Rank | Ranked higher |
| Resolution | Done [ 10000 ] | |
| Status | To Do [ 10001 ] | Won't Fix [ 10405 ] |
I'm closing this as Won't Fix, because I think we really need to split this up and increase the story points to represent the real work involved (I'll link those issues here once they're all created). At the very least, transferring this code will require RFCs which may generate changes to the APIs, and we need to capture the effort there involved as well.