Ha! True!

So how about this - Taking a snapshot of the data between two easily definable points during the fastest part of each run. Because of the cubic relationship of speed to drag, this will minimize the influence of the different starting velocities. It also eliminates errors in my button pushing accuracy, especially when looking at speed. Because the garmin is only taking a datapoint every second, just looking at time might give skewed results (though the data points line up close to the center of the roads surprisingly well in each file) but I can also look at average speed over each interval.




The data from this section:


Run1: Aerohead, 53.2 sec, 36.2 mph
Run 2: Selector, 50.92 sec, 38.1 mph
Run 3: Aerohead, 52.68 sec, 37.1 mph
Run 4: Selector, 50.75 sec, 38.2 mph


Time difference: 2.1 seconds
Speed difference: 1.5 mph


t-test for time: 0.026
t-test for speed: 0.083


This data seems much more compelling to me. Might I be getting something wrong in the analysis?

---

-------------
Ed O'Malley
www.VeloVetta.com
Founder of VeloVetta Cycling Shoes
Instagram • Facebook