Strava Shootout Week 3 – Smyer KOM

Posted

in

We are nearing the end of Week 3 of the second annual Birmingham Strava Shootout. Basically, we pick a different climb each week and then see who can get the fastest time up the climb. Mark Fisher has been crushing it (and crushing a lot of my KOMs along the way) so when he laid down another smoking fast time yesterday crushing by 20 seconds my KOM on the long version of the Smyer climb, I knew that I was going to give it everything I had to get back the KOM today.

The rock where I left all my stuff while I was going for the KOM

I did a new version of the endless Vestavia climb at a really easy pace to get nearly an hour of warm-up in before my KOM attempt. I came into the KOM from the top so I dropped all my stuff off (water bottles, tools, pump, food, iphone, etc…) behind the rock shown in the picture above. Then I drilled it down the descent to keep my legs loose and ready to go at the turnaround at the bottom. I forgot to look ahead of time to see what wattage I should be able to maintain for 6 minutes, but I guessed it should be around 425 watts. I made the final decision on that wattage as I was descending and kept telling myself not to go too hard at the beginning.

As narrated in the video, I started out by looking at the wrong wattage number (3s wattage which happened to be 370watts at the moment when I looked instead of the Lap wattage which was actually 470 watts at that point). After I figured out that I had looked at the wrong wattage number, I settled into a good rhythm backing off my initial pace so that the power average drifted back down towards 425 watts. The last time I looked at my wattage was near the Brookwood Metro back entrance road where the wattage average had dropped to just below 450 watts. I looked at my average speed a few seconds later as I turned onto Smyer and I had a solid 18.8mph average through that point. This gave me a ton of motivation because I was expecting to be closer to 18 flat and was afraid that I would even be under 18 based on the fact that I was trying to be more conservative through the opening part of the climb.

Up ahead I could see two other riders side by side as they entered the switchback portion of the climb. I was on them really quickly and had to pass them on the wrong side of the road because there was no time to yell and wait for them to get out of the way. Fortunately, I had a clear view through the switchback and was able to pass them very quickly and get back onto my side of the road. There was a good tailwind through the 280 overlook section so I entered the flat section before the next set of switchbacks with a ton of speed. I got a bit overconfident at this point as I tried to hammer through the next switchbacks in too big a gear leading to quite a bit of bogging down. I upshifted into an easier gear at the Hurricane Ivan landslide/washout area to try to get back on top of a gear and proceeded to nail the deepest pothole in the washout.

I happened to look down and see my time as I rounded the last turn before the straightaway leading to Shades Crest, and I saw a time of 4:00 or maybe it was 4:05. This caused a lot of mental anxiety/consternation because up until that point I felt really good about my prospects of getting the KOM, but when I saw that I was already up to 4 minutes, I wasn’t sure if that was going to leave me enough time to get to the top. I don’t normally ever look at the time through that section so I had no clue how much time was left in the climb. Those thoughts/doubts were quickly dismissed as I saw a group of riders strung out climbing up from the steep portion of Shades Crest Rd crossing the intersection that I was barreling towards at 20mph. Normally, you have to time the merger to slide into the road either in front of or behind cars that are coming up the hill. The still image screenshot in the video at the top of this post is a picture of that intersection (Shades Crest is the road coming up the hill from the left).

If I wasn’t digging so deep, then I probably would have laughed at the irony of having to time that intersection based on riders coming up the hill instead of cars. I found a hole to dive into and then passed the rider who I had slid in behind. He cheered me on as I came flying by, and that helped motivate me to push it really hard through the sharp steep turn onto Smyer Circle and then the flatter drawn-out ending of the climb. When I hit the lap timer button, I saw 5’55” and I was about ready to fall off my bike.

It’s funny, too, because I was really trying to discipline myself to maintain a 425 watt average throughout the climb instead of starting out too hard and then watching the power drift down. I ended up hitting my 425 watt target wattage exactly even though I cannot recall ever looking at my wattage again after passing the Brookwood Metro entrance. Speaking of wattage, when I loaded this ride into Golden Cheetah, I first noticed that my effort was indeed a new maximum that extended all the way to the edge of the critical power curve. But then I noticed that my CP curve had been dropped from 305 watts down to 293 watts. I’m guessing that this has something to do with a better fit to the curve. The good news is that this shift in the curve means that I theoretically have a lot of “wattage-room” to take back the shorter KOMs on Old Montgomery and Big Momma that Mark got the last couple weeks. But it seems strange that my new curve predicts a new, lower 1 hour wattage of exactly 300watts instead of the previous prediction of 315watts based on the new 293 CP wattage vs the old 305 CP wattage. Can any power/golden cheetah/critical power experts out there weigh in on how this ride would cause my curve to shift? I’ve included three screenshots below that show my CP curve before updating with the Old Montgomery KOM effort, after updating with the Smyer effort, and then one that shows the CP curve with today’s Smyer effort in black before Golden Cheetah had updated the CP curve. Thanks!

305W CP curve with the Old Montgomery KOM effort shown in black (click to enlarge)

293W CP curve updated after my Smyer KOM effort — shown in black. (click to enlarge)

305W CP curve with the Smyer effort shown in black. This is the screenshot before Golden Cheetah updated the CP curve to a 293W CP curve. (click to enlarge)

Smyer power map annotated with 30second power averages (click to enlarge)

Smyer KOM lap summary data (click to enlarge). I thought it was interesting that my xPow (normative power) was lower than my average power. I’m pretty sure I was pedaling the entire time so I’m not sure why there is a difference between normalized power and average power?

Finally, I’ve posted screenshots from the ride and also taken some screenshots from the video showcasing the beautiful fall colors. These are in the gallery below. Enjoy!

Comments

One response to “Strava Shootout Week 3 – Smyer KOM”

  1. Frank Marrs Avatar
    Frank Marrs

    Brian,

    It looks like Golden Cheetah uses a quadratic regression curve between CP2 and CP180 to estimate mean maximal power. So, when you significantly increase a max at one end, it is natural for the other end to fall. I would guess that your theoretical CP2 to CP6 values are higher than before. This makes sense from a general perspective: someone who is significantly improving their fitness at high power levels may see some fitness tailing off at lower power levels. Finally, it’s possible that the regression is weighted more heavily at certain ordinate points (i.e. zones like CP2,6,30,60, etc.) and you may have hit very close to one.

    As far as commentary, it looks like the updated Cheetah curve is a much better fit for your data. I know you race with your power meter and have LOT of data, so I would guess most of your mean maximal powers are very close to realistic for you (even up to CP120 — see breakaways). I think it’s better to work off past data — when that data is efficacious — than off theoretical max powers anyhow.

    Frank

    p.s. I enjoy reading your blog. Keep it up!

Leave a Reply

Your email address will not be published. Required fields are marked *