Avg pace = 8:12/mi
Total distance = 5.01 mi
Elapsed moving time = 41:09
Avg heartrate = 134 bpm (Coospo)
I also tracked this run on my Amazfit watch, which reported a slightly lower distance and a significantly higher heartrate (156 bpm average). Don't think this watch does a good job tracking heartrate, and I'm unconvinced that I can replace its native sensor with the Polar sensor. Going back to leg soreness, it might be the case that one of my bike shoe cleats is not aligned properly, so that longer bike rides cause irritation to my leg. I wore different shoes over the weekend and didn't feel any discomfort from that area on the ride. Had some cereal, yogurt, and a banana for breakfast, then I went over to a neighbor's house and picked up a plastic storage shelf they were giving away. Put it in our garage by the entrance to the house and placed a lot of the gardening supplies on it. I think it will work, although it makes for a tighter squeeze to get to my workbench area. Then I went out in the front yard and did some more work weeding the gravel path. Temperature was about right, but I just didn't have my heart in it, so I only worked for about an hour. Then I went in and ate some small cheese sandwiches for lunch. In the afternoon I tackled an issue I've been wondering about with my bike ride analysis program, which has output a significantly higher elevation gain than Strava has. Did some Gemini research, and it suggested that I average out the high-frequency noise in the elevation data before calculating the gain. I implemented a simple moving average approach, averaging about 30 seconds worth of data to smooth each point. Now, my program results more closely resemble the Strava numbers, so I think I'll go with this method. Made dinner from leftover spaghetti, Ann made bread and it was messy to clean up. Quiet evening watching TV.
No comments:
New comments are not allowed.