Skip to content
This repository has been archived by the owner on Mar 14, 2021. It is now read-only.

Trajectory visualization #70

Open
zsunberg opened this issue May 11, 2020 · 1 comment
Open

Trajectory visualization #70

zsunberg opened this issue May 11, 2020 · 1 comment

Comments

@zsunberg
Copy link

From #65:

My idea was to implement some plotting, save, load... methods on that type. However, I think that could be accomplished on the Vector also...

It would be cool to pop up a plot of a trajectory whenever a ResultsStore is returned.

However, using ResultsStore as the primary mechanism for visualization has a few problems:

  1. If someone else wants to use your fancy plotting code, they have to understand and create everything in ResultsStore, like Aircraft, etc.
  2. Visualization typically involves many visualization-specific configuration options, for example velocity_vector_color="blue". It doesn't seem appropriate to store these options in ResultsStore.

In my opinion, a better pattern is to have a visualize_trajectory (or similar) function that takes in a trajectory along with visualization options and returns a displayable object. We can talk about more details if you decide to pursue this pattern.

@zsunberg
Copy link
Author

(Also, if you do end up having a ResultsStore object, you can implement automatic plotting with something like show(io::IO, mime::MIME, rs::ResultsStore) = show(io, mime, visualize_trajectory(rs)).

@zsunberg zsunberg mentioned this issue May 12, 2020
14 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant