Skip to content
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

Handle non-ICRS coordinates in query functions #3164

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

snbianco
Copy link
Contributor

@snbianco snbianco commented Dec 23, 2024

This PR handles coordinates passed into query functions that are not in the ICRS frame. If it is found that the given coordinates are not in ICRS, they are transformed.

Copy link

codecov bot commented Dec 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.70%. Comparing base (311197b) to head (76610a1).
Report is 19 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3164   +/-   ##
=======================================
  Coverage   68.69%   68.70%           
=======================================
  Files         231      231           
  Lines       19214    19220    +6     
=======================================
+ Hits        13199    13205    +6     
  Misses       6015     6015           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@snbianco snbianco force-pushed the ASB-29990-coord-frame branch from 4dc257f to f2bd777 Compare January 24, 2025 22:01
@snbianco snbianco marked this pull request as ready for review January 24, 2025 22:19
@snbianco snbianco force-pushed the ASB-29990-coord-frame branch from 4baa044 to 50648fd Compare January 24, 2025 22:25
@bsipocz bsipocz added the mast label Feb 15, 2025
@bsipocz bsipocz added this to the v0.4.10 milestone Feb 15, 2025
Copy link
Member

@bsipocz bsipocz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if this should live in the commons function, or you could use what we already have for simbad (_parse_coordinate_and_convert_to_icrs)?
(or also move the simbad one to commons? cc @ManonMarchand )

_parse_coordinate_and_convert_to_icrs

@@ -121,6 +121,32 @@ def resolve_object(objectname):
return coordinates


def parse_coordinates(coordinates):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if this should be a kwarg argument for commons.parse_coordinates instead? e.g. to convert right at the end before returning the current output

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean a parameter like return_frame or something to that effect that you could pass in a value like 'ICRS' and get the coordinate back in whatever frame was given?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just made this change! I added a return_frame parameter to utils.commons.parse_coordinates that defaults to None. If it is provided and the coordinates are not already in that frame, it will attempt to transform them. If the transformation fails, a warning is issued and the coordinates are returned as is, without the transformation.

@ManonMarchand
Copy link
Member

Oh that methods only parses coordinates if I detect that they are written as a sim-script string. This is an old way of writing coordinates that only existed in the former Simbad interface (hence this is in Simbad's utils and not in commons).
In the other cases I use parse_coordinates from commons and then convert the SkyCoord it returns to icrs 🙂

@snbianco snbianco force-pushed the ASB-29990-coord-frame branch from f83c591 to 0746ddf Compare February 21, 2025 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants