It’s been a mixed week this week, I have been working from home as it was a short week in the Swiss office so it gave me the chance to do some local running and get to the track on Friday night. Â I’ve been getting used to my new Fenix 3 (I bought it from GoPro4Hire after seeing them recommended on Facebook), and whilst I am still pressing the wrong buttons at times we’re starting to bond nicely. Â We went for a nice run on a local trail together using the course navigation functionality and he beeped at me as I went off course and carried on up the trail rather than turning left across a field and we’ve been for plenty of walks to the shops and back with my steps being logged.
On Friday I was scheduled to do some 3 minute sprintervals, so The Boyf and I headed to the track. Â I decided that this would be a good opportunity to see how close in “accuracy” the Fenix 3 and Forerunner 620 were to each other. Â I have it in quotes because let’s face it I am not going to sit here and work out exactly which one is the most correct taking into account them being work on different arms, hence the 620 technically travelling further on the outline of the track lane and the Fenix on the tighter inner line. It’s really just a bit of fun. Â I also used this as an opportunity to have a play with the Zombies, Run! Intervals functionality. Â The app has just released Season 4 (more on that in another post) but having never managed to get the intervals to work previously I thought I would see if they had fixed it. Â They have, but the chat at the start of the session doesn’t count in the run time so whilst Fenix 3 & 620 were vibrating my interval changes in unison the Zombies were 90 seconds out of phase.
All in all it was a lovely track session in the sun, a slight breeze and a bit of shade meant I didn’t bake and I didn’t have the left calf and foot issues I had suffered in Tuesday’s threshold session (my compression socks definitely suit me better than ankle socks). Â I noticed from early on in the session that my 620 seemed to be pacing on the fast side. Â It does this sometimes but as I have got better about understanding my running body I have improved at understanding what pace I am running at. Â Not that I could run and tell you exactly my pace but I can tell by feel if I am running at 6:25/km or 5:30/km if presented with those choices. Â So today I went with the Fenix 3 as my pace indicator for the intervals and pretty much managedÂ my planned 4:49/km reps. Â It was toughÂ towards the end, especially the final 10 minutes back at my base pace but the training is designed to get the most benefit out of my training time without me descending into junk miles and it works, so I suffer in silence (well with a slight wheeze).
Saturday meant a trip to Thetford parkrunÂ to finally meet Dr Sean Radford of TrainAsONE. Â It was a lovely course, a wiggly, multi-lap mass of slight confusion (I wouldn’t want to be a front-runner here) and it gave us a good chance to chat as we ran along at my current base pace. Â I’m really please with how my training has been going with TrainAsONE, for a while I had my worries that aiming to run an ultra in 6.5 hours with my longest training run was 75 minutes long and that my speed over shorter distances would suffer whilst my training plan was focused on marathon distances (as that has happened to friends I know following off the shelf marathon plans) but it hasn’t been the case. Â The plan works for me, it has meant I have run my fastest 5km (27:44) and my longest distance, 29.7 miles (look away compulsive rounder-uppers) both whilst having a marathon as the target race as the basis for the programme. Â I can’t wait to see how the software deals with what I plan on throwing at it over the rest of the year! Â For my part I will continue to do what the plan tells me too, shuffling sessions slightly as needed to fit in with travel days and to accommodate parkrun and hope that I continue to get better at this running lark!