As I understand it from the Firstbeat website, the Garmin 530 requires a stable vo2max estimate. So that takes some time after restarting training. I had 3-4 weeks from the end of August to mid September without basically no riding/training, and it did take a week or two to get my first downgraded FTP estimate. I didn’t trust the first couple of estimates, but was training by HR when coming back and really didn’t care about FTP at that point.
That said my outside workouts happen to align with the VO2max estimate recommendations: solo and sustained 20+ minute efforts where power is fairly constant, HR doesn’t change much, and HR is >70% HRmax. And FWIW, my current fitness age is 25 and I’m about to celebrate the 35th anniversary of that age
Good to know it’s Garmin Firstbeat waiting for a stable VO2. It makes sense.
I’m due another ramp test after a recovery week starting Monday. It’ll be interesting to compare the various estimates that come from that with what I can do on the bike.
Can’t wait! I know every individual is a single non-representative case study, but for me ramp tests (whether TR, zwift, or others) have never provided a good training baseline number even though it obviously works well enough for the vast majority (then again, 20 minute tests haven’t been much better). Having something that will update regularly without having to test and that will integrate well with AT seems perfect for how I use trainerroad.
Not everyone will like it, but I would hazard a guess that the vast majority will (it might be the more vocal people that don’t like it though). For those that don’t like it, the formal tests are all still there. Best of both worlds
Not sure why people wouldn’t like it—everyone’s got the option to select which of the testing methods they like. It’s an additional protocol anybody can add to their available tools.
I am looking forward to it so I can compare the estimate with a ramp 2-3 times and just let it take over from there. I used to do the 4DP test from sufferfest or 20 min tests before that; the exhaustive longer efforts are good proxies for experience in time trials and triathlons but they were definitely a mental beast… had to treat each one like a race, almost!
I’m not sure that there is a rational reason for not liking it, but when has that stopped people? As evidenced from many of the threads on the forum, and from this one, the slightest suggestion of a change will rapidly cause some people to overreact and think the apocalypse is coming. I think it will be great for the vast majority.
There will be those that don’t want to use it - not a problem as they will be able to continue testing as normal. There will be some that go for a hybrid approach, mixing the suggested FT updates with occasional testing. And there will be some that take personal offence at the slightest suggestion that other people might not have to do a test.
Had time to listen to the podcast covering the FTP estimate feature in more detail. Nate explained that it is not derived from a power curve matching a max effort. Also, it would have a sense of accuracy to it in the proportion of how much data you have under your profile that qualifies for quantification of the effort.
Sounds like an alternative way to approach it that would greatly reduce the risks that I pointed out in the opening post and my last comment to this thread. Let’s see what they come up with. I’m excited
It’s like the restaurant biz, you could have exceptional service with every meal being delicious. You’ll still get bad feedback, can’t please everyone. If you please the majority you’ll retain a solid customer base and that will grow regardless.
Oh my lanta I can only imagine never being able to escape from “Antelope” and “Buckhorn” because your changing ftp is always resetting your AT levels to 6
To solve this, have you considered allowing people to schedule an FTP estimation, and then TR could run the estimation overnight? For example: let’s say I know I’m going to have a test week the week of January 31, and I schedule TR to give me an estimated FTP on January 31. TR could run the estimation between midnight and 5am local time on Jan 31st, so when I get up, the estimated FTP shows up in my account.
This would have a couple of benefits: for the user, there is no delay. For TR, as the user isn’t waiting in real time for an estimate, you can better load balance running the estimation.
I won’t be making many friends but why are so many resources invested in this?
Why are many so many people so afraid to do a 20 30 or longer minutes test? Are they afraid of discovering their FTP because they associate it to their real worth as a cyclist or what exactly is the problem?
Any estimate can only be derived by all out efforts which for longer durations means… Doing a proper FTP test.
I mean it’s nice to have software that can detect any improvement and so on but not if it comes at the expense of other projects such as improving training plans.
As evidenced from many of the threads on the forum, and from this one, the slightest suggestion of a change will rapidly cause some people to overreact and think the apocalypse is coming. I think it will be great for the vast majority.
.
