Monday, December 22, 2014

2014 in numbers

We managed to log one last dirt ride for the year before we head to Fairbanks this week — eight hours of soupy fog and equally soupy mud. The California drought and an attitude that "rain is running weather" has almost completely desiccated my patience for mixing bikes with mud. Hours of splooshing through a cold goo shower is just so much better when you don't involve a fast-moving, difficult-to-clean mechanical object. But I wanted to squeeze in a long ride this weekend, as we're now just three weeks out to the 200-kilometer snow bike race. Beat and I rode with our friend Jan, who had a great attitude about the grimy day. "How many times do you get to see Skyline like this?" he said, referring to fog so thick we could barely see a few meters in front of us. As I remember from March 2011, if we have a more "normal" winter ... actually, a lot.

From a "pre-holiday-party run" along Russian Ridge on Saturday.
Plugging the ride into Strava started me thinking about my "year in Strava." This is the first year I've used GPS fairly consistently to track rides and runs, which means I have a nearly complete record of my training data (the GPS did stay home from time to time.) I can be a numbers geek with the best of them. Although I don't place high personal value in my statistics (because statistics do not tell very good stories), and although I can't make much use of them because I have little interest in a structured training plan, I still have fun tracking these details. I'm glad I managed to record my activities consistently through 2014.

I thought it would be fun to crunch the numbers for 2014. I realize the year is not quite over, but like most people, my free time will be limited over the holidays, so winter solstice it is. Hikes are included in the running totals, because in my world there isn't that much of a difference between running and hiking — either way, I am trying to move in the most efficient way possible in regard to terrain, distance, and elevation change. Usually my effort levels are fairly consistent regardless of pace. Cycling is both road and mountain biking. Strava doesn't distinguish between the two.

Cycling:

Distance: 4,557 miles (including RASA)
Time: 321 hours, 13 minutes (not including RASA)
Elevation gain: 478,196 feet
Rides: 92

Running:

Distance: 1,570 miles
Time: 394 hours, 46 minutes
Elevation gain: 282,608 feet
Runs: 140

Cumulative distance: 6,127 miles

Cumulative elevation gain: 761,227 feet

This section of the Skyline Trail opened to bikes in November, but remnants of past discrimination linger.
It was a good year. Not even including the moving time within 21.5 days of the Race Across South Africa, I spent 716 hours on the move. That's the equivalent of 29 days — nearly a month. Some will undoubtedly ask, "Why do you spend/waste so much time training?" My answer is simple: I am consistently the most happy when I am moving through the world. Even better when I am moving through the world under my own power. In 2014 I had the privilege to spend more than one twelfth of the year in this happy place — in addition to a variety of other great experiences. Yes, 2014 was pretty fantastic. 

The month-to-month breakdown tells a better story, because there are some wild variations to the numbers. In January and February I was simultaneously training for the Iditarod Trail Invitational and the Freedom Challenge — so loaded cart pulls and long mountain bike rides. March was mostly snow biking in Alaska followed by the White Mountains 100 at the end of the month. April and May were highly training-focused with many hours on the bike, and June was the Race Across South Africa. July was a recovery month, although with Tor des Geants on the horizon I embarked on some long hikes. In August I increased the running mileage. Early September was the Tor des Geants, which ended in an LCL tear in my left knee, followed by four "zero" weeks. Once my knee started working again in October, I ramped up the bike mileage quickly, and started walking and then running again in November. I was lucky to get away with increasing my mileage as quickly as I did after my injury. I believe having a solid base of high-mileage conditioning helped. I also really did take all that time off, and my knee had a fair chance to heal. 

Beat looking good during a day of playing in the mud. 
The breakdown: 

January: 
Bike: 511.3 miles, 50,334 feet gain
Run: 195.4 miles, 35,010 feet gain

February:
Bike: 78.7 miles, 9,718 feet gain
Run: 456.6 miles, 33,233 feet gain (Iditarod Trail Invitational) 

March:
Bike:  327.8 miles, 16,388 feet gain (White Mountains 100)
Run: 28.8 miles, 1,349 feet gain

April: 
Bike: 490.9 miles, 61,936 feet gain
Run: 110.5 miles, 19,544 feet gain

May: 
Bike: 647.1 miles, 72,110 feet gain
Run: 137.8 miles, 27,270 feet gain

June:
Bike: 1,450 miles, 121,391 feet gain (Race Across South Africa)
Run: 19.5 miles, 5,866 feet gain

July:
Bike: 33.2 miles, 4,380 feet gain
Run 108.5 miles, 23,625 feet gain

August: 
Bike: 183.9 miles, 23,822 feet gain
Run: 169.7 miles, 48,323 feet gain

September 
Bike: Big fat zero
Run: 133 miles, 48,615 feet gain (almost entirely Tor des Geants)

October
Bike: 494.6 miles, 59,632 feet gain
Run: 12.4 miles, 1,824 feet gain

November
Bike: 263.7 miles, 39,423 feet gain
Run: 93.4 miles, 17,927 feet gain

December so far
Bike: 155.2 miles, 21,893 feet gain
Run: 119 miles, 22,172 feet gain

