Open
Conversation
This file contains hidden or 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
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.
Addresses #17, #18, #32, #69 (sort of, we can tweak what's on the tool-tip specifically if needs be), #295
The previous branch and PR #111 is a) out of date, b) calculates orbits incorrectly, c) only handles BKEP input, and d) is just ugly. Made a whole new branch and PR now that creates much nicer and wider scope visualisation tools. Features include:
This all utilises only Plotly and Dash to create an interactive way of visualising plots, much nicer than Matplot itself. Code is (I think) vectorised as far as possible, and up to ~1000 orbits can be plotted before performance starts taking a hit (but at 1000 orbits are you really getting any info?)