Sunday, October 16, 2016

Oh fer cute, Strava

I started using Strava and Training Peaks, having found the charger for my gifted-to-me Garmin Forerunner 405. With one fell swoop I stopped logging my runs in logyourrun.com (which requires a manual upload of gps-watch data) and just let Garmin's Connect app sync with Training Peaks, Strava, and my employer's get-fit incentive program handle my data/training logging and uploading.

I'm using both apps' free versions right now, but Training Peaks gives you an initial free trial of its premium edition ($119/year). There is tons to love about the premium version - making it easy to dive into maps, data, its proprietary fatigue/fitness/taper graphs and algorithms (which I loved to view). Planning workouts is wonderful - it's the first app I've ever seen that will allow you to see a) what you planned to do; and b) what you actually did - in a single spot. It's something that I never really figured out how to do well within a single Google doc, for example. And a web app like Logyourrun doesn't allow for such capabilities - it's data entry only, no analysis or planning. 

The basic/free edition of Training Peaks is very stripped down. Gone are the proprietary graphs and algorithms (except their TSS - training stress score) that showed your acute and chronic training load. Gone is the ability to plan workouts in the future (my favorite feature of the app); you can still enter them same-day, but that defeats the purpose of using it to plan out a week, month, training cycle, or an entire season. For some reason I really miss their proprietary graphs, etc. - it was a nice analysis of what I was doing for training. I had been given something which I never had (or really needed?) before, but now it was gone and I wanted it back ROAR!

Strava is an odder duck. It is like Twitter for athletes with its activity feed. It asks users to be and create content in the form of segments, like Facebook. And it contains some analysis tools (at least in its free version) that look similar to Garmin and Training Peaks - mostly maps/graphs of distance, pace, elevation, heart rate, etc. But most of its analysis tools and its propriety measure of run difficulty (Suffer Score - a ridiculous, clickbaitable term) appear in the premium version. 

My biggest gripe is with Strava's segments, however. When used properly, it allows athletes to compare themselves to others in a "who can run from X to Y faster" type of setup. It also allows a runner to compare progress overtime. 

But. 

And it's a big but.

The comparison tools are only useful if we're comparing apples to apples - take any athlete, and compare how they run a certain segment at a given intensity, to another athlete running that same segment at the same intensity. I may appear lower on a Strava segment leaderboard - not that I'll ever top one - because I run easy or endurance-pace runs on areas where someone else was doing an interval/tempo/threshold workout. My efforts on those segments will seem artificially low. 

And then there is the constant competition aspect of segments. My twitter exchange with runner Devon Yanko below illustrates this. 
Finally, you have the people who through ignorance or intent, screw with Strava leaderboards. There is a whole Twitter feed dedicated to these shenanigans: @StravaWankers.

StravaWankers is an attempt to point out, ahem, publicly shame, those who log workouts/runs/etc. while commuting to work via airplane, those who leave their workout on "run" when they hope on the bike. But one example: 

Oh, fer cute, Strava.

Friday, September 16, 2016

2016 Superior Fall 50 mile: By the numbers

First the data: my 13 hr pace chart and my splits for the same race, plus analysis is at this link.

A couple notes of the chart. This pace chart was initially created so that I would spend 45 percent of my time in the first half (or so) of the race and 55 percent in the second half (or so) of the race. The aid station at Cramer Road is at mile 26.7 of the 52.1 mile event, so its 0.65 miles past half way. Based on that, I was trying run a 5:51/7:09 split between the halves. 

My actual splits and elapsed time are in the ACTUAL (ELAPSED) and ACTUAL (SECTION) columns. The DIFFERENCE (ELAPSED/SECTION) columns compare my actual elapsed and section times, respectfully, with my estimated elapsed/section times. Negative numbers indicate I was under my estimate, positive means I was over. 

The three columns to the right are a feeble attempt to compare how difficult (in-race, not had each been run individually on fresh legs) each section is by comparing my actual race times as a percentage of the finish time to the section distances as a percentage of the total distance. A negative number means I took less time in a section that its proportionate distance, a positive means the opposite. Note the limitations of this data, as it does not control for elevation changes or terrain. 

With that, some observations: 

I ran a more even race than anticipated, with a 47.7/52.3% split front to back as a percentage of total time. Looking at the first half data, this was primarily a function of my effort to get to Cramer, which was off by a full 15 minutes (almost three minutes per mile slower than anticipated). I went through a rough patch in-race during this section, and hiked more than I would have liked. 

I was about 0:45/mile slower than anticipated in the Crosby/Manitou section, and was pleasantly pleads with that effort. No issues there. 

The second half was run remarkably faster, with two consecutive sections being run a full 11 minutes faster than anticipated, the sections to Temperance (1.5 min/mi) and to Sawbill (2 min/mi). Both of these sections have given me fits in the past. The Temperance section is split into three parts, with the second part traversing the Cross River and the third part climbing out of the Cross River and up and over the hills and down into the Temperance River. This second part is technical and hard to run quickly, and the third part is a climb and descent that is generally exposed and dusty. It crushed my dreams in 2013 when I came into the Temperance aid station incoherent. The section to Sawbill is relatively gentle, but contains the long haul up, around, and down Carlton peak. This section kicked by butt in 2015 because the climb up is exposed. 

The section from Sawbill to Oberg is far and away the easiest section in the entire course (including the 100 mile course), but this year it was full of mud and muck, making the going slow. I was nine seconds off my goal time for this section nonetheless. Finally, the section into Lutsen felt slow in-race because getting up and over Moose Mountain felt like a slow slog, but again I was but a few seconds off (48) for the overall section time. 

Race report coming soon. 

Monday, May 30, 2016

Cup of stress

I learned long ago that I can only have one hobby. Running is that one hobby, and it is the best of all possible choices. When I can't run, some other distraction percolates up from the recesses of my brain to take its place. Possibilities include chess, reading (which I should be doing anyway), writing (same, whether fiction or this blog, or something professional, like an article), a computer game I have dedicated hundreds (thousands?) of hours to since ~2001ish, or something else that my mind becomes obsessed with, etc.

I also learned long ago that I cannot have more than one hobby. I cannot maintain running while imposing other hobbies. There is only so much time in the day not already dedicated to family (primarily as husband and father - two separate, distinct roles, regardless of however intertwined they are - but there is also son and brother) and profession. 

Occasionally I agree to take on additional roles. I recently was elected to the board of the alumni association for the staff of a scout camp that, in one role or another, I attended/worked at for 13 summers. Some of my closest friends are those who I worked on staff with; they were in/at my wedding, and I was in/at theirs. I threw my name into the hat at the election, time commitment be damned, because of how much the camp gave me. I can give something back to ensure that it is around in the future to do so much good for others like me. 

Every one of these roles - husband, father, son, brother, attorney (trial lawyer), runner, board member, etc. - cause, in their own ways, stress. This is not a bad thing in and of itself. In running, training stresses the body to achieve a fitness response. That three-hour long run stresses every part of the body so as to improve overall fitness. A jury trial stresses the mind and makes me a better advocate. Being a parent and husband stresses every system so as be the best father I can be to my son, however taxing, and be the best spouse I can be to my wife. How the body responds to stress, and adapts to it - whether becoming a more athletic, responsible, or patient person, e.g. - is the benefit of this stress. 

But the body can take only so much stress. We have a reservoir, like a cup, in which to put stress. We add volume to that cup by all of our activities. We take stress out by getting enough sleep, taking appropriate relaxation time, eating real minimally processed foods (not too much, mostly plants) and appropriately recovering from our stress. A banana and a glass of milk post-run does wonders for recovering from said run, for example. 

The cup of stress can overflow. This happens because there is simply too much stress - another activity or stressor has been added, and the input into the cup of stress is too great - or with insufficient recovery - not eating well, not relaxing enough, not sleeping well. I get irritable, cranky. It tends to be a vicious cycle. When I am stressed at work, I tend to wake up in the morning with my calves balled up in knots. My sleep is less restful, and the recovery benefit I gain from it is reduced. My diet goes south, my weight and body composition changes. Etc.

The end result is that one of my roles gets dropped. More often than not, running gets dropped. Why? Without running, I sleep more. No more 4:45 AM weekday wake-ups, or earlier on the weekends if I'm going long at Afton, for example. No more quick runs post-dinner, or being exhausted in an afternoon after a 20-mile jaunt on a weekend. The time needs to be devoted elsewhere.  

This spring, I broke the "one-hobby-at-a-time" rule, and my cup of stress overflowed. I was asked to teach a university course on very short notice, just a few days before the semester was to begin. The course was taught in the evenings twice per week, but given prep time and grading materials, most weeks I dedicated three or four evenings per week to it. Grades were due this past week, and I made a huge push to review submissions, final project sets, and grade finals.

Teaching caused my cup of stress to run over. Running was the casualty. I stopped running in the morning. My evenings were occupied with teaching, preparing, grading, or being a father/spouse to make up/ensure the quality time that I was otherwise missing on the evenings I was on campus or otherwise occupied. Or the non-teaching evenings were spent relaxing, again to make up for the time I was otherwise missing. 

