davidtinker

Thanks! Intervals.icu is busy updating everyones activities right now. I finally got some stuff working to automatically detect and fix power spikes in rides. Those make a real mess of the stats otherwise. I will post more info soon.

If you are one of the lucky ones with an estimated FTP of more than 600 be aware that it’s not going to last. Busy working on better power file cleanup and anomaly detection.

I don't know much more than what I learned from Joe Friel's blog. I personally mostly don't have the time to ride more than approx 8-10h a week. Not sure if there is anything much I can do about endurance for 4h rides with that

It uses it for future activities. You can change your FTP on old activities and it will recalc training load etc and update the fitness chart. The "list view" on the activities page is handy for bulk editing. If you change your FTP on your most recent activity it will also update your FTP in settings for future activities.

Tx .. this bit is most relevant to the current discussion: Weeks 2-3 At this point, your maximal oxygen uptake 
(VO2 max, the prime measure of your aerobic fitness) will have declined by anything from four to 20 per cent. So thats a 4 to 20% decline in FTP after 2-3 weeks of nothing. The max decay factor in Intervals.icu is 0.998 per day but that gets adjusted up (less decay) if you are still doing some training. Thats a 5% drop after 21 days. Maybe I need to bump that up or make it configurable.

Thanks! Currently it only uses the model for future activities but I could do some work on that. More for the todo list

You can just ignore it and choose not to enter that as your current FTP. That said I am still tweaking this especially the decay rate and appreciate this sort of real life feedback. On the 1st of May you did some good power and reached an FTP of 304w. That part I think is probably correct. You continued training at a similar level until approx 29th of May so the estimate remained at 304w. After that it started decaying reaching 298w on the 12th of June. You haven't been doing nothing over that time or it would have decayed quicker. Its quite possible that the decay rate isn't quick enough. On the other hand should 2 weeks of half usual training load cause your FTP to drop drastically? Obviously if you were sick during that time the impact would be more but I don't have that info. Any coaches out there have an opinion on this?

Currently you need at least 8 previous activities with power and HR and then Intervals.icu will use that data to estimate training load for activities with only HR. It basically figures out "training load / hour" for a given average HR. I could implement a default model to use in the absence of any power data that used only HR. Will look into that. Would probably need to know your max and resting HR.

+1. I want to make it work nicely on tablets at least. Need to support touch events and whatnot for that. More work would be making it fit on a phone. It actually runs on my iPhone 8+ but the calendar view and other things need "small screen" work.

This was almost a road race

Its on a new strip chart at the bottom of the /fitness chart. You might need to shift-reload the app or close and re-open your browser tab. You might also need to choose "Options" on that page and tick "Show FTP" and "Show Estimated FTP" but those should be on by default. Its going to appear in various other places very soon (e.g. on each activity) and I am also not sold on the magenta colour. Clashes with cadence on the activity timeline chart.

What views? I saw one little rabbit run across the track in front of me, otherwise was flat out and no time to look at anything! Never done such a fast MTB race. Thats me in the Hermanus Pharmacies kit in one of the pics above.

You are not supposed to be able to see that estimated FTP line yet Thats a bug.

It uses any max effort of between 60s and 30m to place you on a predefined power curve and then uses Morton 3P parameters from that curve for your power model. This has the advantage of only needing one effort and not a particular set of efforts like Morton 3P to get good results. The Morton 3P stuff is way out if you don't actually have max 5s, 2-3m and 10m+ efforts. Please mail me (david.tinker@gmail.com) your Strava ID (go to "My Profile" and get it from the browser address bar) and I will have a look. I am using the new algorithm for "continuous" FTP estimation like Xert does, but its not helpful if the numbers don't seem right for lots of people.

Can you please email me (david.tinker@gmail.com) a link to the activity on Intervals.icu. Then I can have a look and see whats up.

The Elevate PSS (TSS / Training load) scores are within 1 of mine so its normal TSS. The fatigue and fitness numbers are also very close so also the same algorithm. What Elevate does differently is "todays form" = "yesterdays fitness - yesterdays fatigue" whereas I do "todays form = todays fitness - todays fatigue". So with Intervals.icu you are seeing your form after whatever riding you did vs Elevate showing you what your form was before you did any riding. Not sure which is better or more standard.

Tx. I am having a look at Elevate now. If they are doing the same Coggan chart then the numbers should be pretty much the same. Does Elevate give the "weighted average power" / NP numbers for your rides and do the rides have the same FTP set? Those 2 determine training load / TSS which is what is used to calculate ATL (7 day) and CTL (42 day) exponentially weighted moving averages.

The "model fit" is the r^2 value which is a measure of the distance between the line and the data points. So bad isn't necessarily a problem. You can see visually if the line is fitting the points well or not. I don't think its worth a lot on a l hr ride.

Tx a stack! I have made good progress with improving FTP estimation over time, expect to get some more of that live this weekend. As always suggestions for improvements welcome.

Tx. I am working on FTP and W' estimation from random hard efforts in rides rather than actual tests. The FTP estimation Intervals.icu has now works very well only if you have done max 5s, 2-3m and 10+m efforts within a week or so. I have learned a lot more about this problem over the past few weeks (from Alex from FastFitness.Tips) and other sources.

Have a look now. There is a "Use Laps" button under the ride timeline chart. It still does some analysis on the laps to see which ones look like intervals (is power high enough relative to FTP and duration?). I often use the lap button to watch avg power for lap when riding Z2 to make sure I don't sneak into Z3. Don't want that to be an interval.

What I would really like is to get the detection good enough to not mess up intervals like yours. Those sharp spikes at the beginning of each one are the problem. I will look at adding a "detect from laps" option. Not hard, just an admission of failure but better than making you edit all of them.

Thanks. What do you mean by "HRV"? People have different understandings of the term.

I have had a first shot at implementing this and I think the whole fitness chart is a lot more useful and easier to read as a result. Tx.

Thanks! Always keen for new feature ideas. That article is quite interesting and I will certainly look at implementing something like that. I suspect Xerts "training pacer" is TSB arranged into zones in a similar way.