I split the difference between a 5K and 10K today, running 7K and cleverly thinking I’d get my total distance stat to something nice and even. But I misremembered and should have run 8K for that, so now it is listed as 5339 km and it makes my OCD twitch a bit.
That said, the run itself went fine overall. I felt good and could have gone the full 10K without any issue. It was considerably cooler at 9C, but I wore two layers up top and never felt cold. My pace stayed fairly steady, too, with only a slight dip midway through. My BPM was a little higher than the norm, but I chalk that up to not having run this much in a few weeks, plus the significantly lower temperature. It was still fine, though.
I only saw two other people running.
The weather had called for showers and while it did rain before I headed out, it changed to intermittent spitting on the way to the lake, then stopped entirely, making for a pleasantly dry run, save for a bit of puddle navigation.
There were a few small technical hiccups:
- At about the 3 km mark I felt what seemed to be a piece of gravel slipping into my right shoe. After a few more steps it slipped under my heel and began boring into it with each step. I paused the run to remove it. My glasses steamed up, which I found mildly amusing. No further gravel made its way in, but I’ll keep an eye on the new Peregrine 12s to see that they aren’t like the old Brooks Cascadia Scoopers1not the actual name but it could have been! I used to run with, that seemed specifically designed to scoop gravel off the trail and deposit it into your shoes.
- Before leaving home, I always check the AirPods to make sure both buds are fully charged. There is an issue where sometimes, for reasons Apple has never explained nor remedied, one of the buds will fail to charge, so it will sit snug in the charging case and deplete itself. This morning I did not check the AirPods before leaving. You can guess what happened next. It took about 10 minutes to get the right bud back up to 55%, which was enough to last the run and the walk home. While the glitch is Apple’s fault, I should have known better than to invoke it by not checking first.
- Between the 6 and 7K mark I went to check my heart rate and saw instead the little spinning circles that means, “Heart rate? What is this heart rate thing? Are you sure there is a heart here?” I hit pause and just as I did I could see the BPM kick in. I unpaused, and it was 168, which is basically impossible. But I just ignored it as the anomaly it was and hoped it would correct itself, but it shows the 7th km as 165, which still seems way too high for how fast I was running. I really don’t want to get a new watch, but I’m not sure if I trust this one anymore.
Despite the glitches, it was nice to get out and aboot again. We’ll see how the weather is on Wednesday, as we’re now in “the weather can change multiple times a day” part of the year.
After last night’s rain, the dam was releasing a lot more water than it has of late:
Stats:
Run 725 Average pace: 5:54/km Location: Burnaby Lake (CCW) Start: 11:41 a.m. Distance: 7.04 km Time: 41:37 Weather: Cloudy Temp: 9ºC Humidity: 92% Wind: light to nil BPM: 155 Weight: 159.9 Total distance to date: 5339 km Devices: Apple Watch Series 5, iPhone 12, AirPods (3rd generation) Shoes: Saucony Peregrine 12 (17 km)
