Friday, September 11, 2020

WTRL TTT - New team, same great taste!

 Last night saw my return to Zwift racing after a multi-month respite. I've been focusing on the great outdoors and back-filling Zwift rides as recovery efforts, so I haven't really been doing the kinds of efforts required in a team time trial, and I hadn't really cared much about it until I got a surprise invite on Tuesday to race with the CRYO-GEN Eagles.

That's not a lot of time to prepare, and I have been enjoying a LOT of cookies this summer.

I was able to shed 2 lbs by race day--not back to spring fighting weight, but enough to make the watts-per-kilogram numbers a little less upsetting, especially since the target power was 5.5 W/kg. That's a big number, and well beyond my threshold. The plan also had each rider taking 30-second pulls, and we were running a full crew of 8 at the start, so there should have, at least in theory, been plenty of time to draft below threshold between pulls.

But the plan had a harsh reality to overcome: the circuit was my 2nd least favorite Zwift course: Harrogate. Blech. Gross. Literally only the jungle is worse. Gimme a drag race up Ventoux, or boring laps of Tempus Fugit. But Harrogate? It's just false flats all over the place, and that long drag up Otley Rd is so punishing. The downhills are barely long enough to recover, and the climb to the finish is really tricky to time right. I don't care for it.

Anyway.

We got out of the pens and organized far more quickly than with my previous team, and rotations settled in early. One rider was performing team car duties excellently, calling up rotations and keeping overall calm. Otley Rd claimed an early victim, but our remaining team of 7 soldiered on to the first climb at a crushing 4.55W/kg average. I was on the ragged edge for most of the race, struggling to find consistency on the front, and struggling to get my heart-rate under control OFF the front.

By the time we'd done Otley Rd on the 2nd lap, we were down to 5. With a minimum of 4 riders needed for a team result, we were determined not to lose anyone else, just in case someone had a network/power/vmechanical issue. That meant big efforts and a couple of skipped pulls, which really sucked to have to do. We gave up 22 seconds on the 2nd lap, which is pretty daggone respectable given that we lost 2 riders early. But the way we gave that time up suggests the strategy could use some refinement.

Let me be clear: this is a FAST team with some very strong riders. Everybody on the squad was in A, with 2 A+ riders in the group. Looking through Zwiftpower's sign-up list, everyone had recently held at least 4.3W/kg. And our lap times showed that: we were over 2 minutes faster in our first lap than the Vultures were back in February. So power was NOT an issue here.

But looking at the lap-over-lap analysis, it seems trying to hold a consistent power may not have been the best approach to this course.

The first lap saw an average wattage of 296, with a stupid high peak of 560, and an average heart rate 1 beat into Z5 for me @ 175.

What's fascinating to me is what the 30-second intervals did to my body compared to the climbs. From the turn onto Otley Rd to the sharp drop on Pot Bank, my heart never comes out of Z5. I wasn't frankly sure I'd survive the first lap, and even with a brief reprieve into the very tippy top of Z4 on the descent, I was pushing on max HR before we even hit the first KOM run. This is not a recipe for success for me.

But then things get interesting. I was able to settle into exactly 5.5W/kg for the first half of the KOM, letting off the pressure just slightly on the flatter middle plateau to 5W/kg to bring the group back together, and while my HR soared to 183 for the 2:40 climb, it actually recovered very well on the descent, hitting its lowest number for the rest of the lap @ 168.

The group was, at this point, disorganized and gasping for breath, but we held a consistent 280W--still slightly over 4W/kg--to the end of the lap. Looking at the top chart above, you can see we lost no time lap-over-lap after the KOM, and in fact my average power and heart rate were identical between them, again with 2 fewer riders.

To me that suggests we were letting the terrain be a greater influence on our output than choreographed power targets, and the data in the visual above proves it out: when the ground goes up, so does my heart rate.

Because we allowed that natural use of terrain only after getting shattered on the climb, it further suggests that approach could have been employed to greater effect on the front half of the course.

