šŸŽ‰ šŸŽ‰ šŸŽ‰ Introducing Adaptive Training! šŸŽ‰ šŸŽ‰ šŸŽ‰

I think this raises an important point. Specifically, should the classification of the ride difficulty be focused on the difficulty of the final one or two intervals or the entire ride? Using Nate’s difficulty scale, if a rider considered the first 4 intervals ā€œhardā€, the fifth interval ā€œvery hardā€ and the final interval ā€œall outā€, should the ride difficulty be categorized as a 5 (all out) or a 4 (very hard) that reflects and average difficulty of all the intervals?

Further to this point, if a user needed an additional 30-60 seconds to recover prior to the final interval, and paused the workout to account for this, should the workout be categorized as a ā€œfailureā€ or should this pause be ignored when rating the difficulty of the ride upon completion?

In sum, I think it’s really important that TR clarify/answer questions like these so users are completing the post ride difficulty survey in a manner that will be most beneficial to adapting their subsequent workouts.

I would love the ability to ā€œtargetā€ these workouts and have a progression to get there. I’m training for Leadville and Gibralter +2 looks like good training for Columbine for big slow guys like me.

Indeed. And to expand on another point you mentioned, Nate said they tested the ML for assessing the TSS of a workout outside using only HR and cross referenced it to the actuals with the PM data included. He said that the ML TSS assessment is super close with HR only that you could use it as a proxy. Having a PM is obviously better, but still, that’s a huge boon for people who don’t have the budget for PM but want the benefit from the outside ride data once it gets added into the mix.

Going by the podcast I’m pretty sure they aren’t just using tss. Remember the main problem with machine learning is you need to feed it good data. Tss doesn’t really fully describe a ride so isn’t good data on it’s own. Quantifying a ride is hard

Pauses are accounted for in the ML, and a post workout survey allows you to tell it why the pause occurred. As has been mentioned several times in the thread, the ML is smart enough to know when those pauses are because the work was hard or because you got off to stretch or refill a bottle or something. And if it doesn’t know, it asks you why.

As for the 5-point scale, I think you’re over complicating it. A hard workout should feel hard. An easy one should feel easy. If you completed it but it felt All Out at the end, you mark All Out and it will adjust based on numerous features in addition to your subjective response to the post workout survey. And the more you do this, the more it will learn and the smarter it will become at defining your patterns.

If I want to add endurance to the end of a workout I just extend the cooldown and use the intensity button to increase the target power to the desired level. This way you can progressively up the intensity as the workout target power ramps down into cooldown. Intensity usually ends up around 250% for an endurance (cooldown) block.

Huh, plan builder had been awesome for me. I occasionally fail workouts, and have to juggle a few things, so this improvement is awesome, but plan builder was not a pile of ding by any stretch of the imagination.

So I didn’t have a plan built out yet and I did a plan builder run and dated the start date retroactively to when I started SSB1 in November and I’m getting recommended to pick up on short power build for a couple of weeks, although I’m not sure I’ll dive into something tough to start the weekend lol I haven’t seen any adaptations triggered yet, based on my current vo2 progression of 4 and going into a 7.2 straightaway doesn’t seem like something the AI would like lol

edit: so here’s the adaptations suggested, looks like it’s adjusting the sunday sweet spot but not the Sat VO2. Come on man! lol

For some reason I thought intensity increase stopped at 200%. That may have been some time ago(older software) as I’m not often increasing to that level. :stuck_out_tongue_closed_eyes: I think that is what I’ll do going forward.

the red arrow means a recommended adaptation, in this case a less intense sweet spot session

The max is well above 200%, because I use 220% repeatedly for adding Z2 with cool down extensions.

I can search, but I think it’s at least 300% and maybe higher.

Chapeau @Nate_Pearson and the whole TR team. This is absolutely awesome. Clearly a huge amount of work has gone into developing these new features, and I cannot wait to see the results on my training.

What is really exciting is that it should help to answer many of the ongoing questions related to the best structure for a training plan (periodized, pyramidal, traditional base vs sweet spot) and how much volume is needed for gains and what is a minimum effective dose. Most studies on these topics are necessarily based on a few self-selected participants in artificial scenarios. TR’s ML and huge data resource should be able to discern real-life results based on a wide-range of athletes. This will be a huge game-changer, not just for TR, but training in general.

One specific Q, and one area that I do not think has been mentioned so far, is how does your power curve feed into plan adaptations? And in particular, new power PRs. This is most relevant to data from outside rides, races etc. For example, during the course of my last two training blocks I have set a whole new set of PRs, but the majority of those have been when racing hard online. Of course, they are a result of the inputs (the training I have completed), but they too are a data point as to the power I can currently hold for a given duration - so will that also be taken into account in the progression?

Totally. I simply referenced TSS as that was the specific example that Nate mentioned for the HR analysis for outside rides.

Here is the exact moment he talks about it in the podcast from yesterday.

I just keep waiting for an email saying I’m in the Closed Beta group.

:heart:

It worked based off of ramp tested ftp. Here’s a bowling analogy. The old system had bumper rails, but no strike guaranty. Now the system is going to start steering your ball down the lane. Time to expect more a lot more strikes. The perfect 300 is probably years away and will require integration of additional sensors, but we are on our way.

Yes, I think it was a change last year.

It did create a rest day next Friday but that’s the only rest day created. Not sure about picking lower volume and having it build up, that may be something folks would want to do using the TrainNow feature

That would make you legendary in the forums…

:rofl:

Given that he stated there’d be one more wave of invites to VIPs, and that bugs are already cropping up, I think it’s probably fair to guess that the rank-and-file rabble will be seeing invites in 1-1.5 months

ā€œSkynet is right, it can do no wrong.ā€
Now repeat this ou load so the microphone on the laptop can pick it up