
I didn’t get the sub 3:00, but I did get an official time of 3:05:30, which is a marathon PB by 10:32 and good enough to qualify me automatically for the 2011 London Marathon. So it was a good day. Acording to my Garmin 205, I was on a sub 3:00 pace (6:52) until around mile 20-21, and then I started to fade. So the wall got me, and the 6:52 pace was probably 8-10 seconds faster than I should have been going, in order to maintain an even pace throughout. On the other hand, even if I had maintained what Garmin said was a 6:52 pace until the end, my official time would actually not have been sub 3:00, because according to Garmin, I had to run a good bit further than 26.2 miles to get across the finish line (see below).
I love Edinburgh, I lived there for six months as an undergraduate in 1994 and have returned several times since, and it was great to take part in their marathon. You don’t see much of the city itself during the race, the course is mainly along the coast of the Firth of Forth, because that’s much flatter terrain than the hilly city centre. In other words, to get a faster course, you have to sacrifice running through one of the world’s most beautiful cities. This trade off was worth it for me last Sunday.
I’m not a fan of abandoning my wife and two kids for a whole weekend in order to run a race, I’d have preferred it if they could have come up with me. And I don’t plan on doing this kind of thing very often – my next planned races will be closer to home and my whole family will attend. But I wasn’t all alone in Edinburgh, because I did get to visit with some good friends up there who were kind enough to let me stay with them. So on balance it was definitely a good experience.

My favourite moment after the race was when my nearly four year old son asked me on the phone, “Daddy, did you win?” I laughed and told him I didn’t win but I did pretty well. “Did you get a medal?” he replied. I said yes, I did get a medal, and he seemed satisfied with that.
If you read any media coverage about the event you know that it was an unusually hot day for Edinburgh – temperatures hit 77 F (25 C), and this made it tough for those who weren’t used to that kind of heat, including, sadly, one 52 year old runner who collapsed and died. The heat didn’t bother me so much, I think because I grew up in the American South where it gets a lot hotter than that. I did get a bit of a sunburn, which I never would have expected from Scotland.
I’ve embedded my Garmin 205 results from the race below, and as you’ll see, Garmin thought the distance I ran was actually 26.43 miles. This is the second marathon in which I’ve worn the 205, and in the first (Luton 2009), it was nearly precisely the same story: Garmin recorded the distance as 26.42 miles. So I’m beginning to think that these courses are measured such that 26.2 miles is really the minimum distance you could cover on the course, and even though I try to run the shortest route (taking the inside track, the straight line from A to B, etc.), it’s very hard to avoid exceeding this minimum. As a result, my pace in these marathons as measured by the official clock has been four seconds per mile slower than my pace as measured by Garmin; for example at Edinburgh, my official pace was 7:05 and my Garmin pace was 7:01. What this means in practical terms is that in order to run an official sub-3:00 marathon, I need to run not at a 6:52 Garmin pace, but at a 6:48 Garmin pace. Nothing to do about that except train accordingly.