Non-standard activity types breaks TriScore Calculation (GC 3.5, Build 3991)

[Track Smart]

Hi Folks,

Here's what I've found: If I add an activity to Golden Cheetah that is *not* Run or Bike or Swim, this seems to break the TriScore calculation.  For instance, a mostly Zone 1 (heart rate) hike at 2.2 MPH will yield a TriScore of 220!  This messes up all of my metrics.  If I change the activity to "run", I'll get a much more realistic TriScore value of 21 (one-tenth of the previous value).  

Questions:

1) How is Golden Cheetah making this TriScore calculation on "Hike" and "Walk" and other non-standard activity types?  It seems to be ignoring heart rate (which was very low).  And it doesn't seem to be based on pace (just 2.2 MPH for that last hike).  

2) Is there a fix I can enable?  My current work-around is coding all hikes and walks as "Run" for the activity type.  But its annoying to manually do this.  It also makes sorting by activity type problematic (i.e. hikes are mixed with runs).

Thanks for any insight that folks can provide!  I'm running v3.5 (not the new development builds).

[Ale Martinez]

El lunes, 25 de julio de 2022 a la(s) 04:19:46 UTC-3, track...@gmail.com escribió:

Hi Folks,

Here's what I've found: If I add an activity to Golden Cheetah that is *not* Run or Bike or Swim, this seems to break the TriScore calculation.  For instance, a mostly Zone 1 (heart rate) hike at 2.2 MPH will yield a TriScore of 220!  This messes up all of my metrics.  If I change the activity to "run", I'll get a much more realistic TriScore value of 21 (one-tenth of the previous value).  

Questions:

1) How is Golden Cheetah making this TriScore calculation on "Hike" and "Walk" and other non-standard activity types?  It seems to be ignoring heart rate (which was very low).  And it doesn't seem to be based on pace (just 2.2 MPH for that last hike).  

IIRC there’s a bug in v3.5 fixed in v3.6 which allows a bogus BikeScore value be used in these cases, you can force BikeScore to 0 for the activity in Details > Metrics so TRIMP Zonal points are used for TriScore.

2) Is there a fix I can enable?  My current work-around is coding all hikes and walks as "Run" for the activity type.  But its annoying to manually do this.  It also makes sorting by activity type problematic (i.e. hikes are mixed with runs).

You can setup a filter in your PMC chart to avoid activities other than Swim, Bike and Run. 

[Track Smart]

Hi Ale,

Thanks so much for the reply!  Somehow my notification for your answer ended up in spam.  Gmail doesn't understand when Google itself is sending an email!  Doh!  

I've been hesitating to jump to version 3.6, since it is still listed as a development release, but I might give the hopefully quite stable "Development Release" a try and see if that fixes this problem (and doesn't break anything else).  If that fails, I'll try your workaround (set Bikescore to Zero and see if TRIMP Zonal gets used in calculating TriScore). Thanks again!

[Track Smart]

PS: setting the filter in the PMC chart is another good workaround!  Thanks!

[Track Smart]

Just an update:  This issue persists in version 3.6 of GC (Build 5000).  Changing all non-standard activities to "run" leads to a much more realistic Triscore.  

Example: Instead of an easy hike having a TriScore of ~150 it gets changed to ~15 after labeling it as a Run.  That's a ten-fold decrease in the estimated training load and much more realistic.

Does this issue still exist in the latest stable release?