Your Long-Awaited 2022 MS150 Recap!

FRIENDS!

Over the weekend, I completed my TENTH MS150 ride to end Multiple Sclerosis. I say that, and it’s true that this is the tenth time I’ve been REGISTERED for this ride, but the slings and arrows of outrageous fortune have had their way with this event over the years. To wit:

  • 2013: YEAR ONE. I ride a two-day event ending in downtown Austin, but I do it SLOW because I am FAT.
  • 2014: Sure, why not do it again? I’m a little slimmer but still very slow. My team masses up just outside downtown to roll across the finish line together, which is EXHILARATING but also a giant PITA for our friends and family waiting at the ACTUAL finish.
  • 2015: The weather conspires to take the first day of the event, which is fine because I do not ride, owing to certain medical misadventures, but I still raise money — by now, the mission of the event has taken root in my head, and so fundraising tops $5,000.
  • 2016: Participation on the weekend is lower because of threatening weather, but my team saddles up for day 1, the hundred mile route into La Grange. Day 2 is cancelled during Saturday’s ride, which (unfortunately?) opens the door for a seriously epic bash in the campground. Fun was had, but the hangovers were definitely earned.
  • 2017: AT LAST a return to the two-day ride plan! We didn’t know it at the time, but this would be the last ride to finish in downtown Austin.
  • 2018: I’m a lot stronger, which is fun, and my pals and I knock out the first day in a hair over 5 hours. Day 2 ends at Circuit of the Americas, a huge Formula 1 track outside Austin. This is NOT a great endpoint, but any port in a storm.
  • 2019: COTA again, but by now acknowledged as a stopgap. This is my strongest two-day effort, and the only time I felt up to doing the “challenge” route through the state park outside Bastrop. I’m really bummed about that — I probably could’ve done it in ’17 and ’18, but confidence is a bitch sometimes.
  • 2020: The ORIGINAL plan for the 2020 ride, released in late 2019, was a reimagining of day 2 entirely. The day one routes and endpoint (La Grange) work well and were retained, but day 2 would bring the ride back east and forsake Austin for College Station. Texas A&M was VERY welcoming, and set up a plan for riders to finish ON KYLE FIELD. The logistics of ending this event in a place like that, which was already engineered to entertain 100,000+ people, were VERY attractive. And then COVID happened. Initially, the ride was pushed to the fall and reduced to a one-day event going to College Station, but that was just wishful thinking. COVID eventually forced a full cancellation.
  • 2021: With COVID waning a bit, they tried to do the one-day College Station plan again, but weather eventually forced an 11th hour cancellation. Even so, I hit a personal best on fundraising of over $17,400.
  • 2022: Now, finally, we get the full two-day College Station plan. It was, by all accounts a HUGE success!

So if you’re keeping track, out of ten rides, I’ve actually done a 2-day effort only 6 times. Two we lost to due to COVID; one I sat out entirely for medical reasons; and once we lost day 2. Oh well!

So, Chet, how’d it go this year?
Great question! Let me tell you.
You ride a whole bunch! I’ll bet you just ate this up with a spoon, right?
Well, funny thing about that. It’s true I AM a pretty dedicated rider, and usually notch 100-140 miles in any given week including back-to-back efforts on the weekends, especially this time of year, and largely to prep for this event. But this time around, a crash back in March utterly derailed my training at a critical time. I lost several weeks of those back-to-back efforts, and came into the ride at a lower level of fitness than I wanted.
Wait. Crash? What?
Yeah, not a big deal in the larger scope of things — nothing broken, gnarly roadrash, sprained shoulder, etc — but I had to lay off a while. Had it been a month further back, it would’ve made all the difference.
Quit bitching. You did the ride, didn’t you?
Damn right. It was just harder than I expected.
Define “harder”?
Well, we still kept a solid pace though the start of the hills on day one, but it was slower than in prior years owing to (a) a shared lower fitness with my immediate cadre of pals and (b) the fact that 3 folks made the choice to do the ride on mountain bikes as training for an ultra-endurance event called Leadville later in the year. The gearing on those makes it VERY hard to maintain speeds that are not especially fast on a road bike, but owing to point (a) this was less of an issue.
Who are these weirdos you rode with?
Aha! There’s a picture! L to R: Your Humble Author; Amish Mechanic; Everyone’s Favorite Bulldozer Rep; She Who Questioned Her Choices A Bit; Person I Don’t Know Well Enough To Have A Funny Name For; The Charming Axis of Bradford & Cody; The Amazing Returning Cory. (It amuses me to note that there are 5 A&M degrees represented across only 8 folks, but one person is double dipping.)

IMG 2717

