Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Remove afw.filter dependence from DCR model

Description

In anticipation of the afw.Filter refactor (https://rubinobs.atlassian.net/browse/DM-26259#icft=DM-26259) it has been noted that DCR is the only code making use of wavelength information stored in the filter definition. In order to simplify that transition and in light of needing to use the true filter transmission curves (https://rubinobs.atlassian.net/browse/DM-13668#icft=DM-13668) eventually, I should temporarily move wavelength information to a new location and remove dependence on afw.Filter. That new location could be in the config of the Tasks, which in the future could be used as a user override even when the true transmission curves are available.

Checklist

Lucidchart Diagrams

Issue Matrix

hide

Activity

Show:
Dan Taranu
November 3, 2020 at 5:26 PM

Just a few minor comments on github. I do wonder if effectiveWavelength/bandwidth should be a NamedTuple/dataclass - does it ever make sense to specify only one and not the other? I suppose you can revisit that when implementing the other pending tickets.

Tim Jenness
October 15, 2020 at 11:55 PM

Noting that pipe_tasks/python/lsst/pipe/tasks/dcrAssembleCoadd.py does use getFilterProperty().getLambdaMin().

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Labels

Reviewers

Dan Taranu

Story Points

RubinTeam

Components

Sprint

None

Parent

Checklist

Created September 4, 2020 at 12:01 AM
Updated December 8, 2020 at 4:36 AM
Resolved November 4, 2020 at 5:14 PM