RojoRacing
Donut Powered Wise-guy
Dispite my sadist nature I'm not cruel enough to feed them false hope. I find it much more humane to crush dreams with raw truth . I really think today's ride is going to put me in the hurt zone because they are going to drop me on the long climb and the DH is so twisty I'll probably loose a little more time there ass well. I'm going to have to push the rollers and flats in the second half to catch back up.
I think finding a flat 2-3 mile stretch of road and setting up two strava segments, one in each direction would make for a good testing zone. It'll have real world influences like wind so I could determine a set avg speed and try and hold it during each run. If there's a head wind one way and a tail wind the other I'll pick one speed I can maintain both ways to show the aero benefit of the V in both scenarios. Like any lab test I'd have to collect dozens of samples to discredit any outliers and determine an average. I think just park my truck and tools on one end and ride the DF out and back twice then swap pedals and do the same on the V. I'd have to get in at least 10 out and backs on both bike to find a true avg wattage to compare. I'd also have to keep swapping bikes every lap or so just in case the wind speed or direction changes during the length of the test.
This type of test would give you the difference in wattage needed to avg say 20 mph with a headwind or with a tailwind for each style bike. You'd also be able to compare the two bikes to one another during each direction. Because the test course will be set as a strava segment I can roll into it already at the avg speed and the computer will start and finish collecting the data for each run on its own. Then if I set one of my data fields to display avg lap speed I should have to problem hitting an avg to the tenth of a mph.
I could probably do the same test on a climb but it would need to be steady and done on its own in similar fashion. I can think of one place that could work for the hill test maybe.
I think finding a flat 2-3 mile stretch of road and setting up two strava segments, one in each direction would make for a good testing zone. It'll have real world influences like wind so I could determine a set avg speed and try and hold it during each run. If there's a head wind one way and a tail wind the other I'll pick one speed I can maintain both ways to show the aero benefit of the V in both scenarios. Like any lab test I'd have to collect dozens of samples to discredit any outliers and determine an average. I think just park my truck and tools on one end and ride the DF out and back twice then swap pedals and do the same on the V. I'd have to get in at least 10 out and backs on both bike to find a true avg wattage to compare. I'd also have to keep swapping bikes every lap or so just in case the wind speed or direction changes during the length of the test.
This type of test would give you the difference in wattage needed to avg say 20 mph with a headwind or with a tailwind for each style bike. You'd also be able to compare the two bikes to one another during each direction. Because the test course will be set as a strava segment I can roll into it already at the avg speed and the computer will start and finish collecting the data for each run on its own. Then if I set one of my data fields to display avg lap speed I should have to problem hitting an avg to the tenth of a mph.
I could probably do the same test on a climb but it would need to be steady and done on its own in similar fashion. I can think of one place that could work for the hill test maybe.