Average pace: 6:12/km
Location: Burnaby Lake (CCW)
Start: 2:14 pm
Distance: 5:02 km
Wind: light to moderate
Weight: 168.1 pounds
Total distance to date: 4610 km
Devices: Apple Watch Series 2, iPhone 8
The conditions for today’s run were different in a number of ways compared to last week’s:
- warmer (16º vs 9º)
- windier (it was a tad breezy at times)
- at the lake running clockwise (ostensibly harder than clockwise) vs. running the river (which is inarguably easier)
I headed out and was pleased by a decent pace on the walk to the lake. I was less pleased by having to pee twice before starting the run, using every available public toilet along the way (which was both of them). I had decided ahead of time to run counter-clockwise, but this time I started the run on the south side of the dam, at the official 0K marker.
I headed off and at first it felt like I was running too hard and I kept pulling back, but it still felt hard. When I finished and saw the average pace of 6:12/km, I was not surprised–it nearly matches my previous run at the lake. The total run time is only separated by a mere second. It always creeps me out a little when that happens. How can I be that incredibly consistent from one run to the next over a distance of five km? Weird, I say.
Because I felt like I was working harder, I was also not surprised to see my BPM up a bit, but only a bit, and well below the threshold I prefer staying away from.
The big surprise came when I looked at the splits:
As you can see, I was doing the opposite of pushing to hard at the start, as I was muddling along at a decidedly average pace if 6:14/km. I did succeed in slowing down, though. as I dropped to a slug-like 6:33 in the next km. I recall feeling especially slow right around the midway point of the run before finally finding something of a second wind, or maybe just a moderate second breeze.
Whatever it was, it allowed me to pick up the pace, so my last few km were actually run at a decent pace. But by the end I was tired. I spent the first km after the run recovering and thinking about how much more my knees were aching compared to most runs (they seem no worse for wear now). After that one km of recovery, though, I ended up finding a new reserve of energy and managed ro run/walk the rest of the way around the lake. Overall, I’m not thrilled with the result, but I’m not really upset, either. It felt harder than it should have, but maybe the uptick in temperature was enough to drag on me.
The trail was quite busy. I didn’t see too many runners going by (and none dealt me the psychological blow of sprinting past me from behind), but one was jogging with a German Shepherd on a leash and I thought it was cute and then the dog barked at me–once–as I passed by and I no longer found it cute.
There were multiple cyclists out, all of them wearing that “I’m pretending I don’t know I shouldn’t be riding here when I totally know I shouldn’t be riding here” look. You fool no one, naughty cyclists!
The stinky part is in reference to the skunk cabbage, which is nearing peak skunk cabbage aroma. It is not a delicate bouquet.
Fortunately, despite the people, dogs, cyclists and geese, there were no near-collisions or fancy dipsy-doodling required to navigate around anyone. The section near the fields was festooned with several large puddles, and these did require a bit of coordinated footwork to avoid getting soaked from the ankles down. If they do any resurfacing on the trails this year, I hope they do this section first, even if I’d really like to see all the tree roots on the Cottonwood trail covered up. At least that trail never gets submerged.
I’m tentatively planning on another run on Monday, as it’s a holiday, but I will see what my knees say (“Hell no” or “Well…okay” seem the likeliest responses) before deciding. Also, if it’s pouring rain I may lean toward the “Hell no” even before consulting the knees.
Fun fact: I set a new Move record on my Apple Watch today, with 1840 calories burned (it’s up to 1912 as I write this):