Andy,
Is there any way to limit the range of durations use to compute mFTP?
Occasionally, my powermeter will spit out a erroneous reading that completely skews the mFTP for all dates within 90 days of the error. For instance, on 10/21/2015, the data from my ride showed a one second reading of about 3,300 watts. The one second readings adjacent to this were both under 200 watts. However, mFTP for all dates within 90 days of this date jumped up about 30%. As a TT-type rider, I would like to eliminate erroneous readings from the computation of mFTP without having to review the data for every single ride for anomalies. This could be done, I hope, by being able to limit the range of durations to say, 15 seconds to 1.5 hours.
Mike
Is there any way to limit the range of durations use to compute mFTP?
Occasionally, my powermeter will spit out a erroneous reading that completely skews the mFTP for all dates within 90 days of the error. For instance, on 10/21/2015, the data from my ride showed a one second reading of about 3,300 watts. The one second readings adjacent to this were both under 200 watts. However, mFTP for all dates within 90 days of this date jumped up about 30%. As a TT-type rider, I would like to eliminate erroneous readings from the computation of mFTP without having to review the data for every single ride for anomalies. This could be done, I hope, by being able to limit the range of durations to say, 15 seconds to 1.5 hours.
Mike