-
Notifications
You must be signed in to change notification settings - Fork 31
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
True Wind Direction (based on AWA and headingTrue) is wrong, should be removed #75
Comments
Please explain. |
Scott so sorry for being unclear, and a bit rude. It cannot be done by definition, because you lack boat and wind speed in the equation. The script trueWind.js shows the correct calculation, and that one works. If you follow that script, and especially how the angle in there is calculated, you'll see what I mean. |
Boat and wind speed are included in the calculation. |
Oh. There are two calculations for this and maybe some confusion about the definition. |
Not in this one https://github.com/SignalK/signalk-derived-data/blob/master/calcs/windDirection.js |
Just had a look: I see it as marcobergmann, directionTrue and directionMagnetic are wrong if calculated via the implementation in windDirection.js, it lacks speedThroughWater. To wrap it up: In my opinion only one implementation for directionTrue should be provided and furthermore windDirection.js contains a calculation that is wrong. windDirection.js should be deleted. (I use trueWind.js since > a year and it gives reliable results) |
It also depends on leeway. Speed sensor only measures speed over water in the direction of heading. TrueWindVector + SpeedOverWaterVector = ApparentWindVector To figure out SpeedOverWaterVector you need to know heading vector, speed from (speed sensor) and leeway leeway doesn't get measured by boat sensors. It has to be estimated and there is an empirical formula for leeway Leeway = -1 * k * Heel / BSP^2 |
True Wind Direction cannot possibly be calculated from AWA and headingTrue. The idea is wrong, the calculation is wrong. It should be removed from the code and from the Derived Data Plugin Config.
The text was updated successfully, but these errors were encountered: