I’m a new user of Intervals.ICU. I’m having trouble with the FTP setting. I don’t recall putting it into Intervals.icu, so I assume it was pulled from Strava. However, they aren’t matching. Strava shows my FTP since June 5 as 252. Prior to that, it was 234. Intervals.icu shows 258 for all my rides. Is there any non-manual way to fix my past rides? Related, if I change the FTP on my settings page, will it only effect future rides?
Yes the Intervals.icu FTP setting is initially pulled from Strava but after that it is independent. Strava only recently added support for FTP history and I am not sure if that is exposed via the API.
If you change your Intervals.icu FTP in settings it only applies to future rides. You can use the “Edit” button on the calendar page to set FTP on older activities for a date range. You can also switch the calendar to list view and edit FTP directly on the grid.
1 Like
Thank you, that worked perfectly. Separate question: I’m transitioning over from TrainingPeaks. Comparing load/TSS between the two platforms, I’ve noticed it’s very similar for some rides, but pretty different for others (77 vs 60, for a recent ride). My mountain bike rides seem to have the biggest variances (TP is consistently higher). Do you know if there are differences in the formulas? My MTB rides tend to have more high-zone power, but also more coasting and rests. FWIW, my TSS scores on MTB rides have always felt inflated with TrainingPeaks.
Intervals.icu uses the standard formula which is the same as TP (as far as I know):
TSS = intensity * intensity * hours * 100
intensity = NP / FTP
The differences come in via FTP (not the case here) and the hours. Intervals.icu doesn’t count “not moving time” (coffee stops etc.) whereas I have been told that TP does. So it could be that. I looked at a recent MTB ride of yours (https://intervals.icu/activities/3999127233) and there is quite a bit of not moving time. You can add the “Moving” chart to the ride timeline to see this.
1 Like
TP does a lot of weird stuff with the data. They’ve said they can’t always distinguish between a connection dropout and being stopped or coasting, so it often changes power data from zero to something else. I’ve noticed many times when I was completely stopped, my data graph and grid will show a very unnatural straight line connecting the 0 power to the time where I actually start pedaling again. Cadence and power will look like 0, 2, 4, 6, 8, etc. to 300 or whatever. Makes no sense, though, since speed is zero and position isn’t changing. In my experience so far, Intervals.icu seems to be more accurate.
1 Like