Run 674: Gloriously slow

Yes, I don’t normally use “gloriously” and “slow” together to describe my running pace, but today I am!

And it’s because this is only my second post-COVID run and I’ve only done one other so far this year (I am not counting my treadmill workouts, which are not actual runs). I wasn’t really planning to run at all, so I made an effort (ho ho) to stick to a conservative pace. I aced this because my overall average of 6:28/km is probably my slowest 5K run ever.

And it felt good.

I did actually experience a bit of a cramp on my left side just past the 2 km mark, probably because at that point I still had enough early energy to subconsciously push against the slower pace. The cramp went away quickly as I shifted to moving not-so-quickly.

Conditions were great at the lake. Despite being a Sunday, the trail was not at all crowded, the sun was out (but high up in the sky and not glaring into my eyes) and it was a balmy 18C. I experienced a touch of Dry Mouth™, something that normally doesn’t happen in April.

I also saw my first garter snake of the season, as it slithered off the trail and into the grass. The “Beware, bears!” signs are also back out, truly signaling that spring has arrived.

In all, I’m glad I made the effort. I may be a tad sore tomorrow, but I expect it to pass quickly.

Stats:

Run 674
Average pace: 6:28/km
Location: Burnaby Lake, CCW
Start: 1:12 p.m.
Distance: 5:02 km
Time: 32:27
Weather: Sunny with some high cloud
Temp: 18ºC
Humidity: 41%
Wind: light
BPM: 155
Weight: 173.5
Total distance to date: 4973 km
Devices: Apple Watch Series 5, iPhone 12, AirPods (3rd generation)
Shoes: Brooks Caldera 5 (93 km)

Treadmill walk: Odd

Odd because I usually finish strong, but the last workout was the opposite and today, I felt for sure I finished stronger on the last km but was in fact slower.

I have no explanation for this.

But I did sweat a lot. And I am two for two on my 30 minutes of exercise each day thing, so that’s good.

The stats are mostly worse than yesterday, though. Bluh, I sez.

Speed: 6.5 km/h (6.0)
Incline: 10

Pace: 9:44/km (9:41 km/h)
Time: 30:04 (30:03)
Distance: 3.08 km (3.10 km)
Calories burned: 311 (300)
BPM: 145 (140)

Treadmill walk: So sore

A day after doing a 5K run and a lot of walking for the first time in more than two months I decided (with it raining outside) to get at least a little exercise by going on the treadmill for a 30 minute workout at the more causal speed setting of 6 (bumped to 6.5 for the last five minutes).

Every muscle that had been worked yesterday screamed. Then they eventually stopped screaming. By the end I was feeling tired (I had been feeling sore and tired all morning and wanted to nap, not work out).

Overall, it was not too bad an effort and shouldn’t contribute much to even more soreness in the days ahead. I am going to try to hit the treadmill more often at noon, either walking or running, when the weather is not nice, to insure I get a little exercise every day. It won’t make me shed pounds, but it will help keep me a little healthier. Plus, it keeps my AirPods from getting lonely.

The stats (previous workout in brackets). As befits my current flabby state, BPM was a bit higher and pace was a bit slower, but nothing too egregious.

Speed: 6.0 km/h (6.5 km/h for last five minutes)
Incline: 10

Pace: 9:54/km (9:47 km/h)
Time: 30:04 (30:04)
Distance: 3.04 km (3.07 km)
Calories burned: 272 (251)
BPM: 136 (132)

Run 648: Holy lack of stamina, Batman

Run 648
Average pace: 6:28/km
Location: Burnaby Lake (CCW)
Start: 12:53 pm
Distance: 5.03 km
Time: 32:33
Weather: Clouds and sun
Temp: 19ºC
Humidity: 53%
Wind: light
BPM: 163
Weight: 175.1 pounds
Total distance to date: 4850 km
Devices: Apple Watch Series 5, iPhone 8
Shoes: Saucony Switchback ISO (210 km)

I would say it’s hard to believe it’s been 70 days since the last time I ran outdoors–March 22, just days after everything started getting locked down in B.C.–but when you look at my stats, it’s actually quite easy to believe, because I was not so much slow as struggling to keep moving over a distance I would in peak condition find trivial to run.

I knew I was in for a challenge when I walked the 4 km to the lake and saw my pace averaged 10:02/km. It would normally be about a full minute faster. And this was just walking.

Undaunted and without madding crowds due to the early afternoon start on a weekday, I made a pit stop at the Jiffy John (no sanitizer–boo, are they trying to give us Covid?) then set off on a five km course counter-clockwise around the lake, setting a steady pace and knowing that the goal was merely to finish.

And finish I did, though at several points it felt like the run was going to finish me instead.

You can see graphically what happened in this map of the run (Apple, please make these maps available on iPads and the web, thanks, and change them back to being light instead of dark. Dark is weird and ugly. Or at least make it a toggle):

The GPS did not fail twice, but my body did!

As you can see, I started out slow and occasionally–such as when the ground slopped downward–got a little faster before going slow again. Partway into the Piper Mill Trail my lungs were ablaze and I had to do something to keep them from scorching from the inside out, so I paused the run, then resumed once my breathing and heartrate settled a bit–before I reached the end of the Piper Mill Trail, at least.

I puttered along until I got about two-thirds of the way down the Cottonwood Trail. Again, I struggled to keep going and paused for a minute before resuming, after which I was abler to keep going through to the end.

My total time was a perhaps worst-ever 32:33, with the average overall pace being 6:28/km. I’m certain that is my slowest average pace ever. It certainly felt like it.

But I did it and while I may be sore as all get-out tomorrow, right now I don’t feel too bad. My BPM was 163, which is actually lower than my previous run, but this was likely due to the fact that my pace was so incredibly sluggish.

I did refill the tank to run a bit on the way back, though, so I have some dim hope that things will improve if I keep getting out there.

The weather was decent–pleasant, but not hot, partial sun and a light breeze. There weren’t a lot of people out, and the majority of those that were made little to no effort at physical distancing, except where it was impossible to avoid, such as on the narrow boardwalks. A surprising number of joggers were out and even more surprising, I passed one of them somehow. They must have been in casual running mode.

Despite some recent heavy rain a few days earlier (which was unusual compared to the weather trends we’ve seen this spring), the trail was in good shape, so puddle jumping was not needed, with one major exception.

This section of trail was completely submerged for some reason. Luckily, it’s right off the fields and you can actually detour around it by heading up the access road and hooking left at the first turn-off to rejoin the main loop.

A river runs through it…but shouldn’t.

Overall, while I am a bit shocked at just how slow I was, I can’t say that I was surprised at being slow and finding the run a bit of a struggle. Seventy days is a long time between runs. I will try not to go another seventy days before the next one.

Run 646: Technically running

Run 646
Average pace: 6:08/km
Location: Burnaby Lake (CCW)
Start: 11:49 am
Distance: 5.02 km
Time: 30:49
Weather: Cloudy
Temp: 7ºC
Humidity: 66%
Wind: strong
BPM: 162
Weight: 169.8 pounds
Total distance to date: 4840 km
Devices: Apple Watch Series 5, iPhone 8
Shoes: Saucony Switchback ISO (200 km)

Although I have run and done many walks on the treadmill since acquiring it in early December 2019, it’s been awhile since I’ve done a run outdoors. A large chunk of this has been due to having the flu and then almost immediately getting a cold as follow up.

Today I finally headed back to Burnaby Lake for the first time since December 29th, just over two months ago. Yikes.

The weather was a bit brisk (in fact, three degrees cooler than it was in late December) so I wore two layers, which was a smart choice, especially with a somewhat strong breeze also blowing.

I started out slow to keep myself from tiring out quickly, but that turned out to be a formality, as slow is the only speed I could achieve. The back half of the run felt not exactly like a slog, but slog-like. I kept moving. I was glad when it was over. I surprised myself by actually finding the energy to run a bit afterwards on the way back home.

The pace of 6:08/km is very slow but unsurprising, given the long layoff. Oddly, my BPM remained exactly the same as the last run, a bit up there at 162 but well below a level that I would be uncomfortable with. I did not think about my knees at all during the run and only thought of them briefly on the walk out as I felt the entirety of both legs start to stiffen and get sore in real time.

I expect the soreness to persist through tomorrow.

The trail itself was mostly dry, but sections are still in terrible shape, with parts collapsed and marked by traffic cones, others hastily patched up and the usual boggy parts by the fields requiring fancy footwork to avoid the feet getting mud and water-soaked.

Because it was the weekend and not raining, a decent number of people were out. One dog was kind of snippy toward me and another jogger. I didn’t notice so much because the music blocked out its yapping and it was low enough to be mostly out of my field of vision. I did turn back and see it going after the jogger that passed me in the other direction. Dumb dog (owner).

