Saturday, July 28, 2012

I did not finish

I'm not sure where this post will take me, but as a week has now passed since the unfortunate premature end to my Vermont 100, I feel like I should write something more than the little snippet I sent to my friends with the Bull City Track Club.

I entered the race knowing the will was there, and I was pretty sure the muscles were trained, but as anyone who has run 100 miles will tell you, 100 miles is a long way, and there's no way of knowing what's going to happen on any particular day.  So I tried to keep my expectations realistic (read: tempered).  That being said, I was, let's say, about 75% sure I would finish going in to the race, even with the waves of apprehension that washed over me as race day drew nearer.  I knew going in that my body has historically not responded well to high mileage training, but reasoned it had always held together for the high mileage races, and had been impressed with how well I endured the increased mileage in training.  Spoiler alert (in case the title didn't grab you): I did not finish.

Heading back onto the trail at mile 40-ish.
Even as far as 40 miles into the race, things were feeling pretty good - the 'quad busting' downhills hadn't busted my quads, and I was receiving compliments on my awesome climbing abilities (I apparently walk uphill like a champ).  I was still flirting with the preposterous idea that I could perhaps slide in under 24 hrs even with the somewhat ridiculous number of rather steep hills (though rationally, that was stupid because factoring in Joe/Blake's 1.3x differential between the first half and the second half, I would have to set a PR for the first 50 miles).  Deep down, I figured 25 hrs was a more reasonable goal, but I was out there for a long time - I figured I should be allowed to dream a little, right?  Regardless, I still felt good at 40.  Except my feet hurt.  And I had this nagging shin-splint-y feeling on the front of my ankle/foot area that popped up around the time we trucked through a long pavement stretch that involved descending about 800 feet in roughly 1.5 miles... around mile 12.  I had kind of been ignoring it, though, because there had been other little silly problems that had come and gone with the downhill pounding, so I figured this would go away, too.

Unfortunately, this was not the case, and between 40 and 57.5 miles, the shin splinty feeling intensified until it felt like someone was kicking me with every step my right leg took.  I was still feeling pretty great on the uphills, but I was no longer able to run much by the time I pulled into the aid station at 57.5.  I had been thinking I would just pop some advil or tylenol and motor on out, but when we took off my shoe to look at it, we noticed a nice knot had formed, which was a little scary and changed things dramatically in my head.  Now we were looking at a potential actual injury that might extend my planned month off after the race to something more closely resembling the achilles tendon PT/rehab debacle of my late teens.  I still took some tylenol on the recommendation of someone who thought the kidney-failing potential of advil might be too much of a risk, and decided to walk the next section to see how things felt.  Unfortunately, after the lovely ascent, in which I actually passed a couple people, the long descent confirmed that we (the royal we) would not be running any more that day, so faced with the best case scenario of walking for 37.5 miles and sneaking in just under the cutoff (still disappointed) and worst case scenario of walking 33.5 miles, missing the cut at the last aid station, and making whatever was going on worse, I bailed in favor of a full night's sleep in a bed and salvaging the rest of a nice mini vacation.

A fuzzy picture of the ankle the day after.
I named my cankle Sam.

It was the logical decision.  I don't regret the decision.  I know I made the smart choice.  If we had been at mile 85, it probably would have been a different story, but with that far to go and visible focused swelling in the region of a tendon, there was no reasonable way to go on.

Largely unrelated, but I like this picture.

...but that doesn't mean I'm not disappointed.

...and perplexed.

It's odd, but I actually felt better at the time I dropped than I did after reading all the nice supportive things people said about 62.5 miles still being really impressive.  I don't want to sound ungrateful because I really do appreciate everyone's kind thoughts, but telling me 62.5 is really great and impressive just kind of makes me feel like a heel.  It's not that great or impressive.  I just ran 53.5 a month ago.  62.5 is not that much farther.  It is decidedly anticlimactic.  I didn't even make it 2/3 of the way through the race.  I can accept that my body fell apart and couldn't make it the full distance, but I can't accept that being counted as a successful outing.  I'm glad I made it that far, but it still was not successful.

So now I am left in a pit of confusion.  Do I try again, knowing that my body may decide (again) that 100 miles is just too much to bear structurally?  My heart leans that direction, as I'm not a big fan of failing to complete something, but my head remembers how much I hated training for this attempt.

When I stopped, I was resolute about not trying again.  My appendages sent me a message and I was going to listen.  Perhaps train for something a little more reasonable - something that I could do in ...say... a morning.  But the reverse psychology of my facebook page has me thinking maybe I should learn what I can from this one (long, steep downhills are not my thing) and try again with something a little more suited to my strengths (whatever those are - do they have 100-mile hikes uphill with no descent?) and be a little more low key about my approach.  We do have an awfully nice local 100, you know...

It's like a crazy beacon... calling to me...

Fortunately, I don't have to decide until September, but I'm just not sure how I'm going to decide.

