SC14 in New Orleans, when I accidentally learned that many nerdy/geeky members of my Supercomputing (SC) / High-Performance Computing (HPC) family are avid runners/athletes, it has become a practice to look for and participate in organized athletic events in conference locations. It adds a bit more spice to and with an opportunity run with and learn from some of them, helps me extract more value from what would otherwise be a purely academic trip punctuated with delicious pit stops. Supercomputing (SC18) in Dallas, TX, was no different. As the conference date drew closer, I started searching for Dallas running races in November and found a flat-coursed event – Trinity River Run Half Marathon – outside of the conference schedule. After some trepidation (it wasn’t an inexpensive endeavor) and doing some running mathematics (training plan was calling for 16 LSD miles), I bit the bullet and signed up for the half marathon.
Great Turtle Trail Run Half Marathon was one of those events that got on my bucket list during the early formative years of my running … like 5 or so years ago. Around those days, I had wanted to do every half marathon within 6-8 hours of Houghton, if not anywhere and everywhere. I let life get in the way and I put this event on the backburner of bucket list items. Then again, the stove in those days had so many backburners that it was too easy to forget what I had on them … and needless to say, I forgot all about it. That is, until a week or so ago when Stephen Eles brought it up in a conversation, explained the course profile and expected low temperature and encouraged me to sign up!
Marquette, MI and Madison, WI, but without a formal training plan. Back then and until recently, I was basically hopping from one event to the next using the performance in one as the baseline for the next. Such an approach worked pretty well in the first few years of getting into running because there was a LOT of room for improvement – so much so that anything and everything I tried, small or big, often led to newer personal best times.
my utter unpreparedness and punish thousands more that had very diligently trained for nearly a year with unseasonably warmer temperatures (and even rain) in days/weeks leading up to the 2017 Birkie weekend. In hindsight, we (the collective phrase to represent all of us and not just the Royal plural) are quite fortunate that this lack of snow thing happened in 2017 and not in 1206 in Scandinavia. Should that have been the case, as one unknown racer put it in 2017, the Prince couldn’t have been saved, and we wouldn’t have the event in 2017 … or in any other year.
In all honesty and fairness, participating in this event was a very distant thought when the year started. Unlike 2017, I have been making a decent amount of progress towards the upcoming Kortelopet as part of the Birkie festivities. Progress, to be fair and honest, has so far been only about improving the technique – especially having to make a right turn while going down a slope. To be fair and honest, I did want to improve the distance (per session or attempt) as well but just hadn’t made enough time (or had made time for excuses, as my lovely Lombardian friends would say).
2015 and 2016 editions. And the quest (read: want) for the final piece ensured I at least signed up, and would find ways to complete it given my very limited training.
2017 American Birkebeiner (I wasn’t prepared for that either), Great Bear Chase became the final and only test of my skiing this season — cumulative (since January 2014) and newly acquired (with each passing season/session — as I said, there wasn’t much of it this season) alike. And the event is a a long-running and well established, managed and reputed one with usual perks — near-zero traveling, sleeping in my own