Training Log Archive: BadgerIn the 7 days ending Apr 22, 2016:
| ||||||||||||||||||||||||||||||||||||||||
| « | » |
| » now | ||||||||||
|
| ||||||||||||
| Sa | Su | Mo | Tu | We | Th | Fr | |||||||
Friday Apr 22, 2016 #
Note
Unbelievable news about the Manchester Marathon course being short in 2013/14/15! http://www.independent.co.uk/sport/general/athleti...
Being 380 metres out is huge - about 1% of the total course length - at the pace I was going at towards the end that would have added over 2 minutes to my total time, turning my just under 3:07 into something just over 3:09.
I did always have my suspicions – my 2014 GPS trace (http://www.attackpoint.org/sessiondata.jsp?session...) only came in at 41.75km / 25.94 miles (which it now turns out was pretty much bang on!), as opposed to 42.35km / 26.32 miles this year. It explains a lot – in particular as I mentioned in my race report last week how in 2014 the mile markers were all coming up slightly short, and this year they were all slightly long, despite it being pretty much the same course, which is consistent with the explanation from AUKCM (http://coursemeasurement.org.uk/investigations/man...) that it was a measuring calibration issue.
What it also means is that actually I don’t think I paced it as badly as I thought on the day in 2014 – I was frustrated by my over-reliance on the Garmin and not adjusting my pace during the race when the mile markers were coming up short. So my half way split shouldn’t really have been the official 87:54 (Garmin only showing 20.92km at that point) – my actual 21.1 km split was 88:37 which is much closer to what I’d originally aimed for and perfectly sensible for a 3-hour target. Which means that than my hitting the wall at 20 miles (or 19.8 miles…) was probably less due to poor pacing, and maybe was just going to happen anyway on that day for whatever reason (perhaps just not quite fit enough at the time).
Anyway, thank goodness it was all sorted out for this year and my new time still stands, as my previous PB from 2014 has now been wiped off the record books – Power of 10 has already been updated to remove GMM 2014 from my list of marathons, now describing this race as a “short marathon”! I’m guessing 2015 times won’t now be eligible for London GFA next year. Very pleased in hindsight that I didn’t get the sub-3 in 2014 – I might not have done GMM 2016 then, and if 2014 had been my only sub-3 now I’d have been rather gutted!
Being 380 metres out is huge - about 1% of the total course length - at the pace I was going at towards the end that would have added over 2 minutes to my total time, turning my just under 3:07 into something just over 3:09.
I did always have my suspicions – my 2014 GPS trace (http://www.attackpoint.org/sessiondata.jsp?session...) only came in at 41.75km / 25.94 miles (which it now turns out was pretty much bang on!), as opposed to 42.35km / 26.32 miles this year. It explains a lot – in particular as I mentioned in my race report last week how in 2014 the mile markers were all coming up slightly short, and this year they were all slightly long, despite it being pretty much the same course, which is consistent with the explanation from AUKCM (http://coursemeasurement.org.uk/investigations/man...) that it was a measuring calibration issue.
What it also means is that actually I don’t think I paced it as badly as I thought on the day in 2014 – I was frustrated by my over-reliance on the Garmin and not adjusting my pace during the race when the mile markers were coming up short. So my half way split shouldn’t really have been the official 87:54 (Garmin only showing 20.92km at that point) – my actual 21.1 km split was 88:37 which is much closer to what I’d originally aimed for and perfectly sensible for a 3-hour target. Which means that than my hitting the wall at 20 miles (or 19.8 miles…) was probably less due to poor pacing, and maybe was just going to happen anyway on that day for whatever reason (perhaps just not quite fit enough at the time).
Anyway, thank goodness it was all sorted out for this year and my new time still stands, as my previous PB from 2014 has now been wiped off the record books – Power of 10 has already been updated to remove GMM 2014 from my list of marathons, now describing this race as a “short marathon”! I’m guessing 2015 times won’t now be eligible for London GFA next year. Very pleased in hindsight that I didn’t get the sub-3 in 2014 – I might not have done GMM 2016 then, and if 2014 had been my only sub-3 now I’d have been rather gutted!
12 PM
Trail running 41:17 [1] 8.07 km (5:07 / km) +55m 4:57 / km
ahr:147 max:166
Regent's Park.
Thursday Apr 21, 2016 #
12 PM
Trail running 42:21 [1] 8.22 km (5:09 / km) +38m 5:02 / km
ahr:153 max:169
Hyde Park. First post-marathon run after 10 days of complete rest. Kept it nice and easy. All feeling pretty good, no niggles - a good sign as it was the first post-marathon run in 2014 that started all the injury problems. Running in brand new shoes (Asics Fujipro - great for the grass and gravel trails in the parks). Also the first outing for a brand new Garmin I've treated myself to (Forerunner 235) - wow, the difference in time for picking up the satellite signals is incredible! (i.e. 10 seconds or so instead of the usual minute or two). The upload to PC also seems much more reliable now too. This one comes with a built-in heart rate monitor (no chest strap required) - many years since I ran with one of these (I never liked wearing a chest straps), will be interesting to look at this data and see if it helps at all - I've no idea what to make of the initial data.