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

Winds aloft #46

Open
hr0nix opened this issue Feb 2, 2014 · 3 comments
Open

Winds aloft #46

hr0nix opened this issue Feb 2, 2014 · 3 comments

Comments

@hr0nix
Copy link
Owner

hr0nix commented Feb 2, 2014

Different winds for different altitudes.

@ilyapoz
Copy link
Collaborator

ilyapoz commented Feb 2, 2014

👍 nice idea.

One of big questions here is: how will we define the reach set in this case?

  • Full information reach set: reachable points based on the whole information
    • ➖ Harder to implement
    • ➖ Doesn't fully correspond to reality: we only know the wind at current altitude and on ground (by looking at the windsock)
    • ➕ Very interesting to see it
  • Reach set based on known wind at altitude
    • ➕ Corresponds to reality: we think that we are reaching the LZ, but suddenly we have a strong wind at some altitude and we can't reach it anymore (who would have known! 😕)
    • ➕ Nothing new to implement
    • ➖ Reach set evolution will be a bit weirder: it will jump a bit unpredictably when the wind changes
    • ➖ Don't know how to account for wind at ground level information.

@ilyapoz
Copy link
Collaborator

ilyapoz commented Feb 2, 2014

Let's say we don't load the real data. How would we design the interface in this case?

@ilyapoz
Copy link
Collaborator

ilyapoz commented Feb 3, 2014

I now have a view on reorganizing of the interface. Briefly: remove the legend to a tutor, create separate sections on the right for winds, pattern settings etc.

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

No branches or pull requests

2 participants