As always when you encounter multiple groups of people on the trail, some seem unaware that others are in fact using the trail, too. Fortunately I never had too much trouble moving around them, but the baffling inability handle interaction with others in a public space will always continue to annoy me. I try to not let it, but it does.

A mystery of sorts emerged just as I was heading out from the lake. My right hip suddenly became sore. It felt fine on the run and the 5K walk out of the lake, so I’m not sure why it turned on me long after the fact. Maybe it’s a trick hip now. I don’t like tricks. It seems mostly fine now.

Overall, this was not a bad run after more than 60 days off. I was tired, but never felt gross and wanting the suffering to end like nothing else in the world. I just kept going and going and then was done. I’ll try to run again next weekend and see how it compares.

Run 607: A bear, cramps, bikes and a sore foot

Run 607
Average pace: 6:33/km
Location: Burnaby Lake (CCW)
Start: 12:42 pm
Distance: 5:03 km
Time: 32:59
Weather: Sunny
Temp: 21ºC
Humidity: 52%
Wind: light
BPM: 166
Weight: 166.9 pounds
Total distance to date: 4615 km
Devices: Apple Watch Series 2, iPhone 8

This run was kind of awful, but not entirely unexpectedly so.

My last run was on April 20, 36 days ago. The main reason for the long gap was The World’s Worst Cold, which visited me over three weeks ago and continues to linger on with the occasional cough and stuff clearly still in my lungs. Perhaps I had an actual lung infection and instead of getting it treated with antibiotics, I opted for the old-fashioned cure of a long, painful recovery.

In any case, the weather was dandy today and I felt it was time to get back out there.

On the plus side, I was able to start the initial walk using Siri on the Apple Watch. Of late it usually just fails, no matter what I ask, but today Siri was feeling cooperative. On the negative side,. the pace of my first km walking was over 10 minutes. This is what the imaginary scientists I pay call “really slow.” The pace did pick up, but overall it was clear I was not yet 100%–even just walking. This did not seem to bode well.

The first surprise came as I approached the bridge on the Brunette River trail. A group of cyclists had just gone past me on the left, then came to a stop short of the bridge. There was something in their body language that seemed off. I caught up and saw why they had stopped.

There was a black bear walking down the trail toward them (and me, and another jogger who came up from behind).

A cyclist wonders how tasty the black bear would find him.

Here’s a zoomed-in shot in case the bear does not seem sufficiently bear-like in the above shot:

Woods hard, trails easy.

Some of the cyclists made noise. I wanted to shout out terrible puns like, “This situation is unbearable!” or “Don’t bear with us!” We waited to see what the bear would do, but it kept slowly advancing, seemingly oblivious of us. It went up a side trail before the bridge, but returned shortly, so we continued to move back, keeping us out of snacking range. The bear crossed the bridge, then headed up another side trail. This time there was a pregnant pause and the jogger carefully crept forward on the left to see if the bear was coming back.

It seemed the bear had found something sufficiently interesting on the side trail–perhaps an unleashed dog–and was out of sight. The cyclists pedaled and the jogger and I ran, me keeping an eye behind and to the side, but the bear was not to be seen again.

This seemed like a not-so-good omen for the run and just as I entered Burnaby Lake Regional Park, my left foot began to hurt in the way it would hurt in the pre-orthotic days. I have no idea why this happened out of the blue, but before ditching the idea of running, I went to the loo and on the way back to the starting position, I recalled how it was often easier to run than to walk when the foot got like this, so I started my run.

The run was hard. Not only was I shaking off 36 days of rust, I was clearly operating at less than 100% capacity, because even the opening km was poop, with a pace of 6:36/km. For three of the next four km the pace would only vary five seconds, between 6:32 and 6:37. Somehow in the fourth km I miraculously found some kind of small energy reserve that let me push to a fast-for-this run pace of 6:25/km, before slowing down again for the final stretch.

The sore foot was no doubt a factor, though once running it was not terrible or anything, more a background annoyance. But the lack of energy was palpable. I did not get a second wind. I didn’t get a first wind. Or any wind. I slogged.

I also did something I’ve rarely ever done–twice I paused the run and walked a bit to recover stamina and get my heart rate down, totaling about half a km overall. If I had kept the run timer going, my pace would likely have been a good ten seconds or so slower.

Once I mercifully finished the run, I just wanted to get out and back home. And then I started feeling cramps in my abdomen. Not the kind you get from running too hard (not an issue today), but more like something not agreeing with you, though I had eaten nothing out of the ordinary before heading out. This cramping persisted for much of the walk out from the lake before finally easing up. By then I was so weary it made little difference.

