Repository navigation
Make AstrometricFrame behave like other coordinate frames. #4941
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
Merged
Merged
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
5c9d7c3
Change to a generic astrometric frame
alexrudy 71b2d8d
Moving frame attributes around.
alexrudy 2581b16
fixing pep8 errors.
alexrudy c24ec8d
Improvements to AstrometricFrame documentation
alexrudy 1243189
Fix one last 'icrs' reference
alexrudy 5ec5d33
Fix PEP8 errors in AstrometricFrame docstring
alexrudy 76e6d3f
Add additional PR number to CHANGES [skip ci]
alexrudy 3c5caab
Fix inheritance order of AstrometricFrame
alexrudy b0b752b
Fix doctests.
alexrudy 208bc26
Update CHANGES.rst [skip ci]
alexrudy b634141
some minor pep8-ish fixes
eteq 9346bf9
change from dra/ddec to lon/lat
eteq 3742e79
change back to astrometric frame names including their base type
eteq 51ec04d
documentation updates for astrometric frames
eteq 491e02c
add check for unrealized origin frame and related test
eteq 8efaaf0
Merge pull request #1 from eteq/astrometric-magic
alexrudy 29f8db0
Fix multi-parent transforms in Astrometric
alexrudy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Can this ever happen, given that
AstrometricFrameis always a subclass ofBaseCoordinateFrame?Uh oh!
There was an error while loading. Please reload this page.
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, because BaseCoordinateFrame doesn't implement
__new__, this is always triggered right now. If another frame were to implement a custom__new__, this would be skipped by the parent class when traversing the class hierarchy ifAstrometricFramecame before theframeclsabove, which ideally it would, but that breaks something about ordered descriptor that I don't understand (but maybe @eteq could fix?)Regardless, right now, this is required to prevent this
__new__method from breaking should an descendant implement__new__in the future. When this happens, if we didn't put in this statement, arguments would never get passed to a subclass__new__, since we'd need to assume we are callingobject.__new__. As this is kind of a subtle bug when that happens, I would advocate for leaving this check in now.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.
OK, yes, I was sloppy in looking through the chain. Given that
objectis one up as far as__new__is concerned, it definitely makes sense to have this in.