kileyay wrote:
... I think for simplicity the goal should be to come up with a ponderation law or ponderance curve, which is Mavic's pretentious term for "probability" or "histogram" or "distribution". Flo uses a description: percentage of time spent in yaw angle range. Trek uses something similar except that they bifurcated their research by probability data collected on two different IRONMAN course -- Kona and Wisconsin -- which is presented in a simple histogram with time on the y axis.
...
Trek doesn't use a simple distribution weighting formula.
Trek real engineering wrote:
Note that these simulations take into account the key subtlety that not all time at a given yaw angle is the same. For example, a 5° yaw angle can occur in a wide range of conditions — headwinds, tailwinds, fast descents, slow climbs, etc. So, it is important to also consider the apparent airspeed and bike speed for each time segment at a given yaw angle. This allows us to more appropriately analyze the bike’s true aero energy consumption and time savings at all moments during the ride.They have all the data required to do this and they indicate how non-trivial it is to properly quantify what's 'fastest'.
Mavic and Flo might have all the data but they don't (?) indicate that they use it properly, they do however give you some 'yaw angle distribution' which you seemingly want to run with...
RChung told you what to do. Just present the drag coefficient vs yaw angle. Corrected for beta-squared of course...