Ok, so then what?
Well, as expected, things got harder for me once the hills hit in Bellville, or about halfway. You can see the elevation graph below; that’s where the Hill Country starts. I am a flatlander, and I am 52 and mildly overweight, and so these are hard for me. But that’s not what made the day suck.

Screen Shot 2022 05 03 at 11 30 11 AM

What DID make the day suck?
Cramps. I am not, historically, a person who cramps up. I ride thousands of miles every summer in Houston’s tropical humidity and heat, and it really never comes up. I only recently started carrying salt-supplement tablets, and I mostly have them to give to OTHER people. I’m careful about on-bike hydration and nutrition — any long effort is at least partly an exercise in body chemistry; you MUST eat and drink a LOT to ride 100 miles — and so I figured this was a solved problem for me.

Around mile 60, it becamse clear that no, this was NOT a solved problem for me, and that the rest of the day was going to suck out loud.
That sounds bad.
Yeah, you’re not wrong. The weird thing is that, according to Strava for Day 1, I actually covered the second half of the ride in SLIGHTLY less time than I did in 2019. I have no idea how that could be true, because I felt like CRAP and could only occasionally really put my legs into it; most attempts at any real power would bring back the cramps. But I didn’t sag. I don’t sag.
What DIDN’T suck about the day?
The company. Even once I was mostly riding alone, I still ran into my friends on the regular — with the exception of the very HEAD end of folks, we weren’t THAT far apart on the route, and so we’d see each other at rest stops, or pass one another and start riding together again. The suck is ameliorated in good company.
I’ll bet it felt good to stop!
Absolutely, but in this case it was very much in the way that it feels good to stop smashing yourself in the head with a ball-peen hammer. I was so wrecked that I gave SERIOUS thought to bailing on day 2.
But did you die?
Reader, I did not in fact die. A coke, a beer, a giant jug of electrolyte recovery drink, and a huge plate of Mexican food led directly to about 10 hours sleep, and that helped a LOT. I wasn’t exactly bright eyed and bushy tailed by Sunday morning, but I was no longer in danger of quitting. After all, I had 70 donors watching me via LiveTrack!
So tell us about day 2.
Traditionally, day 1 of this ride, at least for stronger riders, is about seeing what they can do. Put your back into it, and drop the hammer, and test yourself. Day 2, on the other hand, is about riding with your teammates and friends, and for that I was GRATEFUL. I rolled out with a small set of pals — mostly the folks enumerated above — and we put some speed out for about 15-20 miles before a few of us decided to drop back and let the stronger ones surge ahead. That triad of folks — me, my pal Bruno, and Eric Cody from day 1 — really ended up doing most of the 80 miles into College Station in some flavor of together. Some of the time it was Bruno pulling me, and some of the time it was me and Bruno pulling Eric, but it was definitely cooperative.
Did the cramps come back?
NO, thank God. I had limited power until lunch, but figuring I was probably low on fuel we DID stop at the lunch stop and eat. We don’t normally do this — we skipped lunch on day 1, for example, as we nearly ALWAYS do — but on Sunday, I needed it. This made a huge difference for the back half of the day; I was finally able to put down a little power, and felt good about finishing the ride. Also, lunch pics with BRUNO and ELLENDROTT!

95D1394D 1590 4421 9EA5 94BE92781CBE 1 105 c

D665411C EC2E 47AA BF3C C7C01A749809 1 105 c

Anything else?
Yeah, impromptu breaks helped, too.
“Impromptu?”
Yeah, the Society I guess lost the usual day-2 lunch sponsor (HEB), and as such had no drinks other than water or Gatorade at lunch. Eric and Bruno and I, though, REALLY REALY wanted (and had ANTICIPATED) a Coke. (You have NO idea how good a Coke can be on a hot day like that.) As luck would have it, a stopped freight train not long after lunch left us idle for a few minutes in front of a gas station, and so…

E7293097 A6B2 4B12 B2A7 D958657BDA25 1 105 c

Let’s talk about momentum
That’s where we find ourselves after the Cokes. We were over 50 miles into what we thought was an 80 mile day, so definitely on the downhill side. (Turns out, it was 85 miles, the extra 5 wasn’t on our radar until later.) Plus, the elevation gains for this ride were actually mostly behind us, which we knew, and which made us feel a LOT better.

Screen Shot 2022 05 03 at 11 23 57 AM

How about that finish?
It was, as expected, pretty damn awesome. A&M has every right to be proud here; they rolled out the red carpet for us. The ride literally finished on the football field. We did a “victory lap” around the field, and my name was announced (in my capacity as a top fundraiser) while Erin and other friends already finished cheered for me. That was pretty darn nice, and WAY better than the ending experience at either COTA or downtown Austin.

68CEECFE 6250 48BA AD48 5DF2C2B06206 1 105 c

