Cedar Point 70.3 - 05:29:01.830

After a stomach flu related DNS at Cedar Point last year, and a terrible DNF at the half distance this year, I really wanted Cedar Point to go right. 

Please be sure to read this post on how I revamped my nutrition for a cramp free (but still very colorful) experience.

Lana had to work until Friday evening, so we drove half way from Illinois to Ohio Friday night and we stopped at South Bend Indiana, in this awful hotel.   It was right on Notre Dames campus, and there were groups of drunk hockey players out playing bags in the parking lot until 3 in the morning.   The next morning they had ‘breakfast’ that both of us were pretty afraid of, but since there was no microwave in the room we made do.

We made it to Ohio and got a quick swim in, then registered.  After registration I was shaking down my bike when I discovered my front wheel was flat.   I fixed it and noticed the wheel was once again leaking from the valve.   I changed the valve extender, and my problem was fixed so I checked my bike in.  To say I was on edge would be a massive understatement.

That night we made dinner in our room, as extra food poisoning prevention. Unfortunately Lana said her stomach was already upset.  I walked down the beach to check my bike one last time that night.  The tire was holding…  I set the alarm for 4am and went to bed.

That night, at about 2 am, Lana was sick.   It seemed very similar to what I had the year before.  After the tire stress, and then this, I had really had my fill of this race.  Two years in a row…

I thought about it, but I knew Lana would want me to race.  She went back to bed.  I felt terrible for her.   When I got dressed that morning I had a problem with the zipper on my new jersey.   I’d only worn it once before, so Lana suggested I take her bike jersey with, just in case…

Swim

Time  35:19

Distance 1.2M

Rate 2:00/100

AG Place 13 / 75

The lake swim was moved to the bay this year, because a 25ish mph wind was creating some rip currents in the lake that made swimming too dangerous, according to the coast guard.

It was a TT start, and I had to wait forever (it felt) to swim.   The swim was at least half a mile from T1. 

My swim went really well.   I had a new wetsuit I was looking forward to wearing (Tyr Hurricane Cat 5).   My only complaint, and it happens a lot in triathlon swims, is that the distance just doesn't add up.   My GPS reported 1.33 miles instead of 1.2.  That’s the difference between a 1:33/100 swim and a 2:00/100 swim.   Admittedly, I could have sighted poorly or my watch could have been off, but I rarely swim as slow as 2:00/100, even on a cool down lap, and I doubt very much that a 2:00/100 pace would have gotten me 13 in my AG.   So, I choose to believe I swam the 1.3 miles.  :)

T1: 09:35

Note previous comment about long long run to T1.

Bike

Time 2:36:07

Distance 56 Miles

Speed 21.53

AG Place 16 / 75

Well, the good news is I had air pressure in my tire!

Conditions were pretty bad.    It was very windy and misting rain, enough to make the cornering slow.

After the first 10 minutes I started working at my goal watts.  My RPE was way too high though, like time trial high.  But I was still missing my numbers by about 5W.  I looked down and noted I was averaging about 23 Mph.   Nope, too hard.  Something’s wrong with the quarq maybe.   I was questioning everything, trying to figure out if I should push it, back down, or something else.  What’s the plan?   I spun the pedals backwards a few times to try to zero the quarq out.   Still, things aren’t feeling right, and I seriously doubt my electronics.   Then I remember that I calibrated the quarq when it was in the rev3 rack.  Maybe that?  

 Then comes a wave of doubt.   Have I already blown it?   Did I go too hard chasing that number to run later?   In the end, I made the call to flip to my plan B screen, which has heart rate but not power on it, and rode by RPE and heart rate. 

By mile 56, I was ready to get off the bike, and my average pace was right in line with what I did at route 66, on a worse day.   So, even if I wasn't hitting my numbers, I was going hard enough for today. 

The last ten miles of the bike were with a wicked cross wind coming from over the beach.  It was like being sand blasted.  I was holding on for dear life, and sand was everywhere.   Up my nose, in my mouth, everywhere.   I was happy to be done, but unsure about the run.  

  

T2: 04:13

Right off the bike into T2 I noticed the zipper had broken on my new jersey.   Seriously?   Luckily I had Lana’s bike jersey at her request earlier.  

I took my time in T2, changing into dry socks, plan B for wet weather on the bike.  I glanced down at my HRM and saw that the sock change brought me down into zone 1, so I figured I’d go out and run a few miles at low zone 2 and see what stuck, I was wanting to be careful at this point.   Thinking about Lana sick in bed, I didn't want to drive all the way out here for another DNF, so a conservative approach was warranted.

Run

Time 2:03:48

Distance 13.1 Miles

Pace 9:31

AG Place 25 / 75

After the first few miles ticked by, I was pretty pleased to see I was sitting right around 9 minute pace, at the lowish end of zone 2 heart rate.   Combined with quick aid station walks, I was averaging about 9:20.   Not speedy, but I knew at even that pace I was lined up for a huge PR.  I was running really well, and decided to stay at that conservative pace.  (Yes Laura, your run training is working!!!)  

At about mile 5 I picked it up into upper zone 2, but I was really staying at about the same pace.  

Around mile 10, I finally let myself hit zone 3.   Running back into the park the last two miles, I was running directly into the wind and I was very glad I was as fresh as I was.   I was right at threshold, running a 10 minute mile.   Once we finally turned, I was all out, trying not to barf, and running to the finish.  

And finally, having executed every plan B in my race plan, thinking about my poor wife with the same stomach bug I had last year, my jacked up quarq, and the flats the day before, I turned down the finish chute to smile for my finish line picture, in my purple woman’s bike jersey, relieved to cross the finish and happy that an anvil didn't fall from the sky to bonk me on the head.   Good grief, what a race.

On Statistics and Half Ironman: Going from a DNF to a 15 minute PR at the half distance

Flash back to last year, I got a stomach bug and DNS’s CedarPoint.

Then, this July, The Route 66 HIM happened.   I had a ‘just ok’ swim, but I started to feel bad with about 10 miles left on the bike.   The run was awful.  I cramped the whole way, and both calves finally locked up around mile 11, sending me face first into the dirt and qualifying me for a free ambulance ride.  Game Over.

I was seriously considering that my efforts at the 70.3 distance were somehow cursed statistically improbable. 

But, just the same, Cedar Point 2013 was on my calendar, and I wanted a bit of redemption.   So, how do you come back from your first DNF?  

To paraphrase Seth, I think first you have to acknowledge that, if you do this triathlon thing long enough, you'll DNF.   It's almost certain.  So, it happens.   How do you get back up?

For me I'd first have to not cramp up and fall over...but I just didn't have time to really dig into that.  I've got a new job, and I’m training for Ironman, there just wasn't time.   So, the bigger problem was time management.  

Time Management

My two ‘biggest’ rocks outside of family life were work and Ironman training.   These two time commitments were about 60-70 hours a week, combined.   Additionally, I was spending another 1-2 hours a week figuring out which workouts I should be doing, and how I should be training.  

So, when I heard that longtime friend, exercise physiologist, PhD student, and super triathlete athlete Laura Wheatley was starting a coaching business it seemed like a good idea to solicit her help.  

 I've worked with a lot of coaches in the past.  Most of them want to talk about what an ‘art’ coaching is, and I’ll concede that it somewhat is.  Few will answer my questions when I ask why.   Fewer still have good reasons when they do answer those questions.  And while I’m not an exercise physiologist, I’m a scientist just the same and scientific process doesn't change.  Said another way, I’m an evidence based, research based, pessimistic math guy that won’t do something because that’s what your n~=50 coaching experience says works.  I’m always going to ask hard questions and expect proof, and Laura is one of the few people that have answered those questions in a reasonable way. 

So, I have a coach.  Poof, 2-3 hours free per week, more confidence that I’m doing the right kind of work, and a lot of experience I can call on as needed.  I can focus on the work, and not the planning.  Additionally, my run has been bad for a long time, and I needed a new approach to make it less bad.   Stick to your core competencies, as the business guys say.  But first things first, I now had the opportunity to invest those hours on fixing my cramping issue, hopefully for good…

On Fixing Cramping

