Skip to main content
Monthly RAMP test

In order to track progress in power output and efficiency I am going to perform a monthly ramp test. This will take place every 4th week on the Saturday before the Tour of the Surrey Hills on Sunday. Just to be awkward I have reversed this week to avoid the bad weather.

Protocol
Pump up turbo tire to 100psi and pedal comfortably for 15 minutes, to allow me to warm up but more importantly the turbo to warm up. Then calibrate the turbo to 0. Warm up for another couple of minutes in case the calibration takes a while. The test proper can then begin, maintaining a comfortable cadence gradually increase the power output by moving through the gears. Target power output for 3 minute intervals are: 180, 210, 240, 260, 280, 300, 320. Finally, drop back to easy pedalling at 180w and wait for heartrate to return to level seen at the beginning of the test.

Results
Startlingly different from a 20minute 250w test yesterday that set my HR at 147 for the entire 20 minutes.
  • 3 min 180 - 118bpm
  • 6 min 210 - 120bpm
  • 9 min 240 - 130bpm
  • 12 min 260 - 137bpm
  • 15 min 280 - 144bpm
  • 18 min 300 - 152bpm
  • 21 min 320 - 159bpm
  • 25min Recovered

I found it quite hard to get to the target power output and stay on it consistently but then sometimes I was high sometimes low, I'm sure it all comes out in the wash. During the recovery period I sat up and pedalled without realising that made my heart rate go up again - won't make that mistake again. Thought it amusing that I hit 180w at 118bpm at 25mins on the nose - exactly 4 minutes to recover whilst pedalling at 180w.

It is VERY important to note that the Tacx is very optimistic in its power calculation, popular figure puts it at about 20% over, so that helps to normalise back to my 250w test which was on a gym bike. I will be using this protocol going forward since its on the turbo I own and far more easily reproduced.

Popular posts from this blog

W'bal its implementation and optimisation

So, the implementation of W'bal in GoldenCheetah has been a bit of a challenge. The Science I wanted to explain what we've done and how it works in this blog post, but realised that first I need to explain the science behind W'bal, W' and CP. W' and CP How hard can you go, in watts, for half an hour is going to be very different to how hard you can go for say, 20 seconds. And then thinking about how hard you can go for a very long time will be different again. But when it comes to reviewing and tracking changes in your performance and planning future workouts you quickly realise how useful it is to have a good understanding of your own limits. In 1965 two scientists Monod and Scherrer presented a ‘Critical Power Model’ where the Critical Power of a muscle is defined as ‘the maximum rate of work that it can keep up for a very long time without fatigue’. They also proposed an ‘energy store’ (later to be termed W’, pronounced double-ewe-prime) that represente

Wireguard setup for dummies

We all know that Dad is the IT infrastructure manager at home, so when it became clear that we needed a VPN for everyone to enjoy that infrastructure (aka access to streaming services) on their phones and laptops when they were away- it became Dad's job to make it happen.  My first instinct was to get a Unifi device since I've got lots of them already. Something like the USG or Dream Machine and use the hardware VPN support from there. But then I baulked at the costs for something with enough horsepower, anywhere from £99 to £350. I looked at their Edgerouter X and other devices like the Netgate pfsense and thought, heck, how hard can it be to install a VPN server on my Linux workstation and do it for nothing ? So I started with OpenVPN but couldn't get it to work or work out how to configure clients. So I switched to OpenVPN access server and couldn't even get it to install (I am using Ubuntu 23.04 right now and its not supported). I watched some videos from Cross

Implementing the Banister Impulse-Response Model in GoldenCheetah

Over January 2019 I implemented the Banister model in GoldenCheetah, along the way I learned a little about its strengths and weaknesses. This post is about that; explaining the Banister model and how it relates to the PMC , how it has been implemented in GoldenCheetah and what it's limitations are. I've also added a bit at the end covering some of the things I'm looking to do with this next from potential model improvements through to deep learning. In some ways this post is a longer written form of this tutorial I recorded covering Banister and GoldenCheetah. The Banister Impulse Response model In 1975 Eric Banister proposed an impulse-response model that could be used to correlate past training with changes in performance in order to predict future improvements from future training. Originally proposed for working with collegiate swimmers it was reworked in 1990 for working with running and of course also applicable for cycling. Each type of sport needed a w