New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DM-27168: Phase out use of FilterProperty #428
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused by your comment about dcrAssembleCoadd.py
. DM-26615 has already been merged and is ancestral to this branch; are you still seeing residual use despite that?
@@ -144,7 +144,7 @@ def getShortFilterName(name): | |||
# I'm not sure if this is the way this is supposed to be implemented, but it seems to work, | |||
# and its the only way I could get it to work. | |||
try: | |||
return afwImage.Filter(name).getFilterProperty().getName() | |||
return afwImage.Filter(name).getName() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this should be getCanonicalName()
; compare the definition of getFilterProperty with the definition of getCanonicalName.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In fact, looking at the function definition, I'm pretty sure this could be entirely removed. Maybe remove the existing comment and mark removing the function as TODO for DM-27170?
The commit comment was fine before I rebased. I've removed it as you mention it's inaccurate now. |
1ce283a
to
b847eb5
Compare
b847eb5
to
cdd9f35
Compare
End usage of FilterProperty, as per RFC-730.
Usage in dcrAssembleCoadd.py left as it is dealt with by DM-26615.