-
Notifications
You must be signed in to change notification settings - Fork 48
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
Celestial frame hardcoded to 2 axes? #21
Comments
@eteq I am using Also |
@nden - if what you want is the names specifically for the default representation (as opposed to the current one for a particular object, which can change at runtime), then this is probably the way to go:
Internally, that's basically what @nden @mdboom - As for
And you can see that it's actually 3D. |
I don't know if this is a bug or not, but it's come up in the work to serialize frames to/from ASDF.
If I assign a reference_frame on a CelestialFrame to a coordinate that has inherently 3 axes, it doesn't complain, but then
len(axes_names) != naxes
.The text was updated successfully, but these errors were encountered: