Just a thought, define a new user metric: myTSS. If power data present use Coggan TSS, if not and heart rate is present estimate hrTSS according to Joe Friel and time spent in heart rate zones.
But TRIMP Zonal Points does not use power data even if this is available, right?
Ale - when you say match Friel's - how would you do this exactly? How do you know the coefficients?
1 | 20 | 0.33 |
1 | 30 | 0.50 |
1 | 40 | 0.67 |
2 | 50 | 0.83 |
2 | 60 | 1.00 |
3 | 70 | 1.17 |
4 | 80 | 1.33 |
5 | 100 | 1.67 |
5 | 120 | 2.00 |
5 | 140 | 2.33 |
Thanks Ale - can you explain why you divide by 60? I'm not following this!
1 | 0.50 |
2 | 0.92 |
3 | 1.17 |
4 | 1.33 |
5 | 2.00 |
Sorry also now I've changed the values - nothing has changed. The date is set way back - should GC auto recalculate the TRIMP zonal values?
TRIMP coefficients are not included in the HR zone fingerprint, right?
Yes sorted that night by deleting and reinstating HR zones.
{
init { myVal <- 0; }
sample{
if(Data contains "P")
myVal <- TSS;
else myVal <- TRIMP_Zonal_Points;
}
value { myVal; }
I then went on creating a new PMC chart using myTSS as Long, Short term stress and Stress balance.
-Pontus
--
_______________________________________________
Golden-Cheetah-Users mailing list
golden-che...@googlegroups.com
http://groups.google.com/group/golden-cheetah-users?hl=en
---
You received this message because you are subscribed to a topic in the Google Groups "golden-cheetah-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/golden-cheetah-users/ElrZ_MhUwHc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to golden-cheetah-u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hello all,your problem could be that you need an extra } at the end. See the last custom metric:
{
value() {
Data contains "P" ? TSS : Trimp_Zonal_Points;
}
}
Also, I can't make it working, Do I need to define Trimp_Zonal_Points? I think that it is done automatically when you define the HR zones.
Regards
2016-07-31 14:53 GMT+02:00 Serban Mestecaneanu <serba...@gmail.com>:Could someone (Mark or Pontus) tell me what is exactly the syntax to put into the User defined metric?I tried Pontus first, but pressing TEST gives me zero values.Thanks,Serban
--
To unsubscribe from this group and all its topics, send an email to golden-cheetah-users+unsub...@googlegroups.com.
I can see in this thread several references about creating your own user defined metrics. I have version 3.3 installed and I don't see that option, should I get the 3.4 version? should I get the code and create my user defined metric from code itself?I'm a developer myself but new to this project and still trying to find my whereabouts.... so excuse the slightly off-topic but I also want to create my_hrTSS whenever Powerdata is not available.
How did you create the chart?
Just a quick question regarding this: I've got my PMC chart pulling training load from either power data, TRIMP(100) if that's unavailable, or RPE if heart rate is unavailable as well, but my chart doesn't feature the exponential decay between points you see on the default PMC charts. Along with this, the default PMC charts appear to use some sort of peak-find when picking which points to highlight (if that option is selected), whereas my chart does not and just picks the highest valued points. Anyone got any idea what I've missed?
--
_______________________________________________
Golden-Cheetah-Users mailing list
golden-cheetah-users@googlegroups.com
How did you create the chart?
El 2 dic. 2016 1:42 a. m., "Scott Michaels" <sc...@sdmichaels.com> escribió:
Just a quick question regarding this: I've got my PMC chart pulling training load from either power data, TRIMP(100) if that's unavailable, or RPE if heart rate is unavailable as well, but my chart doesn't feature the exponential decay between points you see on the default PMC charts. Along with this, the default PMC charts appear to use some sort of peak-find when picking which points to highlight (if that option is selected), whereas my chart does not and just picks the highest valued points. Anyone got any idea what I've missed?--
_______________________________________________
Golden-Cheetah-Users mailing list
hi,
{
init { myVal <- 0; }
sample{
if(Data contains "P")
myVal <- TSS;
else
myVal <- TriScore;
}
value { myVal; }
}
{
init { myVal <- 0; }
sample{
if(Data contains "P")
myVal <- BikeStress;
else
myVal <- TRIMP_Zonal_Points;
}
value { myVal; }
}
Hello,Ale, in your answer to my issue on github https://github.com/GoldenCheetah/GoldenCheetah/issues/3249 , you mentionned some improvements to get my code working...The TriScore metric is null on rides (sport=Bike) without power data...
Therefors, the updated hrTSS code does not work as expected :{
init { myVal <- 0; }
sample{
if(Data contains "P")
myVal <- TSS;
else
myVal <- TriScore;
}
value { myVal; }
}
{
value { BikeStress>0 ? BikeStress : TRIMP_Zonal_Points; }
}
Even simpler is to use just TriScore without a custom metric if you don't mind to use BikeScore instead of BikeStress/TSS.
El lunes, 9 de diciembre de 2019, 9:55:55 (UTC-3), Gilles Foucault escribió:Hello,Ale, in your answer to my issue on github https://github.com/GoldenCheetah/GoldenCheetah/issues/3249 , you mentionned some improvements to get my code working...The TriScore metric is null on rides (sport=Bike) without power data...On v3.5 TriScore for Bike workouts is computed as follows: BikeScore when BikeScore > 0 otherwise TRIMP Zonal Points, hovering the mouse over the metric explain this.If that is good enough for you there is no need to use a Custom Metric, any TriScore based chart will have the fallback included and, if you want to exclude no power ride you can use a BikeScore>0 filter at the chart or global level.
My comment about improvements is: it makes no sens to use a sample() function, which is called for EACH sample -typically one per second- to compute a value which always the same and it can be computed just once in the value function, I don't know from where is ugly code comes but I've seen it copied again and again. A much simpler and efficient replacement is:{
value { BikeStress>0 ? BikeStress : TRIMP_Zonal_Points; }
}
Even simpler is to use just TriScore without a custom metric if you don't mind to use BikeScore instead of BikeStress/TSS.