Use more robust coordinates machinery in get_skycoord
- Dominant language
- Python
- Stars
- 225
- Forks
- 121
- Avg merge
- 28m
- Merged PRs (30d)
- 1
Description
This is basically a move of this comment: https://github.com/astropy/astroplan/issues/382#issuecomment-441892022, which turns out to be separate from the "real" issue #382 . @adrn pointed out there that the `get_skycoord` function could probably be updated to use some of the astropy machinery that concatenates sky coordinates in a way that's probably more likely to remain stable/without warnings since it would defer more of the "hard work" to astropy itself.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the get_skycoord function and read the discussion moved from issue #382, especially the referenced comment. Investigate the Astropy machinery for concatenating sky coordinates and compare it with the current approach. Done means get_skycoord uses the more stable Astropy path without introducing warnings or changing expected coordinate behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100