And what about the REST?
Well, there is one other thing. This year, I topped $100,000 in lifetime fundraising for this event. If you’re reading this, there’s a very very good chance you’re a part of that. Your support means the world to me, and it WAS that support that kept me rolling when things were going poorly for me on Saturday. I thank you, and the Society thanks you.

Hey Chet, what’s a Criterium?

Scary as FUCK, that’s what.

Seriously, though, it’s a timed, multilap bicycle race over a relatively short closed course. We had one here in Houston on Sunday morning, and while I don’t participate, I have a lot of friends who do.

It’s not one big race, obviously. Bike racing, like most sports, is split into levels. Let’s be clear, too: Cat 5 riders are CRAZY strong compared to non-racing folks. I’ve been doing pretty serious structured workouts for 6+ months now, and I’m absolutely sure that I’d still be dead last in any competitive Cat 5 field.

  • Rank beginners are Cat 5.
  • Some of those will progress to Cat 4.
  • Getting to Cat 3 involves a shitload of work and no small amount of talent. I don’t know many Cat 3 road racers.
  • By the time you’re in Cat 2 or Cat 1, you’re getting lots of stuff for free.
  • Above Cat 1 you find the Pro ranks — and it’s a long way from being a local pro to the class of folks you’ll see on the Champs-Élysées every summer.

And for logistics purposes, these categories combined for actual races. For example, we had friends in 4 different races on Sunday morning:

  • 1 in the Men’s Cat 4/5 race;
  • 4 in the combined Women’s Cat 4/5 & Women’s 40+ 3/4/5 race;
  • Several in Men’s Masters 4/5 (35+);
  • Plus my coach Jason in the Men’s Cat 3

Jason was doing well going into the final lap, but in close-quarters riding like this crashes are a risk, and they had one. Jason didn’t go down, but he was behind it enough that it blew his finish.

Someone very close to Jason in the peloton had Garmin cameras on the front and back of his bike, and has posted the final lap. You don’t really see Jason until the post-crash moments, when he edits in the rear-facing footage, but when you do it’s super clear how close he came to being in a super scary sprinting pileup.

He’s here (click to embiggen; note they’re at 25MPH here!):

Screen Shot 2018 05 09 at 2 11 24 PM

And here’s the whole video:

Stay with the video until the finish, and pay attention to the lower left; the camera setup used by the rider allows him to superimpose his speed and power on the screen. Yes, they’re sprinting at 40MPH.

For more fun footage, check out this guy’s 7:30 video, which includes some sweet overhead drone footage.

Things even non-riders might find amusing

I like riding, and I like data. I also like getting faster, so with the encouragement of a friend who offered to coach, I bought a power meter for my bike to facilitate more directed training.

In order for this to be useful, though, I also needed to establish a baseline of my maximum sustained effort. Cyclists call this the Functional Threshold Power. The truer test is an hour long ride where you go as hard as you can for the whole hour, leaving nothing in the tank.

That’s obviously unpleasant (you’re alone) and hard to gauge (am I going to fast? too slow?), so the more common approach is to do a 20 minute test and multiply by .95, which is what I did today.

This isn’t the sort of thing you want to do on public roads, obviously; fortunately, Houston has Memorial Park and the Picnic Loop, which is a closed, paved track available for public use. When the weather’s nice, you see lots of riders on it, but also walkers and whatnot. Anyway, it’s close enough to the house that I used the ride over as a little warmup, and then started the FTP test as soon as I hit the entrance to the track.

After 20 minutes, I backed off, exited the track, and rode home.

So, can you see the part of this graph from Strava that represents the 20 minute test?

Screen Shot 2017 11 21 at 2 47 01 PM

My superpower is Excel combined with an unseemly attachment to numbers.

When I was first riding pretty seriously as an adult, back in 2014, I tried to keep up a hundred-miles-per-week goal, and I tracked it in Excel.

Obviously, that 2014 sheet is kind of depressing now, since it shows me doing exactly that for weeks on endf — rom June until the week I got hurt in November, and then a loooong sequence of zero mile weeks starts up.

When I started riding again, after rehab in spring of last year, I started a new sheet. I was weak, obviously, and was turning in at best one or two rides a week for a long time. My first ride in that sheet was in the week ending 3/29/15, but I didn’t get over 70 miles in a week until June, and I didn’t top 100 again until the week ending July 19, when I rode my first significant distance post-injury at the Katy Flatland ride. I skipped the century in favor of the “metric century,” i.e. 100 kilometers, or 62 miles. So that week’s a bit of a holiday for me.

In all, I had 15 weeks at 100 miles or better in 2015. I finished up with a shade under 2,800 miles for the year, which I’m kind of proud of given the slow start and the fact that I missed the entire first quarter.

