60_min_Peak_Power/75*1000/Athlete_Weight/((60_min_Peak_Power_HR-config(rhr))/(config(maxhr)-config(rhr)))
and 60' min Peak Pace and HR during that effort (available on v3.5 development builds) for running:
(210/60_min_Peak_Pace)/((60_min_Peak_Pace_HR-config(rhr))/(config(maxhr)-config(rhr)))
If you don't have regular steady 60' efforts the duration can be lowered to 30' or 20', it seems to be an interesting way to look at the HR vs Power/Pace relationship.
I wonder how relevant this chart would be for non-steady state sports like mountain biking, where Normalized Power is more useful than Average Power?
I guess aggregating is deliberately set to "average" instead of "peak" for the NP derived curve?
Ale,I think this formula needs to have a condition to compute only when HR is present. If HR recording is absent, the graph messes up. Would this be a correct assessment?
Does anyone know the differences between the extended model Vo2Max Estimated & the 'Estimated VO2Max'?
I see I can call Estimated_Vo2Max in a function, but estimate(ext, vo2max) does not return anything.
The "Estimated VO2MAX" metric is based on your measured Peak 5' WPKg, it has the following description you can see hovering the mouse over the metric list on config: "Estimated VO2max from 5 min Peak Power relative to Athlete Weight using new ACSM formula: 10.8 * Watts / KG + 7 (3.5 per leg).", the model estimate uses the same formula but it is based on model-derived 5' WPKg.