Related
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

FR 955 Series: Training effect calculation is wrong AFTER 12.23 software (may include 12.27 and 13.15 sw)

rklyukin
over 2 years ago

At the request of duplicate the topic here - from the beta 12.2 forum!
Instead of fixing the problem, Garmin is engaging in bureaucracy!

__________________________________________________________

Because some of you have reported seeing this on the latest(non-beta) production software, let's please have you start a thread in the main forum for this device:

https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series

____________________________________________________

Training effect calculation is wrong! After the update, this indicator began to be considered incorrect relative to the past similar workouts. 

Today, August 22, there was a training session. The workout was in zone 1 with an average heart rate of 135 bpm. Training Effect wrote that he trained his lactate threshold well. O_O IS IT? IT'S A JOKE? The run was strictly in zone 1. My lactate threshold in the app is 176! Until update 12.2 and complete data reset from the watch, Incl. there was no such training!

today's training - 24.08.22. what the ***?!?! WTF?! What is another intense workout? what the *** is a vo2max increase?!? It's a Base workout! This was before the update to 12.2. Garmin please take note and fix this ASAP!


  • 0 over 2 years ago

    Just to test this, I have done 2 x 1 hour and 45 minutes runs at roughly the same pace 

    1. Avg HR 147, TE Aerobic 4.0, 14% Z1, 85% Z2.

    2. Avg HR 136, TE Aerobic 4.0, 85% Z1, 14% Z2.

    This does not seem right to me...

  • 0 over 2 years ago in reply to Alexander

    Have you updated the firmware to 12.25 beta? 

    Why does it not seem right? I don't think those Aerobic TE values are looking very strange. The TE "accounts for your fitness level and training habits" and the scale is defined as "0 – None, 1 – Minor, 2 – Maintaining, 3 – Improving, 4 – Highly Improving, 5 – Overreaching". So it would also be affected by what training you have done previously, which may also have been a bit off due to the 12.23 bug. I don't interpret TE as a pure measuerement of training load for a specific run, which probably would be higher for first run.

  • 0 over 2 years ago in reply to SvenPlex

    https://www.firstbeatanalytics.com/en/features/workout-labels/

    1) Important to look at the classified labels. I guess it's classified as tempo or threshold?

    2) Try to compare with similar and past workouts.

    3) Like you said, it's good to look at subsequent workouts too.

  • 0 over 2 years ago in reply to DPSK

    1) Base and Base, both of them.

    2) Will do

    3) These are subsequent workouts, the one with the lower HR being on a consecutive day

  • 0 over 2 years ago in reply to SvenPlex

    No, stil running 12.23 buggy, not the beta. But a run -11 BPM avg cannot produce the same TE, from my POV... 

  • 0 over 2 years ago

    12.25 seems to have fixed the TE bug, but the cadence running bug still appears (treadmill and outdoors)

  • 0 over 2 years ago

    There is definitely something still up.

    After a fairly easy run today I received a notification to say my max heart rate has been increased from 185 to 186.

    Now my heart rate barely went above 160bpm.

    Training effect was all base though which is what I would expect but the heart rate zones were all over the place when checking the post run stats.

  • 0 over 2 years ago in reply to Mike

    What I fail to understand ...and the is a lot of detail in all these forums ,,,,as a long time user of Garmin and the Training suggestions etc , is why we suddenly need to all delve into such detail and change everything we have been doing ...for no reason , no explanation at all...just because some mess in the software across many devices has caused a huge mess...Garmin needs to come to the table and sort this out...simple give those of use who want it a way to have the base 11.xx ...call it 12.30 if you must but why must we mess about with heart rate zones we have had for years just to manipulate the data to get the result that should be automatic...a base run is not a Tempo, full Stop.   I. am not sure what 12.23 sorted , certainly  not navigation fully - which was the main reason I upgraded from the 745 -  ,and it created so many new issues ...There that is my rant for the day I guess.

  • 0 over 2 years ago in reply to S.M.R.

    I just feel, with all of these quite major bugs, they should be coming out and saying "right we know a, b and c are currently not working correctly, we are looking to fix all of them by x date/month".

    It's clearly been rushed and it's just tarnishing the brand.

  • 0 over 2 years ago in reply to S.M.R.

    You shouldn't have had to mess with your hr zones during this issue if they were set correctly in the first place. The zones are not the problem, it's just observable hr data to help you understand whether or not there's a problem with your device's TE calculation during activity.