-
Notifications
You must be signed in to change notification settings - Fork 167
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
Remove soon-to-be-deprecated usage of AsdfFile.open #2814
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.
This looks good. The clarifying variable names in model_base.py
are good too.
Thanks!
260dd2b
to
41c4a3d
Compare
Seems like the Jenkins job is hung... |
Still failing. Is it just me or is there a problem with Jenkins? |
Yes, Jenkins was hosed. Matt hit the shiny red button to restart. I've restarted (I think the Jenkins CI test by closing and reopening this PR). @stscieisenhamer & @nden, any idea what is going on with this failure in the TravisCI build? https://travis-ci.org/spacetelescope/jwst/jobs/452031031#L1496 Does a |
The |
I think the problem is files in I suspect that a simple search and replace of these for the corresponding tag name in |
I see. Does this mean that all old data like this will now fail to to have a functioning GWCS object without it having to be rebuilt using a current version of |
@jdavies-st the short answer is yes. Of course, you could grab an older version of @nden we made this change expecting that there would be no residual uses of ASDF WCS, but maybe we should go with a deprecation period instead. We're in a tricky place here because if we don't try to be diligent about cleaning these things up, ASDF is going to become a giant crapball of spaghetti code that mostly supports legacy uses. We should handle this better going forward, but I don't think we were expecting this particular change to have any impact. Unfortunately, making this change has exposed some other issues that will need to be addressed (see #2849). Considering the hour, I think the best course of action is probably to sit down with a tall scotch and forget all about of this for a little while. |
hold it...wait...i'm in the wrong conversations.... |
Is it (theoretically) possible to edit the ASDF extension to change the tags, as an alternative to rebuilding the extension? |
@philhodge if I understand correctly, it's probably possible in theory, but I'm not sure we want to support this for the general case since it will probably be fairly difficult to maintain. It would probably be easier just to write a one-off script to convert files like these, but at that point it might just be easier to regenerate them. |
@drdavella, can you rebase this to |
41c4a3d
to
b9152f6
Compare
Looks like we're good now! |
Thanks @drdavella! |
This will take effect once asdf-format/asdf#579 is merged, but there's no harm in making this change now.
This closes #2795.