strata weighted power
01-19-23, 10:51 PM
#1
Senior Member
Thread Starter
Join Date: May 2021
Location: San Francisco
Posts: 2,032
Bikes: addict, aethos, creo, vanmoof, sirrus, public ...
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Quoted: 1273 Post(s)
Liked 1,384 Times
in
708 Posts
strata weighted power
i’ve been tracking just about every ride i make for a couple years with strava, heart rate monitor, and power meter.
the riding app (original source of the data) i’ve been using for the last year was recently updated to fix a power curve display problem in strava. they removed milliseconds from the timestamps. this fixed the power curves completely, at least for any ride re-uploaded or new rides.
but …. somehow those new rides or re-upped rides are now showing significantly lower weighted average power, which is one of the metrics i track carefully over time for similar rides. typically on a ride with llots of stop and go or braking descents, the weighted average would be around 5-8% higher than the flat average. now it’s usually the same (even on stop and go rides!), maybe 1% higher.
i have strava sauce installed, and the sauce normalized power still works. as does the cycling app (cadence) normalized power.
all other stats in strava are unchanged, including total time, average watts, calories, etc.
any ideas WTF is going on here? how could the weighted average algorithm be significantly changed by discarding milliseconds on the timestamps?
the riding app (original source of the data) i’ve been using for the last year was recently updated to fix a power curve display problem in strava. they removed milliseconds from the timestamps. this fixed the power curves completely, at least for any ride re-uploaded or new rides.
but …. somehow those new rides or re-upped rides are now showing significantly lower weighted average power, which is one of the metrics i track carefully over time for similar rides. typically on a ride with llots of stop and go or braking descents, the weighted average would be around 5-8% higher than the flat average. now it’s usually the same (even on stop and go rides!), maybe 1% higher.
i have strava sauce installed, and the sauce normalized power still works. as does the cycling app (cadence) normalized power.
all other stats in strava are unchanged, including total time, average watts, calories, etc.
any ideas WTF is going on here? how could the weighted average algorithm be significantly changed by discarding milliseconds on the timestamps?
__________________