Some bloggers ask questions at the end of their posts. This is one I'm curious about. Do you track your outdoor/training activities? How do you feel about your "year in numbers?" 
Wednesday, December 17, 2014

Almost like a comeback

 I was a bundle of nerves about this 50K on Sunday, which Beat found hilarious. "How many of these have you run now?" he asked. I've lost track of my official 50K number, but I guessed I could still count the number of times I've run a Woodside event. Three different race promoters offer two events here per year, so one rolls around seemingly once a month. It's gotten to the point where the question, "What do you want to do this weekend?" can be frequently answered by, "Let's run that 50K in Woodside."

I tallied each one I could remember. "Seven," I answered. "I think this will be my eighth Woodside."

Beat and I like to participate in these events for the same reasons people go to their favorite restaurants. They're fun social outings in a familiar and pleasant setting. We get to indulge in an activity that releases a surge of mood-elevating neurotransmitters like serotonin and endorphins, and drink ginger ale in a setting that elevates the taste to something like unicorn tears (Oatmeal reference.) There are friends to visit and fun people to meet. I always enjoy these events even through occasional discomfort and nagging pains, which are as natural to a trail race as indigestion at a French restaurant. But after a June bike tour across South Africa, a tight recovery period, a failed hiking race in the Alps, and a subsequent injury, it had been more than six months since my last long run, and there hadn't been all that many miles of actual "running in between. I didn't really care about going slow at Woodside, but I was scared of my LCL giving out, or buckling my knee, or IT band agony, or damn it, tripping and falling — because eating dirt is the source of nearly every running injury I acquire.

 To get my mind off pre-race jitters, Beat suggested we take the fat bikes out for a Saturday afternoon ride. He recently installed a 1x11 drivetrain on Snoots that I needed to test out, as well as contemplate gear distribution and handlebar position for the real adventures this winter — the 200K snow race in Idaho, which in itself is just a test ride for a 250-mile tour on Alaska's western coast in March. This plan is actually scary, as opposed to the Woodside Ramble 50K, which was only scary in the ephemeral sense of fleeting pains and ego-trouncing poor performances. I'm glad there's something to keep it all in perspective.

This was the Woodside Ramble 50K, somewhere around mile 15, where I was thinking, "I'm about ready to be done running now. Yup, just about ready to be done." The first ten miles actually were quite fun, and I was buzzing with happy hormones, but I admittedly started out too fast relative to my current running fitness. One problem with running a similar course eight times is knowing exactly how well I *should* be moving at any given point. There's also the fact that even with 5,000 or so feet of climbing and sections of roots and mud, Woodside is 100 percent runnable on fresh legs. So it's difficult not to berate myself for any walking, of which I did a fair amount.

Beat loves to stroll and chat during this race, and I caught up to him near mile 19, as he and his friend Tony were distracted by shared tales of past derring do. "It's all going okay," I told Beat. "But I'm working really hard for this. It feels a lot harder than usual. My hamstrings are super tight and I'm fading. I'll have to take the descents slow."

After some stalling at the aid station, Beat surged ahead and I loped along the Skyline Trail, which is my favorite part of this enjoyable course. The trail slices a narrow path along steep slope beneath towering redwood trees, winding in and out of drainages on a rolling traverse approximately a hundred feet below Skyline Ridge. Except for aforementioned sections of mud and roots, it's not all that technical, but steep drop-offs always keep me extra vigilant on this section. Despite this focus, around mile 21 I still managed to put my right foot down at a point where there was nothing beneath it. I actually ran right off the trail, in a spot where touching down on the 45-degree-plus slope could easily result in a tumble that wouldn't end until my ragdoll body slammed into the broad trunk of a coast redwood. Somehow, the side of my foot caught the edge of the hill a few inches below the trail. I instinctively rolled my ankle to dig in some toes before setting my left foot down on safety, then flailed dramatically to the left until I had both hands punched in the mulch on the steep uphill slope.

Damn, that was close. Here I am, scared of Alaska, when I'll be lucky to survive the Woodside Ramble.

And if you're wondering whether I'm still concerned about potentially worsening problems with coordination. Yes. Yes I am. I have no idea how I stepped off such a simple trail when I was deliberately focusing attention not to do so. It's still impossible to make any tangible connections to an ongoing tally of incidents. But this one left me rattled for the final ten miles, enough to not think too much about my searing hamstrings. Either way, the downhill miles were slow.

Still, the left knee and LCL performed perfectly, until that night when it was sore in the same spot that had been injured. There were a few disconcerting hours of "what have I done?," but it proved to only be superficial soreness and was gone the next day. I went out for a four-mile run Tuesday afternoon without incident, and despite 25-mph winds and rain, I managed to not stumble and fall, not even once.

It's continued to be rainy and gray all week — which I'm also enjoying as a welcome change — but the sun came out for the half day on Sunday and we enjoyed perfect weather for the Woodside Ramble. Afterward the race organizers put out a delicious spread of fresh fruit and other snacks. I was ready to sit down and stuff my face, but Beat finished ten minutes earlier and had become so chilled in the interim that we couldn't stay long — not even long enough to pick up my age group award (third! heehee.) I didn't tell Beat about my stumble because I was deeply embarrassed about it. It's kind of funny, actually, how I can be so embarrassed about something and yet feel no qualms about blurting it out to the whole world on my blog. Funny indeed. (Sorry Beat.)

