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 effect calculation is wrong on 9.33 software


Hi

We have a major bug affecting F7 Series.

The training effect calculated after a workout is higher than expected.

From v9.33 all base workouts are being calculated as TEMPO and VO2MAX workouts and all metrics based on this are useless.

It seems a core bug affecting 255, 955, F7/Epix.

955 has released a new beta  maybe fixing this, are we (Fenix/Epix) working on this too?

This is really a major flaw and should have the highest priority!

It was reported on Beta forum too base-runs-logged-as-tempo-and-training-effect-wrong

In this 955 thread there are a lot of reports about this too fr-955-series-training-effect-calculation-is-wrong-on-12-23-software

  • It's really odd... I just looked at the threads you linked to, and compared some running data before and since 9.33. For me, nothing changed.

    What Garmin classifies as base run has always been around load 2.4 for me, and what's a tempo or threshold run is around 3-3.2. Never been any big change. But have to say that even my recovery or base runs are above the first ventilatory threshold due to a medical condition. So it's possible that I never got to see this effect because the intensity was too high.

  • @JordiGT - Please highlight my name and send me a Private Message with examples demonstrating the issue exists with your Fenix 7 series watch. Thank you.

    I researched all reports on our end and the tracking case on our end. I do not see Fenix 7 series reports but the reports received for the Forerunner 255 and Forerunner 955 series resulted in Beta v12.25 software that was released yesterday to correct the issue with both Forerunner series.

  • - I just sent you by private message demonstrating with images what happens, if you need anything else do not hesitate to ask me, it is quite urgent a fix because only take out the fix will not fix all the metrics, then we will have to wait 4 weeks until the metrics have real data again.

  • I think that it could be that training effect is using the default zones by age instead of our custom zones, if you don't have custom zones or your custom zones match with the default zones by age you won't notice the problem, but the problem will be more evident when your custom zones are farther away from the default zones by age.

  • Nah, everything is totally custom for me, including LTh and HR zones, based on an exercise test. And they are so completely different than the standard setting. My maxHR is about 3 St.dev from 220-age, just to name one thing.

  • With version v9.33 I performed fourteen zone two running workouts of which 11 were detected as Tempo and 3 as Vo2Max.

    With the new v9.35 version, I performed a Z2 running workout this morning and it was correctly detected as Base.

    It is working fine again.

    Thank you very much.

  • I cannot help wondering why is the training effect algorithm code being worked on? Seemed to work - why tinker?

    seems to be an area unrelated to any of the announced changes / merge of functionality from 955 / 255 etc.

  • Do you adjust your zones for your medical condition? Be interesting to know what how you do that. I have a medical condition and have a lower heart rate than the standard 220-age calc. I contacted First Beat - be interesting to share what others do.
    Not related to this thread - do you mind if I DM you?