Register | Login
Attackpoint - performance and training tools for orienteering athletes

Training Log Archive: PG

In the 1 days ending Jul 29, 2018:

activity # timemileskm+ft
  biking - dark blue bike3 5:05:54 69.66(4:23) 112.11(2:44) 5350
  Total3 5:05:54 69.66(4:23) 112.11(2:44) 5350

«»
5:05
0:00
» now
Su

Sunday Jul 29, 2018 #

10 AM

biking - dark blue bike 1:26:22 intensity: (46:20 @2) + (39:16 @3) + (46 @4) 23.9 mi (3:37 / mi) +1437ft 3:25 / mi
ahr:128 max:153

Off to do a charity ride with Phil in central MA, except the ride was Saturday, yesterday, so we were on our own. Which was fine, could stop at a store for fluids (or beg from a homeowner). And it meant we could start in Templeton, a good bit closer to home. Though we would miss the free beer at the finish.

Beautiful day, first day in a while with lower humidity and it sure makes a difference.

The route was relentlessly hilly. Not big climbs, nothing really steep, but up and down all day long. Sure made it more enjoyable that I had good legs.

Phil was having issues with his bike's rear derailleur on the climbs, so we stopped early on to see what might be done. I'd been having trouble with mine too for the past couple of weeks, nothing serious, just annoying, but I hadn't figured out how to fix it.

But now, looking at his bike, there seemed to be a little knob in about the right place, and it turned easily. We figured his cable had stretched a little and needed to be tightened, but the way I was turning it certainly wasn't increasing tension. So I reversed course and turned it one revolution in the other direction. Basic trial and error, after a while maybe we'd find some setting that worked.

He went off the ride up a nearby slope, can back to proclaim it was now perfect! If all of life was so easy.... :-)

Well, if we could fix his, how about mine. Found the same little knob, figured half a turn was enough for me, tried it out, bingo, perfect. Morale improved all the way around.

We went up and down some more, at some point I was distressed because my Garmin froze up, but then I got it fixed. A little later we climbed up to the top of Wachusett, quite fine. And then down, zip, zip, low 40s on the long straight part. Pretty soon we were at the Wachusett Brewery, where the loop started and finished, but since we had started in Templeton we still had 25 miles to finish our version of the loop.

And guess what. More ups and downs. But eventually we were back where we started.

I had a really fine time. A route that was new to me, weather was great, excellent company. And, of course, good legs. I was climbing well, certainly better than Phil (this was his first long ride of the year), so often I'd push it going up, then take it easy for a moment until Phil would go zipping by on the flats/downs. Pretty much a 70-mile interval workout.





And my one ailment, a sore spot on my butt, didn't really bother me much. :-)

11 AM

biking - dark blue bike 11:20 [3] 2.1 mi (5:24 / mi) +320ft 4:43 / mi

Garmin froze up. Second time it's done that, first was maybe a month ago, don't know what's up. Took me a while to realize it. I was on a longish climb and so my interest in checking it was my elevation, and that wasn't changing. But then the elevation readings are often flakey. I just use them for general info and, of course, entertainment. The fact that I was climbing and the elevation reading was staying the same was no immediate cause for concern. Sometimes I'm climbing and the elevation reading is dropping. Eventually things always balance out.

But not this time. Pushed the button to flip to the screen showing mileage, but the button didn't work. Nor did any other button. After what I imagine were a few curse words, I thought back to the first time it froze, tried to remember what I'd done to fix it. Hmm, pressed some button for 15 seconds. Hmm, which one? Tried the upper left, and after what seemed a while the screen went dark. Progress!

What next? Pressed the same button again, I think I'd done that the time before. And after a bit the screen lit up and I was back in business. Except not quite yet. Had to find some satellites. And I think the Garmin, its guts having been reset, thought it was back in Kansas City, or maybe China. And it took a loooong time. It finally buzzed just as I reached the top of the climb in Princeton, out of the woods for the first time in a while. That may have had something to do with it.

Back in business. Back home I downloaded to AP as usual, seemed the pre-freeze data had been lost. But later I got the usual e-mail from Relive, two e-mails actually, one for the post-freeze and also one for the pre-freeze.

So the data had to be somewhere. Went to Garmin Connect, yup, it was there, just wouldn't download the usual way. But figured out a plan B. See, I'm not alway totally incompetent. :-)

12 PM

biking - dark blue bike 3:28:12 intensity: (58:34 @2) + (2:07:20 @3) + (21:56 @4) + (22 @5) 43.66 mi (4:46 / mi) +3593ft 4:25 / mi
ahr:137 max:163

Rest of the Wachusett ride.

« Earlier | Later »