On Saturday, I will toe the line at the Kettle Morraine 100 for the second time. Last year, I dropped at mile 80 after chaffing badly for the previously 30 miles. I have no business starting this race. I have done only a handful of runs that could count as long runs. Two of those were races, each which I finished with relative ease under the conditions but knowing that I was nowhere near my regular fitness level. It reminds me of this: 


That's where I am. Undertrained. What hangs in the balance is not just a DNF, but missing the WS lottery and having to re-set my ticket count back at one for the 2018 race (instead of having two tickets in 2017 and four in 2018, etc.). 

I've faked my way through 50K and 50 mile races before, and I've been running ultras long enough to know how to get it done when the chips are down. So maybe I'll finish - time and ugliness be damned. 

Maybe I won't. Maybe the fact that this is 100 miles will do me in. Hundred milers are completely different ballgames than their shorter cousins. They require purposeful dedication and the payment of one's dues in respect and adoration for the distance. Maybe my mind has written a check the body can't cash. 

"This just is," Ed Sandor wrote in his 100 Mile Lessons. I read and re-read that list before almost every ultra, and also when it inevitably pops up in FB when someone asks for tips on finishing one of these endeavors. It calms the nerves, prepares the mind, and sets the attitude. These races are run in the gray matter between one's ears, not underneath one's footfalls.

This. Just. Is. 

I'll finish, just you wait.

Friday, April 15, 2016

2016 Zumbro Midnight 50: in a race without expectations, complete satisfaction obtained

This is not a report about suffering. Or injury. Or haste. My Zumbro was none of those things. 

My Zumbro was not a race. It was a run. A run without expectations other than to finish. 

My thoughts on pacing were low going in Zumbro. I had less than 400 miles on the legs year-to-date, and only about 700 miles season-to-date since I started running again around Halloween 2015 post-ankle sprain. I hadn't done many long runs - no trail runs over 20 miles or four-ish hours, and I did a single ~25ish mile pavement run with a friend a few weeks before the race. That run was about her, at her pace, and for me the benefit besides the company was the sheer time on the feet. Normally, I would have liked to have done a 50K trail run as prep for a 50 mile race. That didn't happen this year.

By comparison, when I started 2015's Zumbro Midnight 50, I had ~1,030 miles on the legs, my miles and number of runs/running days was much more consistent. Last year, I considered myself in the best ultrarunning shape of my life when I ran my first sub-five-hour 50K at Afton during a training run three weeks prior to Zumbro. I thought a finish between nine and 10 hours was doable last year, this year I was shooting for something between 10 and 11 hours. 

I got to Zumbro late Friday morning and helped out at the start/finish aid station and as-needed throughout the day. The temps floated around freezing, and it had been snowy, windy, and cold. I walked around camp with long underwear on under my pants and four layers on top: long sleeve top; sweater; puffy vest; puffy hooded jacket. The evening drew near, temps dropped another five or so degrees and I threw on my softshell jacket on top of my jacket - to hell with compressing the insulation, I thought. I was also thankful I had my mukluks in the trunk of my car. The inside of my old inov8 Gore-Tex-lined boots were wet with sweat and they're really too narrow promote good circulation and foot warmth. So I put on my mukluks (still stored in the car from winter) and my feet were pleased. Several others were walking around in winter boots, too. 

After the sun went down, I was glad I was not running the 100 miler. As I worked the aid station Friday night, several of the runners that came in finishing their third loops started to look haggard and broken. They were cold and exhausted, their minds - and therefore bodies - beaten by the course, wind, and temperature. I told the race director that I expected carnage from the 100 milers at about 1:30/2 AM due to the cold temps. 

The carnage started earlier than I expected. Once it was dark, three or four 100 milers walked in and immediately turned in their bibs. They could not be convinced. They could walk straight, talk coherently, and ingest food and fluids, but they refused to continue and offered up their numbers and bibs to someone, anyone, who would take them. I happened to be there.

My pre-race jitters started at about 11 PM. I paced around the dirt roads of the horse camp full of food, a warm-up of sorts. 

