Sky Map feature plugin #1986
Merged
Sky Map feature plugin #1986
Conversation
This file contains 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
…features and message pipes to them.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a Sky Map Feature plugin, that can be used with the Star Tracker & Rotator Controller plugins to view the corresponding sky in multiple wavelengths (radio, IR, optical, UV, X-Ray, gamma).
Multiple Sky Maps are supported, including the World Wide Telescope, ESASky and Aladin Lite.
ESASky gives access to a host of astronomical data from JWST, Hubble, Gaia, Herschel and others, including images, spectra and publications:
The patch also partially addresses #1912 - in that it refactors quite a bit of code relating to available channel and feature IDs and managing message pipes. See sdrbase/availablechannelorfeature* (These can be moved in to a subdir). I've updated a few of the plugins to use this, which simplifies them a bit (more to come, but I thought I'd get any feedback). Also, it has support for renaming IDs automatically when indexes change due to channel/features being closed.