You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most interesting rolling collector metrics are available in the main app bar at the top. The way it is now, it is not straightforward to visualize all interesting metrics. Why not having a new window (from "Settings/Management" -> "Add a new window") to allow to display them (max and current values for e.g. 15s, 1', 2', 5', 10', 20', 30', 60', avg, for power in w and/or w/kg, HR as well as FTP predictor). A bit like in Zwift Activity Monitor.
“Est. FTP” is an estimate of the FTP per time interval as per the commonly used time intervals: 0.95 for 20’, 1.0 for 60’ and above, 0.85 for 5’ and 0 below (5’ is already testing the maximal anaerobic power rather than FTP so it is a bit tricky to use that one, but as a rough proxy some research shows it is about 85%), and a linear interpolation for other intervals, i.e. 0.8566 for 6’, 0.8833 for 10’, 0.9625 for 30’, etc.
The text was updated successfully, but these errors were encountered:
Most interesting rolling collector metrics are available in the main app bar at the top. The way it is now, it is not straightforward to visualize all interesting metrics. Why not having a new window (from "Settings/Management" -> "Add a new window") to allow to display them (max and current values for e.g. 15s, 1', 2', 5', 10', 20', 30', 60', avg, for power in w and/or w/kg, HR as well as FTP predictor). A bit like in Zwift Activity Monitor.
“Est. FTP” is an estimate of the FTP per time interval as per the commonly used time intervals: 0.95 for 20’, 1.0 for 60’ and above, 0.85 for 5’ and 0 below (5’ is already testing the maximal anaerobic power rather than FTP so it is a bit tricky to use that one, but as a rough proxy some research shows it is about 85%), and a linear interpolation for other intervals, i.e. 0.8566 for 6’, 0.8833 for 10’, 0.9625 for 30’, etc.
The text was updated successfully, but these errors were encountered: