Just a smidgen longer than my previous long run, but this time I added some intervals along about the midpoint, where I ran hard for one minute, and then spent two minutes recovering, and repeated for a total of 5 times. Probably not the smartest choice (embedding that in a long run), but I enjoyed it anyway.
My fitbit says I did 4.75 miles in 1:13:26.
Out on my run today, I happened upon this awesome lawn ornament.
I had decided to do a different, dog-free run, but then at the last minute, Ashley seemed to really want to come along, so I did this run instead, and it was great. Not as far or as fast as I’d have run by myself, but great.
I’m trying to ramp up to two runs a week—a “long” run (currently anything over 4 miles), and a “fast” run (sometimes hill sprints, sometimes an interval session, sometimes—as today—just a shorter run where I press the pace).
I got in a nice run: 4.67 miles in 1h 5min 51s, for an average pace of 14:05. My Fitbit would have me believe that I spent 59 of those minutes with my heart rate in zone 5, which I’m sure is double-false. That is, I don’t think my HR reached the 200 bpm that the Fitbit recorded, nor do I think my maximum HR is nearly as low as 154, which is what the Fitbit estimates.
Still it was a great run. My fastest and longest in a long time, and I felt great the whole time.
Ashley seems to enjoy going for a run, and she’s a pretty good running companion. She does want to stop and sniff rather more often than I do, and she wants to stop and pee occasionally, which does make it tough for me to hit my best pace for any particular mile. But that’s okay. Enjoying some dog-companionship is a lot better than hitting my best pace.
I had virtually quit running a couple of years ago. I’d gotten a trifle tentative after a fall, and then Jackie was out of town (and therefore not on-hand to rescue me if necessary), and then the weather got cold and the running routes icy. And by the time the weather improved, I’d just fallen out of the habit. For a few months now I’ve been working to reestablish the habit. I haven’t accomplished that yet, but I am getting in an occasional run.
The Fitbit software in my Pixel watch estimates my VO2Max. My estimated VO2Max has long been excellent for my age, but it had gradually dropped some, which was part of the reason I wanted to start running again. These past few runs have produced a modest increase, so as of today it’s in the 95th percentile for people my age. (I think Peter Attia suggests that the minimum acceptable VO2Max is the 95 percentile for someone a decade younger than you, which I’m still a bit below, although it seems perhaps doable.)
I’m afraid I failed to get a photo of Ashley or myself running (or better, the two of us running together), but I did get a picture of a cool little snake friend who was crossing the sidewalk where I was running.
I got in one writing session in the morning. Now that I’ve finished my run, I very much hope to get in some more writing (and most especially some more plotting) before the end of the day.
I haven’t been running enough, so I went for a run today. The metrics are kinda funny, by which I mean my Fitbit thought it was an insanely hard run. I thought it was interesting enough to post about.
Fitbit calculates heart rate zones based on your “heart rate reserve,” which is your maximum heart rate minus your resting heart rate.
Your resting heart rate (roughly what you’d get if you checked your heart rate right after you woke up, before you started moving around) the device actually measures. My resting heart rate, according to the Fitbit, was 56 bpm. (It actually hit 44 bpm at some point while I was asleep, but your lowest resting heart rate is a different number.)
Your maximum heart rate, though, isn’t measured. Instead, it’s estimated as 220 minus your age. I’m 66, so that comes to 154. So my heart rate reserve is 154 minus 56 equals 98. Then my various zones are calculate as a fraction of the reserve plus the resting rate. Zone 5 (peak activity) begins at 85%, so my zone 5 begins at (0.85 ✖️ 98) + 56, which comes to 83 + 56 = 139. All the parts of my run shown in red in the map above were run at a heart rate at or above 139.
In fact though, my maximum heart rate is way higher than that estimate. I have in the past been somewhat dubious of the maximum readings shown by my Fitbit during a run, because all the wrist-worn devices sometimes sync up at your foot-strike rate, so you get anomalous readings around 180 (a common foot-strike rate). But I also check my heart rate doing other exercises, such as kettlebell swings, where foot-strike rate doesn’t matter. Plus, I get heart rate readings from my Oura ring, which is not wrist-worn, and which doesn’t seem to have the same syncing-with-foot-strike problem. So I know my max heart rate is much higher.
On this run, for example, the maximum heart rate as measured by my fitbit was 169. My Oura ring thinks the peak was 166 (but it averages over 5-minute periods, which smooths out the peaks quite a bit).
Anyway, if you take 166 as my actual maximum heart rate, then my heart rate reserve is 110, 85% of it comes to 94, so my zone 5 range ought to begin at a heart rate of 150, rather than 139.
I find that a lot more plausible. If the Fitbit is right, then I just spent 36 minutes in zone 5, which seems very unlikely. It was kind of a hard run, because I haven’t been running enough, but I not only could have talked while I was running, I actually did sing, which is one of the markers for being in zone 1. (I was listening to and singing along with some Kpop songs.)
So, I think much of that run, even some of the bits shown in red above, were in zone 2 or 3, not zone 5.
Whatever the heart rate metrics, it was a rather slow, rather short run: 3.15 miles in 58min 10s.
Much better than not running.
Updated next morning: I slept great after my run, and woke up feeling great. Legs not sore at all. Overnight heart rate right back down to my current baseline.
My run was already supposed to be pretty short—about 2.5 miles, across Dohme Park, up First Street to Windsor and then back—but it ended up being even shorter than that, because Ashley wasn’t up to running even that far in the heat of the day.
According to my weather app it was already 75℉ when I got home, and I’ve noticed previously that starting at about 72℉ the dog starts to suffer.
You can see on the map a short spur off to the west just after I started north on First Street. That was where we saw a groundhog, and Ashley really wanted to chase it. I indulged her for a minute, hoping the groundhog would quickly find a place to hide, but it wasn’t to be, and I eventually had to drag Ashley back to the First Street path very much against her will.
Anyway, 1.3 miles is a very short run indeed, but I still spent most of 20 minutes with my heart rate up (average was 141, peak was 169). So, a good workout.
Went for a 3.3 mile run yesterday, with a time much too slow for me to be willing to mention it here. (I don’t know how much of the slowness was the previous day’s sword fighting training and how much of it was yesterday’s extreme heat, but boy was it slow.)
Slow as it was, I had a great time.
Got in a very nice run today with Ashley, going 2.46 miles in (despite what the image says) 33:41. Ashley was a Very Good Dog on the run, despite just a little bit of grabbing the leash in her jaws after we turned back toward home. 🐕 🏃🏻♂️
