peterwright said:Thanks for the insight all. Ric - it was 60 mins into the ride but the previous 60 mins had been moderate and this was the first climb of the ride - 12.5 mins @ 96% FTP (the last 6 forming part of the peak) then we pretty much cruised for 3.5 mins then we hit a real mother of a climb and I really hit it very hard (in fact I underestimated the length of it and rode the first 2 mins at 137% FTP and the whole lung bursting 6.45 mins of it at 126% FTP)
So I just have a problem understanding how this 20 min period can be a peak when there were 2 distinct high peaks with a distinct rest period in between.
If I look at my MP curve then the 20 min is a "blip" and I do not think that I could ride for 20 mins at an NP of 110% FTP.
Correct me if I'm wrong, but it sounds like there are really two separate issues that have you scratching your head:
1) the fact that CyclingPeaks picked that double-humped effort as a single peak, and
2) the fact that the normalized power value for that effort overestimates (by about 5%) what you could actually sustain for that duration.
#2 is explained by the fact that, while the algorithm is surprisingly robust, it clearly ain't perfect. #1, OTOH, is simply the way CyclingPeaks works: the highest (peak) value for any duration is used, e.g., to draw the mean maximal power curve, regardless of how that value is obtained. So, a double-humped effort such yours may result in a "blip" on the curve regardless of whether it is based on average or normalized power.