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
Fix a bug in NDData constructor where WCS was not validated correctly #11985
Conversation
536683f
to
6c2f2ea
Compare
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.
Thanks, this fix looks fine
100 failures... |
Ah, looks like the failures may be related to #11727. Essentially the issue is that the WCS cannot currently be |
6c2f2ea
to
effb97f
Compare
I have fixed the test fails by allowing ccddata to accept None when passed to the setter. |
@mwcraig Can we merge this? |
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.
@Cadair -- this is ready to merge
…was not validated correctly
…was not validated correctly
@Cadair I think you have broken the sunpy tests with this: https://app.circleci.com/pipelines/github/sunpy/sunpy/14750/workflows/ef2a05ba-d904-4c63-96ff-c262e937afd4/jobs/71735 - not sure whether there's something we need to change in sunpy or astropy? |
I suspect that's a sunpy bug (we override the property but not the setter). |
…985-on-v4.3.x Backport PR #11985 on branch v4.3.x (Fix a bug in NDData constructor where WCS was not validated correctly)
…985-on-v4.0.x Backport PR #11985 on branch v4.0.x (Fix a bug in NDData constructor where WCS was not validated correctly)
We were not running the input WCS through the property setter which means it wasn't getting up-converted to a High Level WCS object which then would later break when that assumption was relied upon.