Topping up the Exercise

A modest evening walk, because calories are calories, and walking is better than watching TV!
Also builds the legs up, if you are not used to running yet.
Even though the heart rate is under my Zone 1 throughout.

So, you've done the main exercise activity for the day.

30 minutes, say, of intense sweating.
You really couldn't do that again today.

Time for a nice sit down in front of the TV for the evening, then?

There is another choice.

The Long Slow Run - Getting A Bit Muddy On A Lap Round Town.

The Long Slow Run - it's not High Intensity!
My "threshold" is between the two short bars on the far right.
The two tallest bars are at about 85% and 90% of my threshold.
(this is a screenshot of a real run taken from my Training Peaks account)

The Long Slow Run.
A classic training technique.

It's not much to do with how fast you go - it is about stretching the distance.
It's not about being so dead beat at the end you can't move - it is about pacing yourself round, so you finish in "good order" - maybe a bit creaky, but not too much.

Workout Time Being Lost in Training Peaks - and a workaround

Hmm, Running exactly at midnight?
I think not!
Yet this is how my run is displayed in Training Peaks.

14:52, according to Garmin Connect.

14:52, according to Strava

I had a nice run yesterday, but there was a problem.
I uploaded my data from my Garmin 310xt to our PC via the Ant+ dongle to Garmin Connect.
Garmin Connect then automatically cascades the data to Training Peaks and Strava.
So what was the time recorded by Garmin Connect?


So it looks like Training Peaks has corrupted the time data!
Oh.
So I contacted the TP contact email ...
And they asked for a screenshot, which I duly sent.

Then I got this reply:

Reply to the apparent bug I found in Training Peaks,

So there you have it.
It really is Training Peaks corrupting the data.

The problem:
I always do Eleveation Correction first, then use the Recalculate option occasionally to adjust my "zones" as appropriate after a look at the data.
That is what seems to be causing the loss of time data.

The "official" workaround:
However, for the time being, Training Peaks advises that if you are going to use Recalculte, you use that first, and then do the Elevation correction after

My simpler "unofficial" workaround:
Since the time data is already held by Garmin Connect, I can just look it up, and manually overwrite the default "midnight" time in the affected workout!


It seems this "timestamp" problem only shows up if you use both Elevation Correction and Recalculate on the same workout, in that order, so it isn't that much of an issue.
Anyone who recalcultes after every workout is making a lot of work for themselves for little benefit.
the only reason I am doing it is because after my recent crash, I was (am!) a lot less active, and so all my old thresholds don't mean a whole hill of beans. I need to train for who I am, not who I was!