Algorithms different in latest update?

Many of the recent updates seem to have reset HR zones in Garmin Connect which can alter how the Firstbeat metrics interpret that raw data. I'd check your HR zones in GC and GCM and resync before running again.

Judging by the two activities, the HR zones in GC are the same at least. (By hovering over the zones to see the ranges, and looking at the time in zones.)

But it's possible that zones have changed on your watch. A training effect of 4.8 seems sky-high compared to 2.6 for a similar run.

Agree - 4.8 with 0.0 on the other hand seems very odd!

I do not know if this is related but I'm seeing an increase in rested HR since 11.0. I used to average 53-54ish and am now up to 57-59ish. So I would agree on the change of algorithms.

Did you change your weight between these two activities? It is recorded in the FIT if you want to post the files.

To my knowledge, nothing major changed. Certainly nothing that would produce such a massive difference.

I'd double check your HRmax in the watch and in the app. Ceteris paribus an underestimated HRmax would explain both an overestimated TE and the fact your Performance Condition started off at -6 and stayed low throughout.

Looking at the change in TE scores and the fact that your Performance Condition was very poor in the latest edition of that run, it would appear to me that your watch thinks you are working at a intensity (VO2) much closer to 100% than you actually are.

It isn't quite this simple because Firstbeat utilizes some modeling techniques to calculate intensity in terms of oxygen consumption - not simply HR - but lets pretend it's HR for the sake of illustration… the same principles apply. If your HRmax is set to 200 and you are running with an HR=150, your watch thinks you are running at 75%. Meanwhile if your IRL HRmax is either, say, 180 or 220, then you would actually be at an intensity of 83% or 68% respectfully. Same HR of 150... big, big difference in actual intensity.

Just in case anyone was curious about measuring intensity in terms of VO2 consumption from HR data.

https://assets.firstbeat.com/firstbeat/uploads/2015/11/white_paper_vo2_estimation.pdf

The GC algorithms seem all over the place from the last update. My Training Load metrics are worse than rubbish - they are positively dangerous (ie potentially injury inducing).

Back in June I had a week where I ran 11km and cycled 7km, resulting in a training load of circa 440. This last week, I have ran 22km's, cycled 70kms and swam 2.4km's, with a resulting training load of 320. I appreciate the body adapts/changes but in this instance it is the computer that is clearly wrong.

Come on Garmin, please sort it out!!!

MB-Deus Yesterday. I was "maintaining" with arrows facing to the right. Today my load went up 14, but the arrows point down telling me I'm "unproductive".

The GC algorithms seem all over the place from the last update. My Training Load metrics are worse than rubbish - they are positively dangerous (ie potentially injury inducing).

Back in June I had a week where I ran 11km and cycled 7km, resulting in a training load of circa 440. This last week, I have ran 22km's, cycled 70kms and swam 2.4km's, with a resulting training load of 320. I appreciate the body adapts/changes but in this instance it is the computer that is clearly wrong.

Come on Garmin, please sort it out!!!

Have you checked your HR zones after the update? For me they are "reset to defaults (%HRmax)" so they are different to what I usually use. I might result in different results for TL as it's being calculated on device, GC is only displaying it. Just an idea.

are you sure, that you didn't reset your watch short time before your 1st run? you did not get a performance condition there. which looks like, it's not had enough data for calculating your actual training status. on the second run. you can see a performance condition.
PS: awesome run! :-)