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

Make orbital analysis window available in tracking station #2531

Closed
DarthPointer opened this issue Apr 16, 2020 · 2 comments · Fixed by #2536
Closed

Make orbital analysis window available in tracking station #2531

DarthPointer opened this issue Apr 16, 2020 · 2 comments · Fixed by #2536
Assignees

Comments

@DarthPointer
Copy link

DarthPointer commented Apr 16, 2020

[Description by @eggrobin, this issue originally had none]
The orbit analyser is currently only available in map view.

We should make it available for the PredictedVessel, i.e., the selected vessel in the tracking station, and the active vessel in map view.

@DarthPointer
Copy link
Author

Improved level: add abillity to analysis of a user-defined orbit. For example, I wish to know which orbit to choose for a retranslator - I input desired "initial" orbit data and see if it is any stable before I launch the vessel.

@eggrobin
Copy link
Member

Improved level: add abillity to analysis of a user-defined orbit. For example, I wish to know which orbit to choose for a retranslator - I input desired "initial" orbit data and see if it is any stable before I launch the vessel.

One issue at a time. This issue is about making the orbit analyser available in the tracking station, not about every imaginable orbit analysis-related improvement.

This suggestion, much like, e.g., the idea of planning prior to launch, would require a complete rework of the UI and major changes to the underlying data model to describe trajectories without starting from the trajectory of a pre-existing vessel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants