makerplane / pyEfis

Electronic Flight Information System in Python
GNU General Public License v2.0
58 stars 31 forks source link

how to use relative wind indicator? #107

Closed qubolino closed 2 years ago

qubolino commented 2 years ago

Based on the work of previous EAA Founders Innovation prize winner, Airball, we have integrated a relative wind indicator within pyEFIS. The relative wind indicator displays angle of attack on the vertical axis, and lateral wind on the horizontal axis.

i can't seem to find how to use this widget

Maker42 commented 2 years ago

I recall checking this into a branch. Was it ever pulled into main?

On Thu, Oct 14, 2021 at 1:01 AM qubolino @.***> wrote:

Based on the work of previous EAA Founders Innovation prize winner, Airball, we have integrated a relative wind indicator within pyEFIS. The relative wind indicator displays angle of attack on the vertical axis, and lateral wind on the horizontal axis.

i can't seem to find how to use this widget

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/makerplane/pyEfis/issues/107, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGB5XTPRZFXUS5L3GRZ5LR3UG2E6ZANCNFSM5F7AECSQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

birkelbach commented 2 years ago

I don't remember. There are no open Pull Requests. Where did that original quote come from? None of this is ringing a bell. It might have been done when Neil was managing the project.

Maker42 commented 2 years ago

This was something I put on a branch when we applied for the innovation award in 2018 (or was it 19)? I'm sure the text came from that application.

On Thu, Oct 14, 2021 at 8:51 AM Phil Birkelbach @.***> wrote:

I don't remember. There are no open Pull Requests. Where did that original quote come from? None of this is ringing a bell. It might have been done when Neil was managing the project.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/makerplane/pyEfis/issues/107#issuecomment-943488201, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGB5XTM32RKX6XCF6J37DF3UG336ZANCNFSM5F7AECSQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

qubolino commented 2 years ago

it’s still in the documentation of pyEfis. is there a way to get the old branch? i would revive the code

Maker42 commented 2 years ago

The code is in my fork of pyEfis (Maker42) in the branch antiLOC in the subdirectory instruments/airball

There are also things like aural warnings and stick shaker activation code in user/hooks/warnings.py

Thanks, Garrett

On Thu, Oct 14, 2021 at 9:47 PM qubolino @.***> wrote:

it’s still in the documentation of pyEfis. is there a way to get the old branch? i would revive the code

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/makerplane/pyEfis/issues/107#issuecomment-944000031, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGB5XTMBQU72LQQPLMM6C4LUG6W6BANCNFSM5F7AECSQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

qubolino commented 2 years ago

thanks, i found it and will start to integrate the widget in my branch. i somehow feel the warning logic would belong to somewhere else (fixgw plugin) since the widget shouldn't imho need all these fields to work.