I’m back in the thick of it now. My goal is still 100 a week, but now I have a long term goal, too: I want 5,000 miles in 2016. I’m on track for it, too — slightly ahead, even. For the year, I’m at 1,714 miles, with an average of about 97 per week.

Anyway, it occurred to me to check what my actual mileage and average was since that Katy ride last summer, and now i know: In the 42 weeks since then, I’ve ridden 3,806 miles, averaging about 90.6 per week.

I’ll take it.

Goddammit, Garmin.

Ho. Lee. Fuck.

Longtime readers may recall the trouble I had with a Garmin bike GPS device last summer and fall. They could not get me a model 510 that worked for love or money — Bluetooth connectivity (and thus LiveTrack) never worked reliably, and (worse) the device would sometimes just plain eat data. On two such occasions, it did so on rides I was doing out of town in novel places, where I couldn’t easily duplicate the track. Well done, jackasses!

Anyway, they sorta-fixed it by agreeing to let me swap the 4th or 5th 510 for the next model up, and since then it’s worked better. Bluetooth still only works about 80% of the time, but at least it’s not eating data. I declared victory.

However, as it turns out, Garmin’s aggressive Suck program has other areas of focus, too!

Bike computers of all types generally use a wheel sensor to track speed. You tell the computer how big your wheel is, and the sensor tracks rotations, which gives you pretty accurate speed and distance readings. (GPS devices can work without these with a loss of accuracy, but since they’re easy to use there’s little reason not to use them.)

If you’re really paying attention to training, then you probably also want a cadence sensor, which tells you how many revolutions your feet are making every minute. Typically, you want to pedal faster instead of mashing harder — you’ll be more efficient that way, and get a more aerobic workout.

Traditionally, both speed and cadence sensors have used a pair of magnets to capture data: one affixed to the bike frame, and another affixed to the thing that goes around. For speed, you usually see it on the front fork with the companion magnet affixed to a spoke. For cadence, you get magnets on the chainstay and crank arm on the non-drivetrain side. (Most of the time these days, the sensors require no wires to communicate with the head unit.)

I have sensors like this on my older bike. It’s obviously somewhat fiddly and visually cluttered, but they work fine.

A year or so ago, we started to see more clever sensors for both things. Garmin has a pair that attach only at single points, and require no magnet alignment: the speed sensor attaches to the hub of one of your wheels, and the cadence sensor attaches to a crank arm. Both sense motion itself, not magnetic field flux. They’re much less fiddly (nothing to keep aligned) and are drastically more visually appealing on the bike. I chose those for the new bike last fall. So far, they’ve worked fine, too — with one exception I encountered last week.

The cadence sensor is a little thin pod about the size of two quarters that you attach to the interior of your crank arm using one of three supplied (but proprietary) rubber bands. I say they include three, but they’re in three sizes, so you only get one that will actually work with your bike.

I was a little dubious of this choice on installation, and it turns out I had good reason. Last Tuesday I noticed that the band on mine was partly broken. They get credit for using a design wherein a single break won’t allow the sensor to fall off, but that’s where credit stops.

You see, you can’t just go to the Garmin web store (or your favorite retailer) and buy a pack of replacement bands. They’re nowhere. I opened a support ticket about this last night; here’s what I got back:

Thank you for contacting Garmin International.

I would be happy to assist you.  

The replacement straps aren’t available through our website, but we do have them available for sale through the number below. A set of three straps is $10 plus shipping and any applicable sales tax. Please call us at the number below to place your order as we are unable to take payment information over email. 

Now, note that he says “set of three.” That sounds reasonable at first, but it turns out they mean “one each of three different sizes.” In other words, they’re asking you to spend ten bucks for a single goddamn rubber band when the first one didn’t even last a year.

When I pointed this out somewhat firmly, the dude I got on the phone offered to send me a set (again, of which two are useless) gratis, which arrived on Saturday.

What’s the over/under on how many times I can shame them into replacing the band for free?

Well, I’ll be damned.

First time back out with the Ride Formerly Known As West End (Reform Congregation), and lookie here:

Screen Shot 2015 04 30 at 9 28 13 PM

IOW, I rode that segment faster tonight than I did in September, when I was at nearly peak form. Flatline speed is there, it’s just the explosive acceleration I have trouble with. I’m pretty amazed, and very pleased.

Today in GPS Amusements

At the Tour de Houston afterparty, a friend noted that, when his wife had a season-ending crash on the TdH last year, her GPS track showed it quite clearly. We checked the track for my last November ride, and sure enough, it’s pretty clear for me, too:

Screen Shot 2015 03 15 at 3 54 16 PM

Heh. I dunno if someone thought to stop it or what, but I remain surprised that the track doesn’t show the part with my bike in the car post-crash.