Due to it being a sunny Sunday, the trail was crowded. At one point a bottleneck forced me to stop to let other joggers and walkers pass. I didn’t mind too much because it allowed me to restore a tiny bit of energy. It was so busy that when I stopped at a bench along the second boardwalk to dump the gravel out of my shoes, three joggers passed by from both directions. That may not sound like a lot, but trust me, it is. It only took me maybe 30 seconds to clean my shoes.

Also I’m getting new shoes. They are great gravel scoopers, but I’d like something more comfy and less prone to scooping every jagged little rock it can find and depositing it under my foot.

One of the putt-putt cars went by me post-run and I felt the driver was going a tad faster than needed, given the little room I had on the side. But a minute or so later a family of three rode by on their bikes and the thought of them catching up to the putt-putt car and being told to get off their bikes, at minimum, gladdened my heart.

Just as I was leaving the park, a pair of cyclists were studying the map and somehow reaching the conclusion that they had to go around the lake despite a very large No Cycling sign below the map. I stepped over and confirmed no cycling at the lake and that park officials were out and would likely warn them at best to dismount. I also confirmed the contradiction of the Central Valley Greenway name, as most of it is along blacktop, and directed them to the bicycle lane on Government Street. I left, but as I looked back, I could see them heading off in the direction I’d pointed. Yay nice cyclists.

Overall, then, this run was not great. Lots of complications, the potential to be mauled by a bear, and no energy at all. I have not decided when I will run next, but waiting until next weekend is not without its appeal. This was also the first run in a long time when I wished I had a running watch with more detailed stats on things like blood oxygen saturation, so I could see how off I was with real data to back up how I felt. Somehow it might make me feel a little better.

Run 563: Nike says I’m slow

Location: Brunette River trail
Start: 12:32 pm
Distance: 5.01 km
Time: 32:07
Weather: Foggy
Temp: 2ºC
Humidity: n/a
Wind: light to moderate
BPM: 166
Weight: 162.3 pounds
Total distance to date: 4380 km
Devices: Apple Watch, iPhone, Nike+ Run Club app

Today I decided to be wacky and use the Nike+ Run Club app for my run, since it now monitors heart rate. And I got wacky results!

My pace was a strangely slow 6:24/km–this is more of a joggish than jogging pace, and while I was running slower due to some lingering icy patches on the trail, as well as to keep my BPM down, I wasn’t that slow. Another sign that things were off was the distance I had to travel to get to 5K. At the point the Apple fitness app would be reporting I’d completed the run, the NRC app was saying I’d only completed around 4.41 km. That’s a huge discrepancy.

There is no way to calibrate the Nike app, so I’m not sure why it was so bonkers. It seemed to get the BPM about right, since that data is pulled directly from the watch (it was 166, still a tad high but much lower than the last few runs so yay on that). I wonder if the app somehow didn’t use the GPS and instead relied on the much -less-accurate accelerometer. On the other hand, I’ve found that non-GPS runs tend to err on the side of being too generous with pace, not too stingy. A further complication is that what you get in the watch and phone apps depends on whether you are using one of the Nike-branded watches, as they come with some exclusive features, such as built-in Siri support. It felt wrong having to start the run by pressing buttons and stuff.

It was almost worth it for the better stats and ability to access the runs on the web (I find it immensely irritating that the fitness workouts through Apple’s app can only be reviewed on an iPhone–not even an iPad, which would at least give you a bigger map to look at).

The final quirk was no audio notifications. I wondered if this was another feature locked out of the non-Nike version of the watch, but it turned out to be working. I just didn’t hear it because the audio literally comes from the watch, not through the phone via the watch. So I was getting alerts but was oblivious to them because of the music blaring away. I only caught a bit of the summary at the end when I’d paused the music. I could fix this by starting the run from the phone instead of the watch or by syncing the AirPods to the watch (which also means listening to music from the watch, not the phone).

Anyway, it was in all a disappointing experience.

The run itself was okay, no issues other than the left knee being stiff to start but warming up not too far in. I did 5K on the river because I’m pretty sure the lake trail is still a pathway of treacherous ice and adventure.

I’ll walk tomorrow at lunch, which will allow me to survey the Langara Trail to see how it has weathered (ho ho) the recent snows.

Also, this marks the first run of the year. If I keep up this pace I’ll complete 365 runs by year’s end! That is somewhat unlikely, but I’ve already topped the number of runs I did in January 2016.