Once the race started, it was uneventful. With a couple exceptions, I spent less than 15 seconds in each aid station. That time was spent deciding what to eat (answer: real, (solid) hot food of quesadillas, grilled cheese, noodle soup and non-hot food of lots and lots of PB&J's), deciding what to drink (answer: soup broth; Coke; coffee; and a single ginger ale, each as necessary), and walking out of the aid station food and cup of some liquid in hand. I drank less than a bottle of water on the first loop, but wasn't concerned about dehydration due to the cold temps. 

Lap one was done in 3:20ish; I was out in less than two minutes after re-loading my pack with Clif blocks. The effort on this loop was consistent. I was constantly thinking about the small inclines throughout the course: Can you run this on the third lap, I asked myself? If the answer was "no," I wouldn't run it now. Occasionally I lead a train of runners, but mostly I ran alone. I passed numerous people as they loitered in aids. 

Lap two was significantly colder - we were getting to the heart of the morning, and the loop took four full hours, despite feeling that I was traveling at a consistent effort. I wore my hat, a buff around my neck, and gloves plus mittens for most of the entire lap. Temps hit the mid-to-high teens, I estimated, and I only occasionally felt cold in my forearms (where I had a single long sleeve covering; my core temp was never an issue).  In reality, the pace was so much slower in the first three quarters of the lap, as I started to see the light of the sun under the horizon as I ascended to the overlook after aid three. The pace started to pick up when I hit the road. It was full-on daylight now and there was just four miles between me and the final lap. By now, the necks and tops of both of my bottles had long-since frozen, and I was forced to get my fluids only at aid stations. I was not concerned about this; it just is, I told myself. You can run for a long time without fluids, and you'll make it to an aid eventually and be able to fill up. 

I came into the start/finish at around 7:20 AM. I contemplated jettisoning my frozen bottles, but decided to melt the ice and go from there. I was glad I did, as the last four miles from the road to aid four to the finish was done under a warm sun. I swapped to two dry shirts (again, one short sleeve and one long sleeve, but the long sleeve was thinner here) and turned my wet fleece skull cap inside out. I still had the mitts, but the hat and mitts were soon bundled up and permanently placed in my vest. It was still cool, just above freezing for a long time, and I rotated with my gloves on and then off, and my buff on and then off, each as temps dictated. 

I pushed hard on the that last lap, going as hard as I could, and not wanting to succumb to the distance or to any sufferfest. So I ran the flats and downs and as much of the gentle ups as I could, knowing that I needed to leave it all on the course. I passed Mark Smith and the 100 miler he was pacing as I ran down into aid two, and for the most part ran every runnable step of the race, and especially the last lap. Due to running hard, the elements of the course - I have now done 12 laps there - came quickly and without my constant gazing into the distance wondering when, for example, Carlton Peak would show up - something that I often look for when running the 50 or 100 at the Fall Superior races. I knew I had the race in the bag when I hit the road, and I pushed the pace to the pace where I was breathing hard.

I was passed by only a single person on that last lap -  the winner of the 17 mile race - and finished in 11:02:31. I had done the last lap in approximately 3:40. I took 26th. 

I was most pleased with the effort my body was able to put into the event itself. I was, from my perspective, undertrained. But I used my now-eight years of experience running ultras to run a smart, conservative race and push hard for an extended period of time (really, the last 20 miles). These things don't get easy, but they do get easier once one clears the learning curve that is running for hours and hours on end and dealing with sleep deprivation. 

Stray observations

Starting a race on a looped course in the dark and running about one-and-a-half loops before sunrise does weird things to the mind. When I hit the pine tree tunnel on the third loop between the start/finish and aid one, I realized that while I had run through the area twice before (because I remembered what the dirt looked like), I had no idea on laps one or two that I had gone through the tunnel. Headlamp-induced tunnel vision. 

My iPod gave out at the last aid station, and I didn't start it until about 10 minutes into the race. I listened to podcasts from NPR (Fresh Aid; Dinner Party Download; Radiolab; Embedded) and one decidedly not (Dan Savage), and the intellectual nature of them was a nice way to keep my brain focused on something else other than the running.  Last year, the iPod was filled with rock and thrash metal and it gave out when I hit the road on the third lap (with about four miles/one hour to go).

I have now done 12 laps of the 16.7 mile Zumbro course. 

The Ant Hill did not suck on any loop, and I did not break a toe going down it this year. 

Five of my toenails have evidence of trail running. Five do not. 

The toenail on my right big toe was not injured, a rarity for races of 50 miles or more. The toenail on my left big toe did have blister underneath it, and it may have partially separated from the bed. I pulled it off today. 

I was going to use Atra's removable rockplates in my Superior 2.0's, but decided not to about an hour before the run started. Nothing new on race day, I thought. I'm glad I didn't. The course is not rocky, save the Ant Hill, and the plates, however thin (<1mm) take up valuable vertical space in the shoe. 

I ate a lot of cheese during the run via quesadillas and grilled cheese. I don't think I've ever eaten dairy during a race (maybe once on a hamburger?) prior to this. 

My stomach was mostly solid, save one time coming into aid 3 on loop 2. I had been putting lots of acidic things into it - Clif Blocks, mostly, plus Coke and the jelly on PB&Js - and needed to eat something that wasn't acidic. Ended up grabbing some M&M's and a quesadilla and walking out. 

Bacon, eggs, and sausage at the finish line hot off the stove was the most amazing immediate post-race meal I've ever had. Kuddos. 

Gear:
  • thin fleece skull cap -> put in pack during loop 3
  • RSR buff (x2 or x3?) (used one as neck gaiter loops 1 and 2; used dry one as primary headgear loop 3)
  • Patagonia Capilene 1 short-sleeve shirt (loops 1 and 2)
  • Patagonia Capilene 2 Quarter zip long sleeve short (loops 1 and 2)
  • Patagonia Forerunner short-sleeve shirt (loop 3)
  • Patagonia Capilene 1 long sleeve shirt (loop 3)
  • Patagonia Houdini windshirt (in pack not used, but glad I had it)
  • Timex Ironman watch
  • iPod shuffle
  • Craft winter running boxer briefs /w strategically placed windproof panels from TCRC 
  • Patagonia running tights
  • Fitsox Isowool Trail Cuff socks x3 (wore one pair throughout; had two more in drop bag)
  • Altra Superior 2.0 (2016 model)
  • Black Diamond lightweight fleece gloves
  • Scott winter running mitts, size L/XL (for over gloves)
  • Ultimate Direction AK 2.0 vest /w UD bottles
  • ~8 sleeves of Clif Blocks
  • Tic Tac container /w Endurolytes (only had one)
  • Black Diamond Spot headlamp (original model) /w extra (4x) AAA batteries
  • Body Glide
  • In drop bag at start/finish and not used (and not already mentioned above): Altra The One's; Montbell synthetic insulated hooded jacket; Patagonia Strider Pro running shorts; Patagonia Capilene 1 stretch long sleeve. 

Sunday, January 17, 2016

2016 Plans

My tentative race plans will be:
  • Zumbro Midnight 50, April 8, 2016
  • Spring Superior 50K
  • Kettle 100
  • Fall Superior 50
Context is important. My little guy will be a big brother some time in late July. This means running will be effectively shut down once kiddo no. 2 shows up. A couple notes on each race and my plains for them.

Zumbro is there for the overnight training, and the potential to run in adverse conditions. I've raced there twice (2012 and 2015) and dodged the 2013 and 2014 years of nasty weather. We'll see what the weather brings in 2016. 

I also ran this race poorly early on and got hurt half way through last year. This year, the run will be smart and even. I have score to settle with the course, if you will. With ideal conditions and smart running, I think sub-ten hours is doable.

1/31/16 EDIT: I will also be running be running that New Prague Half-Marathon (I know! A race shorter than 50K.) on May 7. It's part of the Kettle-specific training to run fast on dense terrain (asphalt), see below.

Spring Superior 50K, if the lottery gods favor me, will be a final training run for Kettle. I have a long-term goal of running this (and Afton, for that matter) sub-five-hours, but again this race needs to be run smooth and even. My PR here is a 5:19 or so, and I am confident I can best that. EDIT: 1/31/16: The lottery smile upon me, and I will be running this race. 

I have a score to settle with the Kettle 100 as well. This will be my "A" race this year, and I need it to qualify for another round of the lottery for Western States (for the 2017 race). I'm going to train as specifically for this as I can, identifying two portions of the course that kicked my butt last years: the heat; and the hard-and-flat first section that you go over four times. I'll do what heat training that I can, and do some quality workouts on the road to best simulate the conditions of that concrete-stiff surface. The grass running and dirt sections can be trained at Afton and Lebanon, and the single track can be trained at Afton and on the SHT. Goals: 1) Finish; 1.5) Finish with consistent effort and nothing left in the tank; 2) Sub-24; 3) sub-22; 3) Sub-Matt Patten's 2009 6th place 19:35:16. 

Fall Superior 50 miler will be run with whatever is left in the tank. I don't expect a good time, but I do expect a finish. I'm running this and not the 100 because the new kiddo is more important, and if I'm going to run a 100 miler - particularly this one - I need to put everything I have into it. And I can't run do that with a newborn taking priority over everything: sleep, training, etc. Running the 50 also means that my time away from the new one and my wife will be ~30 hours (Friday afternoon to late Saturday evening at the least) instead of something close to double that (Thursday afternoon to Sunday AM). This race will be run on my residual remaining fitness from earlier in the year, and so I don't expect something hard or fast, just a finish please. 

What comes after this 50 miler will likely depend on whether I finished Kettle. If not, I may need to look to Western States qualifiers in October and November. I'd rather avoid that, but I also don't want to miss a year of qualifying.