Alex Simmons said:Well, wind kinda sucks for testing.
The issues are twofold:
1) Your CdA is constantly changing because yaw is constantly changing. Using Aerolab, you get a yaw-averaged CdA. It's ok, I guess, but not quite a wind tunnel.
2) Wind mucks-up virtual elevation completely anyway.
I second Alex's reply. There's not much I can do with wind right now in Aerolab.
Here's a rundown of the numerical approaches I've taken so far using VE with wind:
1) Ignore it.
Bad idea. The error on CdA is almost boundless. In fact, you can get any CdA you want, from -0.500 to +1.500 if you ignore wind. Might be a good approach if you like to brag to friends. :-)
2) Use iAero/iBike.
iAero does tend to "clean up" some Aerolab files, but not ever as much as I'd like. If your out-and-back is straight and almost perfectly aligned with the wind direction, you might get ok results. But how common is that?
The iAero has no ability to untangle yaw and airspeed. Yes, the front-facing port is yaw-sensitive, but it's also airspeed sensitive. No way to reliably untangle those yet.
3) Use a numerical "zippering" approach for out-and-backs.
Pretend that at every point in an out-and-back, the wind term is (CdA*0.5*RHO*(v-w_i)^2) going out and (CdA*0.5*RHO*(v+w_i)^2) coming back. w_i is the wind at point i.
This way, you could theoretically start from the turn-around point and "zipper" the "out" ve curve with the "back" ve curve, one point at a time. I've attached the out and back file.
Unfortunately, I've not had a lot of luck with this yet. 🙁
4) Make a wind sensor that's yaw-sensitive.
Points 1-3 have led me to what I think is the inevitable conclusion: a new sensor needs to be built. Alex has pointed it out, above.
The sensor will be ANT+ aware, and provide yaw direction, and airspeed. A printed circuit board is presently under construction.
That's it -- those are the options.
Cheers,
Andy
andyfroncioni.com