This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Training status not calculated correctly?

6797792
over 3 years ago

Yesterday I did an 80 mile bike ride and my 7 day training load went down. My garmin did shut off briefly during the ride, but it still uploaded normally. Is there any way to manually fix the training load and have it update correctly?

  • 0 over 3 years ago

    Does Garmin Connect show a Load value for that activity?

    The 7-day training load can go down if the oldest ride that just faded out of the 7-day window had a higher load than your newest ride.

  • 0 over 3 years ago in reply to Kyle J

    It says the load is 16. All my data is there, moving time 5:17:00, total time 6:26:00. TSS 287, average HR 149, average power 151, total ascent 5800. Whats odd is the total ascent was about 2000 feet less than what happened after I fixed the gain using strava.

  • 0 over 3 years ago in reply to 6797792

    Eck doesn't sound good. A load of only 17 seems unrealistically low for a 5+ hour ride, even if you did it at very low tempo. And the TSS of 287 suggests it definitely wasn't (roughly equivalent to 2.5 hrs at threshold output). So yeah, it sounds like the load value is definitely junk.

    Unfortunately load is one of the many heart-rate derived metrics that are calculated on the device itself. Once the activity is completed, it's done, there is no way to undo/fix those metrics (or at least I have yet to see any way from Garmin). And worse, the metrics from future activities rely on your history, so now that ride is in there skewing future results (downward in this case). It'll flush out of the system in about 7 days to 4 weeks, depending on the metric.

    This is one of the major issues with the Garmin ecosystem - these FirstBeat heartrate-based metrics are all embedded in the devices themselves, and if something goes wrong, it pollutes the metrics for some time and it can't be undone.

    Out of curiousity, what did it give for the Training Effect? A ride like that should normally have a pretty decent Aerobic Training Effect (like probably 4.0+), but it's based on the same algorithms that provide the Load value. If Load is crazy low, then I'd expect the same for Training Effect. Similarly the Recovery Time is probably really short for that low load value.

    As for the elevation, 2000 ft seems like a really large drift error, even for 6.5 hrs elapsed, though I suppose it's possible if the atmospheric conditions changed enough to affect the altimeter that much. But I wonder if whatever happened around the mid-ride shutdown somehow affected it. Is there is sudden change in elevation showing in the data around the point that the unit shut off? You can do a similar elevation correction in Garmin Connect to see how it compares with the correction from Strava. Maybe that'll offer some clues as to which is more accurate for that ride.

    Hope that helps!