This past weekend Jess and I competed in the Philly Tri. My level of competition ended, oh, 20 seconds into the swim when I realized I was fucked. From then until I got out of the water I was just surviving. As you can imagine, my overall time was pretty terrible, which is completely my fault for (not|under)training.
Anyway, the part of the event I was most interested in was the cycling, obviously. I haven’t been in a cycling event since the MS150 last year - partly because of my own lack of initiative, but partly because Mark’s other real-life needs have pulled him away from racing this summer (and he was both my pull and my ride
)
Since I picked up by Garmin Edge 305 I’ve had some fun with the data, but it’s been hard to find a way to post it for use. The charts and information is rather cool, like being able to do a full playback of the ride on a GoogleMap at 1x to 100x speeds while watching my heart rate, speed, cadence, and the elevation changes. Check out this graph:

The red line is my heart rate, the green line is my speed, and the blue line/shaded area is the elevation. The legends for each are on the far left or right sides, and the shaded are in the legend show you the range I was in during this ride.
Of note/interest (at least to me - you guys might not geek out like I do to data…) - this is a 2 lap course, so after ~8mi the course repeats itself. The bubbles on the graph show my top 5 heart rate peaks (though they’re shown on the altitude line - I do this to see where my highest hearts happened based on the altitude change). The speed peaks that drop to ~5mph are incorrect - still trying to figure out what’s up there. Maybe a satellite problem. But I didn’t go 5mph at any point
Then you can look at the heart rates, colored by zone, projected onto the course map (for a better view of the loop structure, see this page):

What does all of this tell me? For one, I got out of the water way too tired. By the time I started recording the session on the bike - which was ~6min out of the water - my heart rate was still 165bpm (though oddly riding brought it down…shows you how comfortable I feel on the bike
). I did pretty well at staying in zone 4, the anaerobic workout zone, for the majority of my ride, though it looks like I could’ve pushed my heart a little harder. However, I know how my legs felt after the swim - they were on the verge of cramping all the time, both on the bike and on the run. So I know my heart/lungs were prepared for the ride, but my muscles weren’t…at least when you throw a 900m swim before the ride.
Looking at individual points on the graph I can see two of the HR peaks came during the biggest climbs of the ride — this is to be expected. The 177 on top of the hill came at the end of a hard push — check out the speed increase up to the 177 reading. The 181 and the second 177 reading are on the flats, but I know why those are there - those points were where the speed from the downhill had gone back down, I had just taken a long drink and quick Clif Bar bite, and had started to push to get back up to speed before the turn around/finishing line.
So what have I learned from having this data? Well, while riding it’s a godsend — I know how hard I’m actually pushing, regardless of my body cues. Knowing the physiological data as well as my body cues, it was easy to disconnect my calves screaming and my heart doing exactly as it should. Knowing this meant I could keep the pressure on and the pace up and just worry about overuse cramping and not cardiovascular cramping (if there is such a difference-I may have just made that up). The speed and elevation during a training ride are nice, but are mainly just flavor — my heart rate and cadence are all I really care about when I’m in the moment. Post-ride, though, this is all great to look at. Seeing the altitude and speed changes - especially on a loop course - graphed alongside my heart rate is amazing. I can dissect the ride and determine if, and more importantly where, I pushed either too hard or not hard enough. Having this data at my fingertips is exciting
So, my times:
| 900m Swin: |
32m57s |
| Trans1: |
5m39s |
| 24k Bike: |
53m16s |
| Trans2: |
5m55s |
| 5k Run: |
38m32s |
| Total: |
2h16m21s |
I’m upset at those times. I’m embarassed by them. I almost didn’t post them because of how ashamed I am of them. But there you have it - my Philly Tri times. Next year I’m going to shatter these. By a lot.
Overall lessons of the Philly Tri? Train for events, no matter how short, no matter how easily you think you’re going to do it. Learn how to transition — I spent 11.5min in the transition area, while Jess spent something like 4.5min. I lost 7min to her right there, and my second transition time of 5m55s was ~10th worst for the event. But the biggest lessons? My knee feels great, which means I can start running for real again, and triathlons are insanely fun. I really can’t wait to do another one — once I’m trained, of course.