Friday, December 14, 2012

Timberman 70.3 Ironman Goal Setting using Data

A little more than a month ago I signed up for the Timerberman Ironman 70.3, aka Half Ironman, in August of next year (8 months away). I've done a few sprint triathlons over the last couple years and really wanted to step it up in 2013. Ideally I would have liked to do an Olympic distance triathlon as a stepping stone, but life got in the way of that this year so I decided to take the jump.

Obviously one of the first thoughts that enters your mind after registering (apart from the, "oh no, what did I get myself into!') is, "how do I properly train for this event"? There are tens if not hundreds of books written specifically about training for various distance triathlons. So I won't pretend I know anything about the actual training part, though I hope to learn more, maybe even pick up a book or two on it. Instead I'll focus on the often overlooked step before that, setting a goal for yourself. This can range from just finishing, to a specific time, to a place in your age group (male, 25-29). I chose to set a time-based goal, and as all good engineers do, I need a basis for the time that I choose, I can't just pick it out of thin air. That would be just silly.

Past Performance

Most (sane) people considering an event like this have some experience with triathlons or at least some of the individual sports. I've got a bit of both so I'll summarize my "race" history here:
  • Swimming: 
    • 800 meter freestyle race (highschool, a long time ago I know, but still a data point): 10:30
    • 1.2 miles lap swim (self-timed): 31:26
  • Running:
    • 5k GE Run: 25:29
    • 13.1 Skunk Cabbage Half Marathon: 2:04:00
  • Biking
    • HMCC Century: 6:10:00
  • Triathlon
    • Hudson Crossing Sprint Tri
      • 500 yd swim - 0:08:11
      • 12m bike - 0:36:51 
      • 5k run - 0:25:40
If I use my Hudson Crossing pace of 1.6 min/hundred for the swim, 19.5 mph for the bike and 8.25 min/mile for the run, that would equate to 0:33:36 for the 1.2 mile swim, 2:52:18 for the 56 mile bike, 1:48:04 for the 13.1 mile run, at Half Ironman distances. Adding in 5 minutes for transitions puts me across the finish line at around 5:19:00. As you would expect, when you compare the scaled times to the individual events that I've done for the run and bike, they are significantly faster. However I keep a pretty consistent pace for the swim regardless of distance (which means I must have been dogging it on the sprint tri!) Scaling those sprint tri paces to the Half Ironman distances may seem impractical, but I have a lot of room to improve, plus, it's a starting place.

Now lets take what we know and compare it to the results of my age groups for this specific race and course even. Fortunately there was data, broken down by event, from the website for '09-'12 for me to play with! I just looked at the data for my age group, male 25-29. I took the individual event times and plotted them versus the overall finish time. This allowed me to do two things. First, I was able to see trends for each of the individual diciplines and how they varied with overall finish time. Secondly, this allows me set a goal of a particular finish time and determine what each time would need to be based on the trendlines from the data. Here's the plot for your viewing pleasure:

(click to enlarge)

One of the interesting things that is very apparent is as the total time increases the variation in the run and bike times becomes huge. My guess is that this is most likely from those participants being really strong in one sport and not in the other. That or killing themselves on the bike and bonking on the run (foreshadowing?).

Finally, I chose 6 hours as my goal finish time. Partly because it was a nice round number and partly because it allows plenty of cushion from my scaled sprint triathlon time. If I use the trendlines (basically the average person) that gives me the following breakdown:

0:38:00 Swim, 3:05:00 Bike, 2:16:00 Run

I think that I can do the swim in around 33 minutes, which plus the 2 minute transition time, gives a few minutes of extra time to distribute between the bike and run. Heck, add it all to the run! So the final goal breakdown is:

0:35:00 Swim (Includes T1), 3:05:00 Bike (Includes T2), 2:19:00 Run

Hope you find this method helpful or at least interesting. Good luck!

Friday, August 24, 2012

Tab Overload

I'm a huge fan of tabbed browsing. It's the only way I can keep up with the multitude of people and topics vying for my attention. I can't imagine ever browsing without it. Though, I suppose the 30+ second load times for a single page with dial-up had a lot to do with it. But I've learned that there's such a thing as too many tabs, and Chrome has a good way of telling me when I've reached that magic number:

Chrome certainly lets me indulge my tab addiction, finally unable to display text (icon only) at 21 tabs and at 42 can't even display icons anymore (@ 1280x1024). More and more research has shown multitasking decreases overall productivity. I find that's especially true with my researching/browsing when I don't "complete/finalize" a thread of thought or tangent of research, examples of which would be looking up a definition or following a source. Having too many tabs is overwhelming and distracting, and when I realize half of them are obsolete and take a second to close them out, things become much clearer/cleaner. So here's my goal and a suggestion, after reading an article that warrants no further research or copying an image/quote from site that I want, close it. With history and google, it's easy enough to find it again if needed so why not keep things clean and increase productivity.

Thursday, June 7, 2012

How to Change DNS-323 Gateway IP

I recently installed a new D-Link router (DIR-655... yay gigabit!) on my network which has my DNS-323. I had the network up and running in no time after the typical reset-modem-reset-router dance and an obligatory call to the ISP's outsourcing call center located in India. The finishing touch was to plug in my DNS-323 and check out my new blazing fast transfer rates. I plugged it in and typed in the NAS static IP address that I had memorized... nothing. I realized that the default D-link router IP address ( is different than the previous Linksys router ( Meaning that my DNS-323 is probably using the wrong gateway. I was excited to find after a cursory Google search that someone had posted on the D-Link forums with an almost identical issue. The only responder suggested changing the IP of the new router to match the old. After a few unsuccessful IP changes which resulted in me having to reset the router back to factory settings (not fun), I realized that there has to be an easier way, a way to update the gateway of the NAS without being able to get into the settings through a browser. Then I remembered the D-Link Easy Search Utility. Duh...

1. Put in the D-Link DNS-323 Install CD. If you don't have the original CD that you can download just the Easy Search Utility from D-Link here.
2. Open the Easy Search Utility program.
3. If your NAS doesn't show up automatically, press the Refresh button.
4. Highlight the desired NAS by clicking on the name.
4. Change the gateway and IP to match your new router's convention.
5. Click Apply. (while you're here you can easily mount your new drives using the tool)
6. Enjoy!