For instance, our first run up Otley Rd took 7 riders 2:54 with my average power sitting at 317W. The 2nd run, gasping for breath and down 2 more riders, was completed 7 seconds slower @ 3:01 & 306W. 11 watts, smaller draft: 7 second penalty. That trend continued as we pushed through the lap, except I was having to skip pulls to stay with the group. 

By the 2nd false flat (finishing Otley & onto Pot bank), we were down to 3 or 4 riders pulling, with a 4-second loss and an overall power loss of 31W compared to the first lap. That's a big drop-off, with almost identical losses on the 3rd lump.

Conversely, we were losing almost nothing on the descents, irrespective of power output.

And that's where our race was decided: on those 3 false flats in the first half of the lap. Big crazy power numbers on the first lap, deflated riders on the 2nd.

But then we hit the KOM again and pretty much stopped losing time, and looking through my data, it seems that while I was off from the 5.5W/kg on the first half of the first run, I wasn't off by much. A 22W loss brought me to 5.1W/kg, again backing off slightly to identical first-lap numbers after the mid-point. Both 5+W/kg intervals were just over 70 seconds, suggesting that's my sweet spot for bigger numbers. And just as with the first lap, the following descent saw my lowest heart rate and best recovery of the lap.

Next time I think I'll advocate for longer turns on the front with target variations for the terrain, and be happy to get either.

All in all I was extremely pleased with our performance, and thrilled to be able to lay down the watts after a 3 month break from Zwift races. I need to add it back into my regimen, but figure out how to do it without turning back into a 1-hour specialist, because outdoor races WILL come back at some point (please please please).

Total: 39:26 / 26.5 mph / 290W (4.46W/kg) / 175bpm
Lap 1: 19:22 / 26.8 mph / 296W (4.55W/kg) / 175bpm
Lap 2: 19:43 / 26.3 mph / 285W (4.38W/kg) / 175bpm

Otley Rd Climb (1 mile @ 3%)
Lap 1: 2:54 / 20.7 mph / 317W / 172bpm / 7 riders
Lap 2: 3:01 / 19.9 mph / 306W / 179bpm / 5 riders

Otley False Flat (1.1 miles @ 1%)
Lap 1: 2:23 / 27.8 mph / 313W / 177bpm / 7 riders
Lap 2: 2:27 / 27.1 mph / 282W / 172bpm / 5 riders (no pulls)

Yorkshire KOM (0.74 miles @ 5%)
Lap 1: 2:40 / 17.2 mph / 331W (357 / 309) / 178bpm
Lap 2: 2:42 / 17.0 mph / 321W (331 / 309) / 178bpm

KOM top to finish (3.1 miles @ -0.7%)
Lap 1: 6:23 / 29.2 mph / 281W / 174bpm / 7 riders
Lap 2: 6:19 / 29.5 mph / 282W / 175bpm / 5 riders (back in rotation, sprint finish)

Thursday, August 06, 2020

I failed a cycling purity test

The other day I engaged in a conversation on Facebook. I know, I'm sorry. I'd say it won't happen again, but that would be a lie.

The conversation was started by a pro cyclist about the incredible advantages of disc brakes. He wrote a great paean to disc brakes, which are absolutely far superior to rim brakes, but he ended it with a call for all cyclists to immediately switch.

Now I'm all about embracing new hotness, but I also have pay a mortgage and make sure my kids can eat. Those things are priorities, and cycling is a hobby. An obsessive hobby, but still: a hobby.

