-
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
SpectralFrame ignoring reference_position #436
Comments
Cadair
added a commit
to Cadair/gwcs
that referenced
this issue
Oct 12, 2023
Cadair
added a commit
to Cadair/gwcs
that referenced
this issue
Oct 12, 2023
Cadair
added a commit
to Cadair/gwcs
that referenced
this issue
Oct 12, 2023
Cadair
added a commit
to Cadair/gwcs
that referenced
this issue
Oct 12, 2023
Cadair
added a commit
to Cadair/gwcs
that referenced
this issue
Sep 26, 2024
Cadair
added a commit
to Cadair/gwcs
that referenced
this issue
Oct 17, 2024
WilliamJamieson
pushed a commit
to Cadair/gwcs
that referenced
this issue
Nov 15, 2024
WilliamJamieson
pushed a commit
to Cadair/gwcs
that referenced
this issue
Nov 20, 2024
WilliamJamieson
pushed a commit
to Cadair/gwcs
that referenced
this issue
Dec 11, 2024
I think #457 fixed this. |
To clarify - the original design was following the IVOA spec for spectral coordinates which defines a reference position. The current implementation uses astropy.coordinates.SpectralCoord. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While testing schema with defaults I encountered unexpected behavior when loading an asdf file with a saved spectral frame.
First running:
Will generate an asdf file with contents:
However, loading this file ignores
reference_position
entirely:Prints
None
I believe the cause of the error is that
reference_position
is not propagated throughFrameConverter._from_yaml_tree
:gwcs/gwcs/converters/wcs.py
Lines 46 to 69 in baef572
called from
SpectralFrameConverter
:gwcs/gwcs/converters/wcs.py
Line 135 in baef572
I looked back several versions and believe this issue might be older than 0.9 (for older versions the issue was with the old asdf types instead of converters).
The text was updated successfully, but these errors were encountered: