I am pleased to report that my legs still work. Having a desk job is not great when you’ve run 20 miles, especially as I’m so busy that I just get lost in what I am doing and forget to get up and stretch my legs. However, having said all that my legs have been surprisingly okay. My shoulders were a bit sore…I must try and remember to shake them out and relax them a bit more when I do a longer run.
I had a recovery run in my plan for Monday but I decided against that for a couple of reasons.
- I didn’t want to run on tarmac (which I have to do if I run at lunchtime) and I didn’t have time to run after work
- I felt a bit knackered!
I did however do my planned swim on Tuesday evening. I did 1100m in 30 minutes which is pretty respectable for me. I was going to do 1200m but I could feel my left leg starting to twist a little which is always a sign that I’m getting tired and I didn’t want to risk hurting it. It was the right decision as it was definitely a bit sore when I woke up on Wednesday morning.
I had a very lovely (and early) Mother’s day present (that I bought myself and then informed Mike and the kids…..naughty Rose!). A Garmin Forerunner 410. I decided to upgrade from my 110 for a couple of reasons. Firstly, the 110 only tells you your average pace for the current lap rather than your current pace which makes doing paced intervals a bit tricky. Secondly, I’ve decided that after this marathon I really want to concentrate on improving my pace – even if only slightly – and in order to do that I want to use the ‘virtual partner’ on the 410 to push me to keep to the set pace. I also like the idea of the ‘show me the way to go home’ feature which will help me to pretend that I’m not really lost if I lead an offroad run (or when I do one of my magical mystery runs in the forest!). I’ve been really pleased with it so far but I think it’s going to take me a while to work out how to use all of the functions!
I didn’t have auto pause on my 110 so when I ran I used to look at the ‘moving pace’ to get the avg for my actual time running as opposed to my ‘average pace’ which included stops etc.
I switched on the autopause on the 410 as when we are doing group runs I have no choice but to stop and regroup etc so I don’t really ‘count’ that as a stop that is enforced by the inability to carry on running (iyswim!) but it does mean that my stats look better than they are really (see left). For example, the average pace for last night’s club run is 10:08 and that is accurate for the time running (excluding the regrouping stops) but I think that for a race it really needs to be turned off as the elapsed time is what counts in the results! In the Mad March my chip time was 3hrs 45 but my Garmin time was 3hrs 41 as my excursions into the woods were discounted!)
What do you do? Keep it on or off? I’m thinking that I’ll have it on for club runs (as I have no choice but make occasional stops) but that for other runs I’ll turn it off (especially races).
I’m not sure what I’m going to do for the rest of the week. My left knee protested a couple of times last night so I’m debating not running until Sunday to give it a chance to improve. I should be doing about 5 or 6 miles tomorrow but I’m paranoid about getting injured at the moment. I’m also in a big debate (with myself!) about what my next few long runs should look like. The plan for the next few Sundays says 15, 20, 13.2 (Reading Half), 8, 26.2 (eeeeeeek!) but I’m not sure that I want to push my luck with doing another 20 miler (or even 15 this week….) I’m thinking that I might do 12 this Sunday and then increase it the following Sunday (but not sure what to!) before going back down to 13 for Reading (no choice there…..). I definitely know that I won’t do 8 the week before the marathon as I’ll be mega paranoid by then!