Until then, I'm back to the trails.  I'm very much looking forward to seeing many friends that I haven't seen in a while because I had to do some outlandish, ridiculously slow run that day (all the days).  The swelling is gone and I was able to run/hike 6+ miles this morning with little more than a twinge in the traitorous tendon.  So the answer, I guess, is we'll get back to some sort of routine, and see where the coming weeks take us.

/catharsis.  Thanks for listening <3

Sunday, July 08, 2012

I ran 100 miles in one week*

I should post about the Bolder Boulder. I really should. I should back up my undying love for this race with an effusive post about how great this year was. About how the weather was perfect (it was), how the crowds were fantastic (they were), how the elite race was really interesting (it actually was), but alas, though the race was fantastic as always, I just don't have anything witty, amusing, or even interesting to say about it. I'll give the executive summary for those who are interested (bullet pointed to facilitate reading):

  • I have been training for a 100 (you know this), so I wasn't sure what 'speed' meant to my legs at this point
  • I ran faster than expected, logging my 2nd best time at the BB (hooray), feeling mostly pretty good the whole time
  • I skipped the slip n' slide (the horror!)
  • I got the massage (was awesome)
  • The expo was lovely as usual - we may or may not have made 3 trips to the free popsicle booth and there was an ample supply for everyone else to do the same
  • We got to meet up with our super awesome friend David to watch the elite race
  • It was too windy for the skydivers (massive bummer - the Memorial Day festivities are not nearly as cool without them)
Overall, a really nice day - definitely a nice iteration of my favorite holiday.

 It was, however, decidedly uninteresting compared to my feat 2 weeks later, which was to run 100 miles in one 7-day period.  Now THAT was epic.  Now, I mocked Ronnie when he did his 100 mile week last year, saying "Wow.  You ran 100 miles in a week.  You know you're going to have to do that in a day in Utah, right?"  But truth be told, jamming 100 miles of running into a week is kind of tricky.   
I can't really say if there was no gas that week,
but it would be awesome if it was true!

Now, I have to admit I kind of cheated because, due to my travel setup and my father’s work schedule, I did my weekend long run from the week before on Monday.  Thus, with a 42-miler on tap for the following Sunday, I really only needed 30 miles in the other 5 days to make it happen.  When I tell people this, they unfailingly point out that this doesn't matter - I ran 100 miles in 7 days.  That's a hundred mile week.  I still feel like it should get an asterisk, though.  Anyway, asterisk or not, it was still a big deal for me, so I feel compelled to share how it played out:

Monday – 27 miles in Denver.  Started at 6AM - ~60 degrees.  Finished at ~10:30AM - ~80 degrees.  Also, I forgot that the last 10 or so miles were going to be paved.  And have no shade.  Oops.  Regardless, I made it.

Tuesday – 0 miles.  Yes, I had an off day in my 100 mile week.

Wednesday – 6.5 miles at Fullsteam.  Got there late, had to sprint to catch up, short cutted (made up for it by parking way far away).  Got my 6.5 in, though, so all was well.  Also, my semi altitude-adjusted legs probably helped.

Thursday – 5 miles – usual run with Nancy – all was well.

Friday – Walked to work and back.  Had to take an outlandishly indirect route to get 8 miles in total.  Yes, I know that walking is different from running, but I sure will be doing both in Vermont, so I’m counting it in my weekly 'running' mileage.  Also, it's not like I ran all 42 miles of Sunday's run, so yeah.

See where those circles are?  Imagine someone
stabbing you right there over and over again.  That's what it felt like on Saturday.
Saturday – OHMYGOSH - apparently you use totally different muscles for walking and running.  My rear end was SO sore.  SO.  SORE.  Still did my 12 singletrack miles in Umstead as planned.  Felt pretty good when I cut out at 2 hrs, but definitely had a heavy sense of impending doom regarding Sunday (and was praying to any god that would listen that the shooting DOMS pain in my a$$ would go away (literally) overnight.

Sunday – 42 miles on the ‘triathlon of pain’ course.  Sadly, my prayers from the day before weren't entirely answered and lap 1 was decidedly uncomfortable.  Ronnie was a trooper in putting up with my whining, but I was feeling a bit apprehensive about laps 2 and 3, where the role of Ronnie would be played by Mandi, who I didn't know as well, and who was apparently showing up on a mission to get me through these two laps 'on pace'.  Oh dear lord.  The theme for lap 2 was heat.  Also, apparently horseflies like Mandi better than me.  Sometime toward the end of lap 2, my feet and quads told my butt muscles to quit their bitching, which was nice - things still hurt, but it was a nice change of pace.  Managed to manipulate myself a break halfway through the third lap by becoming enthralled by the insect ecosystem that had set itself up on a pile of horse doody.  It was super interesting to be sure, but really I just wanted to sit down.  Picked up Brandy about halfway through Turkey Creek and together, we all shuffled our way back around toward the cars, where I passed the 100-mile mark for the week.  Mentally self-fived myself because a physical self-five would take too much energy, braved a swarm of yellow jackets to refill my water bottle, and shuffled back to the car to celebrate with some nice watermelon.  Whew.

So ended the epic 102-mile week.