No one really knows why cramping happens in a specific instance.  Lots of things can cause it.   It’s a multifactorial problem.   It could be overexertion, glycogen depletion, inadequate hydration, an electrolyte problem, or something yet undiscovered, and there are decent arguments around each.    It’s something I've struggled with in the past, but usually only after a race or towards the end.   A DNF based on cramping was a whole new thing.  

So, I had a complicated multifactorial problem and about 4 weeks to solve it.   The way I wanted to solve the problem was to manipulate each individual factor and evaluate.   But, that wasn't going to work.   1.  There wasn't time.  2.  How do I know that two factors aren't dependent on one another, or both on a third? 3.  I lacked a testing methodology, because the issues I experienced in racing I wasn't experiencing in training, for various reasons of which probably only some were known or guessed at.

I was really left in a situation where the only reasonable option was a shotgun approach.   Or, to quote Ripley from "Aliens," ‘I say we take off and nuke the entire site from orbit. It's the only way to be sure.’

So, I’d have to be ok with not knowing why.  I could build any number of models, related to why I was cramping.   But that’s the thing about models.   My hero statistician is George E.P. Box (What?  Everyone has a hero statistician, right?).   He says “Since all models are wrong the scientist cannot obtain a "correct" one by excessive elaboration. On the contrary following William of Occam he should seek an economical description of natural phenomena. Just as the ability to devise simple but evocative models is the signature of the great scientist so overelaboration and overparameterization is often the mark of mediocrity.”

George also says ‘All models are wrong, some are useful’ or something like that…

I think George would have been down with Ripley.   And I had to be ok with not knowing ‘why’.  

So, I overhauled my entire nutrition plan.   This time I hired yet another expert, friend and Coach Kevin McCarthy, to review my nutrition from the Route 66 half and make recommendations.   Kevin was the first to see me after the Route 66 half, and he probably had a better gauge of my physical and mental state than I did.  Laura was of course doing the same thing, giving me great and practical advice on nutrition.   She was also making some changes to my training that I felt would help quite a bit.   I also did an exhaustive amount of research on my own.   Lastly, I talked to almost every experienced age grouper I trusted, including many of my fellow Trisharks.  

Once I had a lot of recommendations from many sources, I consolidated them very, very deliberately, and with great rigor, into what would become my nutrition plan version 2.0.  This is an approach I’m very comfortable with as a data scientist.   This is a proxy for a statistical technique called ensemble learning.   If you need to develop some rules, or generalized learning and you can’t dig deep on the why, because a problem is too complex or you lack time, ensemble learning is where it’s at.  Said simply, you use the ‘vote’ of an ensemble of learners to obtain better predictive performance than you could from a single constituent learner.  (If you’re a statistician reading this, also consider that the decisions of the trees in my little live action roleplay version of a random forest was, from talking to me and their own personal experience, subject to bootstrap aggregation and perhaps boosting as well. :P )

And then I tested, and tested again, on long training days, to make sure it would work, or at least do no harm. 

This is not to say that the concept of ‘phone a friend’ is especially clever in our sport.   It’s not.  But, there is a trap us age groupers sometimes fall into.   There is danger is in reading one paper, speaking to a respected friend or coach, or even  reading one pro’s nutrition plan…and then doing what they do.   My solution to cramping was using formal methodology to avoid this trap, simple as that.

So, how’d it work?

At Cedar Point this year, despite a continued string of misfortune (race report to follow), I managed a 15 minute PR at the half distance.   More importantly, I did it without a single cramp, at approximately the same effort level I had previously raced at.  I’ll never really know what went wrong at Route 66, and that does bug me on some level, but truth be told I’d never be 100% certain, even if I had an infinite number of identical races in which I could isolate and manipulate variables.   The real world is never the lab.

Perhaps even more importantly, I stopped trying to ‘do it all’ myself and gained a team, which as a busy part time long course age group athlete, is really invaluable.   If you only get to race a few times a year you don’t have much opportunity to experiment in race conditions or train sub optimally.   

Big thanks to Laura, Kevin, and all the local athletes I spoke to, that got me this far.  Also thanks to all the professional and age group athletes writing blogs like this one, you can be certain I've data mined you all.  :)