Showing posts with label visualization. Show all posts
Showing posts with label visualization. Show all posts

Sunday, December 8, 2013

I swear I didn't run through my neighbor's houses

I love data visualization
Today's run (street): 4.2 miles

The sky is as white as paper and the temperature is dropping. We're supposed to get two inches of ice and snow by late afternoon. Nothing so far, but I can tell it's coming. For that reason, I made sure I got outside early to get in a few recovery miles before conditions got worse.

I had no intention of running as hard as yesterday and had to throttle my speed a couple of times. A recovery run is supposed to be done well under anaerobic threshold to help flush lactic acid from leg muscles. I used my heart rate monitor to guide my pace, averaging 75% of HR max throughout the run. It was a nice relaxing workout, although my (gloved) hands got surprisingly cold.

No actual yards or living rooms were entered
I've written a lot about the variability of GPS as a measurement tool and today's margin of error was particularly egregious. Not only did the Garmin show me starting the run three blocks from my actual beginning point, the accuracy was laughably bad throughout the entire route. The Garmin route map (see above) makes it look like I ran through many people's yards and houses.

Distribution of pace times through the year
Reflecting back on 2013's racing season, I charted my race paces to see if there were any obvious patterns. The data doesn't show any trends that would explain my performance, as times were all over the map. I'm hoping that next year will yield faster times and more consistency. At least I finished the season in a good place.

Monday, November 11, 2013

Data visualization drives a decision

Downward slope
I downloaded my Garmin after yesterday's race to get a breakdown of my run. I'm a big fan of data visualization. When I looked at the cadence chart the data showed exactly where my base training had come up short. At 3.2 miles (almost the exact distance of my daily training runs) my average cadence had dropped from 89 to 85 SPM.

The shortcomings of my running routine could not have been clearer. I wasn't putting in enough distance in my daily training. I've always prided myself on the fact that I usually run six days out of seven. While the frequency is high, the distance is middling. It's a healthy routine, but not one that produces great race performances.

I'll admit that it's hard to break a running routine that's been a way of life for five years. Clearly a change is due. I'll continue to aim for longer runs on weekends, and try to increase my weekday distances. I'll aim for the same 18-20 miles a week, but will only run three days instead of four. If I could get closer to a 5 mile average run, my performance might proportionately improve.
 

blogger templates | Webtalks