I responded to his argument by saying the conversion to disc brakes is not a trivial matter. One cannot, for instance, simply mount disc calipers to any given road frame, nor can one slap on a disc to any given wheel. Both items are made specifically for one brake technology or the other (let's not get into weird custom-builds). So to "make the switch" to disc means buying a new bike. Or new bikes.

Instead of acknowledging that there is a price barrier to changing brakes, he pointed out that I have more bikes than he does, as if to invalidate my argument of price savings.

I was lucky that, when I first got into this hobby in 2015, 11-speed components were just becoming standard equipment across road and mountain bikes. I chose to set my bikes up with Shimano and SRAM components because they're largely interchangeable. So gearing was easy. I could swap drivetrains between bikes with no more effort than a couple of hours and a new set of cables.

But when I bought my 2nd road bike for commuting, I had a tough choice to make: disc or rim brakes? I knew I wanted faster wheels for my race bike, and that the stock wheels on the commuter would be horrible. If I went with disc brakes, I'd be buying a new bike plus two new sets of wheels. That would mean shelling out at least $1,000 for a new bike, then another $550 for Mavic's Ksyrium Pro Disc (cheap, light, and shipped with tires!), AND THEN another ~$1000 for used carbon race wheels for the other bike. Minimum $2500. Or I could buy the rim-brake bike and upgrade my race wheels later, saving hundreds (ended up saving $800 going this route).

Now there are many riders out there for whom those numbers sound pretty cheap, and nothing throws that into sharper relief than the industry buzz around the new Specialized Tarmac SL7. This new "end all, be all" of road cycling can be yours for the low low price of $12,000, plus tax. Oh and then you'll have to buy pedals, because bikes don't come with pedals. Oh you want bottle cages? Maybe a cyclocomputer? You're bumping up into the $13,500 range now, all in. The kids don't really eat all that much, anyway.

Over the past 5 years, I've accumulated 3 road bikes of my own (+1 for Alastair) that all use rim brakes. Across the board I have a TT bike, a race bike, and a rain/commuter bike. On those bikes I have aero wheels, a disc TT rear wheel, climbing wheels, and a set of commuting wheels. Literally all completely interchangeable with just a few adjustments. And they can also all trickle down to Alastair's bike. All in, including pedals, cyclocomputer, bottle cages, panniers for the commuter, etc etc etc? $12,323.45. I have the receipts.

For less than the take-home cost of a top-range SL7, I've gotten 29,526.8 miles over 1255 rides across 3 rim-brake bikes.

All costs are tracked in Excel and correlated to Strava data thru Power BI


No single bike in my arsenal has even crossed the midway point of the SL7's cost, including my main race bike, which is just now--after 5 years--nudging up to $6000, including $2200 in repairs and $2285 in upgrades. FWIW, that bike brand new in 2011 was listed at $7000 (the same price as a brand new mid-range Tarmac SL7...still without pedals!), so I 'm not even up to the initial purchase price in 20,066 miles of use. I bought it for $950 in August 2015 and have replaced literally everything on it except the fork and the crankset. It has thrashed bearings, crashed hard sacrificed pedals & handlebars, and it's still a rock solid light-weight (998g) carbon, aero, internally-routed crit monster, even at 10 years old.

This sport is stupendously expensive--there's just no getting around that. But it doesn't have to be expensive-r just because there's a new braking technology around. In fact the budget racer is LOVING life right now while all the rich kids dump their old tech. I got my Zipp 404 Firecrests last year at a race for a third of what they cost new. Same for my Super9. These deals do not yet exist in the disc-brake space.

But I know the tech is changing. 12-speed is in the market. Electronic shifting is becoming such a standard some bikes don't even support cables any more. Disc brakes are the norm. When I replace a bike, it will have at least one of those 3 items, and my interchangeability will be diminished. And that's ok, but it's not going to happen until I break a bike, because my kids eat like horses.

Monday, August 03, 2020

The Overtake

As a cyclist, there is a moment that occurs every time a car passes. It usually doesn't last more than half a second, but in that time, your life hangs in the balance. Is the car going to kill you?

For the most part, riders can fit comfortably into two camps: the first assumes the answer is usually yes, and generally switches to mountain bikes pretty quickly and forswears the road. The second set, though, has to accept this moment, which can happen hundreds of times on a single ride, is fleeting and worth the risk for the joy of the open road.

Being born to one camp doesn't mean you can't switch to the other, but I try really hard not to let fear take hold of my heart, and usually I'm able to move beyond a pass.

But some are scarier than others. In that moment, when your nerves are on fire and your heart is trying to jump through your throat, a driver holds your fate completely in their hands. A friendly honk becomes much less friendly if it makes the rider jump out of his or her skin. Certainly rolling down the window to shout obscenities isn't the kindest way to pass, either, though this is actually one of the least upsetting things a driver or passenger can do (do they have any idea how absurd their voices sound at full-chipmunk screech over the wind?).

There are the big trucks that push an air wall around them, first moving you toward a ditch and then almost sucking you into the side of them. There are trailers that drivers merge into your lane. There's the 2nd gear 7000RPM unmuffled exhaust  guy. The coal-roller. The person who sits on your wheel for half a mile while traffic backs up behind them getting angry at you before they even get to you.

All terrifying. All totally normal.

Yesterday I learned of a new foe: the police loudspeaker.

My son and I were out for a Sunday ride on quiet country roads when we encountered a particularly sharp climb. He is very (very) fond of drafting me, but knows to keep his front wheel clear of the rider ahead in case that rider pulls the bike backward to stand. So when the road goes up, he moves slightly left for safety.

Virginia code mandates that cyclists remain "as close as safely practicable to the right curb or edge of roadway", that cyclists cannot ride MORE THAN two abreast, and that riders remain single-file when being overtaken.

So we were making the climb single-file when a car passed without incident. Not pushing too hard, just rolling into power and trying to stay steady. As a second car begins to pull around us, just as the 'will I live or die' moment began to spring to life, came an unexpected loudspeaker: 'YOU NEED TO BE RIDING SINGLE FILE. NOT ABREAST.'

I nearly crashed. So did my son.

I threw up my arm in a WTF gesture before I could even turn my head to the left to see what the heck was happening, and was treated to a follow-up: 'YOU DON'T NEED TO WAVE YOUR ARM AROUND AT ME.' As I'm hearing this, I realize it's a cop, and I'm further realizing that Alastair's wheel is FIRMLY behind my own, though just slightly to the left. We are not abreast.

Cop speeds off up the hill. I asked Alastair if he was ok, he confirmed that he was spooked and angry, and I got pissed. Tried to chase the cop up the hill, but really: it's a hill and he was in a car. He was long gone by the time I got to the closest stop sign.

I titled my Strava ride with an inappropriate term for police officers, but let's break down why I'm not apologizing for that.

Every overtake is dangerous. We've already established that I accept that risk, but every single time there is that moment of not knowing if you're going to live or die.

This officer chose that exact moment--I'm sure he didn't know that, but he did it--to verbally accost us. And he did it in a way that demanded we accept his authority: over the loudspeaker with the windows up. Unannounced and disinviting of even my arm gesture in response. There was no intention of ensuring public safety. There was no goal of 'serve and protect'. There was only one goal: intimidate. And he achieved it. And from within the safety of that 4000 lb steel fortress of air-conditioning and horsepower, he did it with the impunity of not worrying if we lived or died.

There was another car behind him. If I'd crashed, Alastair would have hit me, also causing him to crash. That crash could have put us directly into the traffic that was right behind the police car. Or into the ditch.

If we'd crashed under a car, that officer would be RESPONSIBLE for the death of a 14 year old. But he'd use his badge to claim he was chiding us as wayward evil cyclists when the unforseeable happened and we swerved and crashed. Not his fault, your honor!

If we'd crashed into the ditch, would he stop the comfy car and check on us? If I yelled at him for endangering our lives in that moment, would he have decided I was belligerent and needed to cool my heels in a cell?

Nothing--not one thing--about his intimidation tactic was safe or in the public interest. In that moment, he was not a public servant. He was a pig. He used his badge and his official equipment to put exposed road-users at greater risk for his own amusement.