| Power Training This is the place to talk about training and racing with power (watts) measuring devices such as Polar 710/720, Power Tap, SRM or any other power measuring device. |
| | |
![]() |
| | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
| |||
| |||
I'm new to power training (just got my PowerTap in the last month) and was looking for some guidance from those experienced in training with a power meter. I followed what seemed like the standard wisdom and have tried to record my 5min and 20min watts/kg as a baseline. For the 5min, I was able to find a steep 5min long hill and do an average of 370watts, or about 5.5 watts/kg. I've had a harder time finding any non rolling 20 min route where I live and have a hard time not having my watts go all over the place, so the best I've done for 20 min is an average of 275 watts, or just about 4 watts/kg. So I've got two questions. First, does it sound like I'm doing that baseline testing right? Do people manage to get consistent watts for 20 minutes in rolling hills? Second, assuming that my testing is right, it seems like my 20 min is relatively worse than my 5 min based on the charts I've seen. What sort of rides would help target FTP to improve the 20 min power? I mainly ride triathlon's, so improving FTP seems more critical than having good short burst power. Thanks for any insight, -Joe |
|
#2
| ||||
| ||||
Quote:
Quote:
If you're on the impression that for this test, type of course wasn't ideal for generating sustained power, then result might have been different on some other course. That doesn't matter all that much, because as you continue logging in some training, best sustainable power over 20min will be reached Quote:
This is why it is very important to not care about AVG power over 20min as much as Normalized Power over 20min. Did you use Normalized Power in your analysis for this 20min test? Quote:
I'd say that any work lasting 20min or more with Normalized power that is close to max for this duration will pay off a lot. The 5.5 w/kg for the 5 minute test suggests that you are relatively gifted on the fitness side (especially Vo2Max), now you need to use wko+ along with your powertap to "tap" into triathlon specific type of work. My favorite test is quite simple: 60min all out for this duration. Period. Because that factors in my Pacing ability. But anywhere between 20min intervals to 90-120min rides (tempo) will greatly benefit to improve your time-trial skills. |
|
#3
| |||
| |||
Thanks for the response. I don't have wko+, I've just used the PowerAgent program that came with the PowerTap. I don't think that gives Normalized Power (at least if it does it isn't obvious). I gather from your post that wko+ is the right tool to go along with the power meter. I guess I'll give the trial version a spin... Thanks, -Joe |
|
#4
| ||||
| ||||
Your Powertap purchase was the first and most important step in allowing you to train smartly, now the second most important step is using it along with the appropriate software, and that is wko+ Without being in the *knows*, I suspect Saris to not be in a hurry to improve their agent, since they know there`s something out there that is doing much more than they could ever hope. What I am trying to say is that I am not even sure that significant r&d is allocated to try and match wko+ If I was them, I wouldn't even try. - - - - - Now, you still don't know the result of this 20min test on rolling terrain. Avg is irrelevant. You'll have to wait and get computed average which is what's called Normalized Power. This important variable will put more weight, give more importance to intense work, thus raising the average so that it can precisely quantify what this training dose / test actually was. You basically get a value that represents what this workout might have been if performed on a flat terrain (somehow). In the mean time, there would be nothing wrong in using this 275w as a tentative FTP baseline. Worst case, later down the road you may need to adjust it. Or you may start with a value that is little underestimated (that is what I prefer, for what it's worth). When you first install Wko+, you'll quickly be asked about your FTP, since it is probably the most important parameter for the good functioning of the program. What about plugging in 270 and see if it makes sense later after 2 weeks of workouts. But again, I know many won't agree with me on that. So take it as you want. But as a triathlon specialist, to me, there's just one very valid FTP test and it is a flat 60min on a course that allows for riding this duration with no interruption. I do them on a FormulaOne race track (I am very lucky). You live near New-York, friends of mine love testing on Mount Whiteface. There you have a 60min climb with no cars (from 6pm or 6:30 pm). Or even better mate, just check in to an event of secondary importance, race with your powertap. Perform the Tri as if there was no running leg, and take it easy during the 10k. That will give your your FTP right there, with the motivational edge in bonus. Last edited by SolarEnergy; 07-14.-2009 at 01:56 PM. |
|
#5
| |||
| |||
Quote:
You can calculate it without WKO+, just need to export the file from poweragent to a spreadsheet and run the calcs on it there. It's not a difficult calculation in a spreadsheet. But it's a pain if you wanted to do it for every ride (which for other reasons is a very useful thing to be able to do). WKO+ of course does it automatically and has many other features making it an excelent addition to your "train with power" suite of tools. If over time, with improved knowledge and experience of the data and your performances, you realise your original FTP estimate wasn't correct, well you can always adjust it post-hoc.
__________________ Custom Training Plans -- cyclecoach.com -- My Blog -- Power Meter Hire in Australia |
|
#6
| ||||
| ||||
Quote:
Would 20min MMP be the border line? 20min and less should use AP and longer should use NP? |
|
#7
| |||
| |||
Quote:
Alex's Cycle Blog: The seven deadly sins and this: Alex's Cycle Blog: The Sins of Sins (Testing FTP #2)
__________________ "It takes all the running you can do, to keep in the same place." |
|
#8
| ||||
| ||||
|
#9
| |||
| |||
I can't speak for Alex, but I'd say NP is good for 45 but where you start to get into trouble is NP for 20 then layer that with something like NP_20*0.95 as a way to estimate FTP. Basically that takes a swag at the shape of someone's Monod curve (.95, .92, .97 take your guess but it varies between riders and their AWC to CP ratios) and then uses the NP algorithm which attempts to model overall metabolic stress, not specific intensity at shorter durations and applies it at the short end of its useful range. Get far enough out onto the flatter portion of the MMP or Monod curve and using NP makes a lot more sense as AWC contributions are a lot less, the curve is much less steep and you're effectively using a tool (NP) that models metabolic stress to estimate an intensity that's almost entirely metabolic. -Dave |
|
#10
| ||||
| ||||
Quote:
My only question would be. Why do they call this testing protocol "deadly sins"? I just don't get the pun. Anyway. Thanks. |
|
#11
| |||
| |||
Because the original post on the topic by Dr Coggan identified 7 methods for determining FTP, and presumably "the SDS" was a catchy title. It's stuck ever since.
__________________ Custom Training Plans -- cyclecoach.com -- My Blog -- Power Meter Hire in Australia |
|
#12
| |||
| |||
Quote:
For me it's probably 30 to 40-min and up is OK for the purpose. For others, shorter durations are OK. But for hard ~1-hour highly variable efforts, NP will be closer to FTP than AP. Some data for just me: Pre accident I've had 20-min NP of 373W & 371W on separate occasions and there is absolutely no way I had an FTP north of 350W !! Post accident I've had 20-min NP of 312W twice and again there's no way my FTP is > 295W. In my case those 20-min NP numbers represent 118% and 116% of FTP at the time, respectively. Or flipping it over - my FTP was/is 84% and 87% of 20-min NP, respectively. Comparing to mean maximal average power for me: 20-min MMAP was/is 104% and 107% of FTP respectively. Or FTP was/is 96% and 93% of 20-min MMAP respectively. Also, based on data for myself and clients, ratio of FTP to 20-min MMAP: Average:_____92.7% Std Dev:_____ 2.3% Min:________ 88% Max:________ 96% Avg +/- 1SD: 90% - 95% The data ain't perfect but it's a pretty reasonable indicator.
__________________ Custom Training Plans -- cyclecoach.com -- My Blog -- Power Meter Hire in Australia |
|
#13
| ||||
| ||||
Thanks Alex for having taken the time for this clarification. Really appreciated. |
|
#14
| ||||
| ||||
Quote:
- - - - Reason why that got me a bit confused I guess is this: At the end, PCM data is built upon NP data, not AP? If 20min long is so borderline as a duration for assessing FTP, then why is this duration included in the SDS list at the first place? Why not suggest the 30min long effort for instance? (anyway, I don't intend to reinvent this complex wheel in any way, just wondering...) |
|
#15
| |||
| |||
Quote:
Here's a link showing Andy's original suggestions and some good comments by wattage list regulars: How to determine your Functional Threshold Power | Two Wheel Blogs IIRC, Alex was pretty clear that he only included the 20 minute * 0.95 method because it is so commonly used and referenced by folks but even then AP and NP aren't in general interchangeable until the durations get longer. -Dave Last edited by daveryanwyoming; 07-22.-2009 at 01:44 PM. |
![]() |
| Bookmarks |
| Tags |
| beginner, ftp, question, targetted, training |
| Thread Tools | Search this Thread |
| Display Modes | |
| |
All times are GMT -4. The time now is 08:26 AM.
Translations delivered by vBET 3.2.2
Powered by: vBulletin Copyright © 2000 - 2009, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.3.0
Copyright © 2001 - 2009 cyclingforums.com
Translations delivered by vBET 3.2.2
Powered by: vBulletin Copyright © 2000 - 2009, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.3.0
Copyright © 2001 - 2009 cyclingforums.com














Linear Mode


