Turns out anything can be treacherous, therefore every day is an adventure. I'm glad there's something to keep it all in perspective. 
Friday, December 12, 2014

Cry me an atmospheric river

Where did this week even go? I've been wrestling with two writing projects, in that sort of phase I think most people can relate with — the phase where everything becomes drivel and I need to step away for a while before the whole project is slashed and burned. Journalismjobs.com is a good diversion, a place I like to go to daydream about landing angst-free copy editing contracts that let me work on my own schedule. Twitter can erase a surprising number of minutes as well, for shouting at random into an echo chamber.

A college friend, Craig, came to visit from Alaska. We spent the weekend in the city doing city things — tapas at a Mexican restaurant; an afternoon at the de Young Museum of fine art; getting our exercise by walking eighteen blocks from the place where we actually found parking; being coerced into buying a 100-pack of fancy jasmine tea I didn't even want because, well, someone like me really shouldn't enter shops in Chinatown; late nights with other old friends talking about the best days that were now 15 (!) years ago; and attending the lively and harmonic Sunday services at the Saint John Coltrane African Orthodox Church (Craig is a Mormon, but joked it was fun to spend one Sunday worshiping the sound of saxophones.)

I finally booked all the reservations for Fairbanks at the end of the month, and became immeasurably excited about Christmas.

Somewhere in there I remembered I needed to train a little for this 200-kilometer snow bike race in Idaho that's just a month away. After a weekend getting fat on tapas and dumplings, I lumbered outside on Monday afternoon to climb the best tear-inducingly steep roads near my home. Redwood Gulch (ouch) to Skyline (tell me that doesn't start to hurt after 3,000 feet) to Montevina (2,000 more feet of !!!) The tires cut like knives into the mud as I ground the road bike over Montevina's dirt section with the fading light, then nearly burned out the rim brakes on a pitch dark, damp pavement descent down Bolman. There was a certain exhaustive quality to this four-hour ride that left me dangling on threads, but I was glad to put in some saddle time before the storm.

The storm. "Hellastorm." Also "stormaggedon" to the Twitterati. A forecast for a particularly strong flow of atmospheric moisture was played up heavily in the local media, and I'm not sure anyone thought it would live up to the hype. Everyone likes to joke about how Californians can't handle weather, even Californians. Even I shook my head and recalled past days of weathering "typical" storms in Juneau — being knocked off my feet by wind gusts on Gastineau Ridge, full days of constant rain, nearly swamping my car on inundated roads dammed by piles of slush, spending on evening on a moored boat on Juneau Harbor as 60-mph gusts rocked the vessel violently against the dock. There was no way hellastorm was going to be that bad.

However, it sort of was. Locally there was widespread flooding, flash floods, 80 mph gusts recorded on nearby peaks where I ride my bike frequently, and, as of 6 p.m., 3.93 inches of rain had been reported at the nearest weather station to my house, since midnight. I used to track weather reports religiously when I lived in Juneau, and I don't think I ever saw a 24-hour total over 2.5 inches. If 3.93 inches fell in downtown Seattle, it would be the second wettest day in recorded history for that city. (Juneau's record single-day rainfall is 17.38 inches. So yeah. There's that.)

But yes, stormaggedon made a dent. Even amid three years of exceptional drought.

Of course, I made a big deal about going for a run on Thursday afternoon. Not because I thought we would assert any semblance of Californian badassery by going out in hellastorm, but because I thought it would be hella fun. I even put in extra effort to pick up Liehann at Google, braving standing water and multiple collisions on Highway 85, just so he could join. Liehann, Beat, and I hit a nearly abandoned Rancho San Antonio park for good splashy lunchtime fun. The gustier wind had calmed, so we weren't too worried about trees falling on us. But there were a lot of trees already down, including two elderly oaks that we simply couldn't climb over or find a way around without risking a high-consequence hack through poison oak. Trails were inundated by shallow streams that carved deep ruts into the surface, and puddles were sometimes shin deep. Creeks that are usually dry gushed with brown rapids, and the hills were a vibrant shade of green, when prior to Thanksgiving the grass was so dry it was gray. This was the most fun I've had with running in a while, and I've been having a lot of fun with running since I took it up again post-knee injury.

Beat and I signed up for a 50K run in Woodside on Sunday, which is admittedly not a great idea since ten miles is the longest run I've completed since the Tor des Geants debacle in September. But I'm so stoked on running right now that I just can't let it go, even with that Fairbanks trip and the 200K fat bike race on the horizon. Beat expressed strong disapproval at my desire to go snowboarding in Utah, citing high-consequence injury risk, but he's surprisingly nonchalant about this 50K. Of course I don't intend to jeopardize winter plans; I'm not above quitting a 50K at the slightest tinge of knee pain. But I'm unabashedly looking forward to this Sunday run, especially since it's supposed to be nice and sunny again.