You have no idea what you are talking about. I spotted the problem with the data from just the record run, which is why I took the time to figure out the offset, and recalculate the wind direction and speed while the CV was stationary by using a "best guess" heading from when the CV started moving in order to tame the results for the graphs I made.The vane stalled, and that is can be easily calculated...but not by you.
My graphs sitll show a shift when the CV starts accelerating, but that's because I used a heading from too early in its acceleration, which was still off, for reasons that have been explained by many already.
I also spotted the problem when the CV accelerated, and passed through wind speed.
That "gust" you and hyevpranglostoph keep referring to in the record run, was a direct result of an error created by the CV's acceleration. If you look at the data from all the runs, you will find the same "gust" of wind while the CV accelerates every... single... time. And you will find the same huge changes in wind direction every single time the CV accelerates or decelerates through wind speed.
You will also find the only times during runs that the wind vane passes through the null are at those points.
If the cart was just barely able to beat the wind speed, that would be a problem, but since it kicked the wind's butt, it isn't.
No, it doesn't, it speaks of real world winds.I was started when the wind was 50 degrees off ddw. It does speak of bias.
You have done nothing of the sort.I have cleaned it up so all the noise is removed.