Rowsandall
Training diary and random remarks around my rowing
RSS
  • Home
  • Season’s Bests
  • Wolverine Scores 2015/16
  • About
  • OTW
  • OTE
  • testing
  • Privacy Policy
2speed

Sep 25 2016

Saturday – 2 speed Lactate test and some thinking

Time for the 2 speed lactate test again. The protocol is simple.

  1. Do a thorough warming up
  2. Row a 1k “at 6k pace”
  3. Take 15 minutes active rest, measuring lactate at 1 and 3 minutes
  4. Row a full out 1k
  5. Row a cooling down, measuring lactate at 1, 3, 5 and 10 minutes.

Then you plot the 1 minute values against power.

I started with a 20 minute warming up:

Then I did the first 1k:

Pretty evenly paced. I measured 5.4 mmol/L  of lactate after 1 minute and 4.5 mmol/L after 3 minutes. I paddled until 15 minutes was gone, at roughly 150-160W pace.

Then I did the second 1k:

I knew this wasn’t going to be a very fast 1k, so after 10 hard strokes at the start, I settled for 300W, then tried to crank it up with 500m to go.

So here is the result (lactate in mmol/L).

Measurement Lactate Power
1 min 5.4 270
3 min 4.5
1 min 6.1 315
3 min 8.1
5 min 7.2
10 min 4.3

The droplet of blood after 1 minute after the full out 1k was a little smaller than normal. I think the measurement was OK. It seems the lactate concentration in the muscle was just much higher and it took time to flush out the lactate. This would explain the higher value after 3 minutes.

Here is the graph of all 2 speed tests I had done in the past 12 months:

2speed

The chart looks like a game of Mikado (or pick-up sticks) and it is hard to understand what is going on. I have been rereading on Lactate, especially this article. I picked up my old simple numerical model and tried to model the recent three series of lactate step tests I did in September.

figure_1-2

Not an ideal fit but it is interesting to look at the parameters.

Nov ’15 Sep ’16
Pthreshold 200 195 W
beta 0.1 0.15
C_La rest 0.7 1.5 mmol/L
V_La_max 0.1 0.2 mmol/L/s

Pthreshold is the threshold Power. The parameter “beta” is a parameter which governs lactate usage as fuel in the aerobic pathway (higher values mean more lactate can be used as fuel during aerobic exercise).  “C_La_rest” is the rest value of lactate (which I measured today), and “V_La_max” is a parameter which governs how fast lactate is produced once you are above the threshold. So the hypothesis is that my threshold power has shifted to the left (bad), but I am better at burning lactate during aerobic exercise. At the same time, I have become better at producing a lot of lactate when above the threshold.

The model should be taken with a very big grain of salt. It’s all very crude and simplified at the moment. Take it as an illustration of my current understanding of lactate “science”. Instead of looking at individual test results, you have to build a model of how blood lactate is generated and used. In “Olbrecht” language, my Aerobic Capacity has slightly decreased, but my Anaerobic Capacity has improved a lot.

Now, if I knew what that means in terms of race performance, and how to use the result to fine tune my training plan … that would be great.

 

By sanderroosendaal • Uncategorized • 0 • Tags: lactate, lactate testing, OTE, rowing, training

crop-934191-12573138-10153714977365202-72418000985001647-n

Sep 25 2016

Friday – 20×60’/60′ rest

Thursday

My parents are visiting from the Netherlands, so training was squeezed for social reasons. On Thursday, I did a steady state session in the morning. Only 40 minutes, and because it felt very hard, at a low power. I just started rowing, following a few Wolverine Plan L4 stroke rate sequences, and stopped after 40 minutes:

Friday

Another session in the morning, to have the rest of the day for work (partly) and being a tour guide around Brno.

This time it was 20x1min/1min rest. In the past winter, I have done this at much faster average pace, but ok.

According to the PM5, I did an average pace of 1:43.6. We had a great night out at the Brno Opera theatre.

crop-934191-12573138-10153714977365202-72418000985001647-n

By sanderroosendaal • Uncategorized • 0 • Tags: ANC, OTE, rowing, steady state, training

curves

Sep 21 2016

Wednesday: 6k Test On The Water

So for today the plan said “Row 2x3k full out, short break just to turn”. After yesterday’s nice trip to the castle, I thought why not make it a full 6k, starting at the castle? On Greg’s blog post of yesterday, there was a discussion on training full pressure turns, and I think it makes sense to train with the mirror as well. This trajectory:

6k

So I set out to do a long (5.2km) warming up to get to the start line at the Veveří castle.

figure_1-2

Then I set off for my 6k. The plan was to row at 25-26 spm for the first 2k, then 26spm for 2k, and finally increase to 28-29spm. In the spring, I did some theoretical mechanical rowing efficiency simulations for head race pace, and it seemed that 27-29spm is the ideal stroke rate for a single. I really have to work on rating up but staying light, from the beginning of the row. I think it also helps with the pacing. When I start at 25spm, pushing with long strong leg pushes, after 15 minutes my legs start to be “empty”. This is actually exactly what happened today.

figure_2

figure_1-32

The average drive force is an estimate (assuming a constant stroke length). I think I was pushing too hard in the first five minutes, then lacking strength in the final 10 minutes.

Did I do the turns well? I have indicated where they are in the second plot. Here is a zoom in to the “serpentines”:

curves

I think that went pretty well. I slowed down only a little. With these turns, the idea is always to connect the turning points with straight lines. You have to look in the tiny rear view mirror and row towards the turning point, which is a few meters off the bank on the inside of the turn. Then you pass the turning point and head straight to the next one. It was hard, though, to find the turning points in the mirror. The bank is grey rock and green trees on a background of grey and green, and even the reflection of the forest in the water makes it green. Well, I managed, but I had to turn my head a few times to check. I would hate to run into the bank.

The other point I indicated in the graph is “wake”. At “Rokle”, I met a pair and two singles. Then, a few minutes later, with about 1500m to go, the coach’s launch passed me, going in the opposite direction. It wasn’t going fast and it didn’t throw a big wake, but because it was going at an angle to my trajectory, I ended up rowing in a small wake for a few hundred meters. At a point where I was really tired. The result was that I didn’t keep my technique up, started to row sloppy, and I slowed down a lot.

This broke me. I had been rowing with the aim to get the average pace under 2:10. The speedcoach had started counting a few seconds before I really started rowing at the start line, so I started at an average pace of 8:00, and gradually worked to bring that down. I was at 2:11.2 average pace when I entered the wake area, and 2:11.4 when I left it.

I finished in 26:11.0 minutes and an average pace of 2:10.9. Average stroke rate 26.3. Average heart rate 177 bpm. Pretty much a maximum effort but not well paced at all. I need to rate higher but row lighter in the beginning of the 6k.

figure_1-33

 

By sanderroosendaal • Uncategorized • 1 • Tags: 6k, lake, OTW, river, rowing, test, training

ss

Sep 20 2016

Cloud-based rowing

Don’t be scared. This is not another nerdy post about data and more data.

It’s just that it was a beautiful, cold, misty morning today. A cloud was resting on the water and just my head and shoulders were sticking out of it. First row this fall where I had to wear an extra layer with long sleeves.

I launched around 6:40 and this session turned out to be one of the most enjoyable ones of the year. It had everything. Rowing through a misty gorge, past rocks, a medieval castle, weekend houses. Seeing the sun rise through the mist (which blinded me for about 500m). Doing head race pace trial pieces of 30 seconds, just long enough to feel the boat rush forward and try to play with and optimize its speed, but short enough to not get tired. Then a long steady state section where I really fell into a groove. With the river turns and the great views, those 55 minutes passed by really quick.

Everything perfect, except a little rowsandall.com upload glitch. This happens only occasionally, and only on the FIT files, and I don’t know exactly what’s going on. The error happens in the part of the rowingdata code where I am creating the colored heart rate bars (this is code that Greg Smith wrote, but I “improved” it) and it leads to the data blowing up, creating 10 MB of data out of a 30 kB set of strokes. The funny thing is that it only happens in the on-line version, and not when I carefully repeat all the steps in an interactive Python session.

But enough nerdy data stuff. Here are the rows:

warming-up-9-20-2016
Warming Up

 

5x30"/45" Set 1
5×30″/45″ Set 1
5x30-45-set-2-9-20-2016
5×30″/45″ Set 2

 

Steady State & Cooling Down
Steady State & Cooling Down

So, first a long warming up of 15 minutes, crossing the lake and going through the windy part of the river.

Then I did 2 sets of 5×30″/45″ rest. I rowed at 28-29spm, deliberately limiting the stroke rate to what I intend to do in the head race. I worked on technique and tried to see the effect on the GPS pace on the SpeedCoach. Rowing clean, with a strong finish, and not too much pressure right after the catch. That’s the recipe I need to follow. I don’t understand why it’s so hard for me to not just do that every stroke. The SpeedCoach is very clear about this. Gives me 2-3 seconds per 500m.


Work Details - Set 1
#-|SDist|-Split-|-SPace-|-SPM-|AvgHR|MaxHR|DPS-
01|00126| 00:30 |01:59.0| 30.0| 149 | 158 | 8.4 #1
02|00145| 00:45 |02:35.1| 20.0| 154 | 160 | 9.7
03|00127| 00:30 |01:58.1| 30.0| 160 | 166 | 8.5 #2
04|00138| 00:45 |02:43.0| 20.0| 159 | 168 | 9.2
05|00124| 00:30 |02:00.9| 28.0| 160 | 167 | 8.9 #3
06|00145| 00:45 |02:35.1| 20.0| 162 | 168 | 9.7
07|00128| 00:30 |01:57.1| 30.0| 162 | 171 | 8.5 #4
08|00145| 00:45 |02:35.1| 20.0| 164 | 171 | 9.7
09|00129| 00:30 |01:56.2| 30.0| 164 | 172 | 8.6 #5
10|00145| 00:45 |02:35.1| 20.0| 165 | 173 | 9.7
Workout Summary
--|01352| 06:15 | 2:18.6| 23.8| 160 | 173 | 9.1


Work Details - Set 2
#-|SDist|-Split-|-SPace-|-SPM-|AvgHR|MaxHR|DPS-
01|00130| 00:30 |01:55.3| 30.0| 150 | 164 | 8.7 #6
02|00148| 00:45 |02:32.0| 21.3| 160 | 166 | 9.2
03|00127| 00:30 |01:58.1| 30.0| 163 | 169 | 8.5 #7
04|00142| 00:45 |02:38.4| 21.3| 164 | 170 | 8.9
05|00129| 00:30 |01:56.2| 28.0| 164 | 171 | 9.2 #8
06|00140| 00:45 |02:40.7| 20.0| 164 | 171 | 9.3
07|00121| 00:30 |02:03.9| 30.0| 164 | 169 | 8.1 #9 - Swans
08|00136| 00:45 |02:45.4| 21.3| 160 | 168 | 8.5
09|00131| 00:30 |01:54.5| 30.0| 164 | 172 | 8.7 #10
10|00140| 00:45 |02:40.7| 20.0| 165 | 173 | 9.3
Workout Summary
--|01344| 06:15 | 2:19.5| 24.3| 162 | 173 | 8.8

The second set is going through a big turn but the fast bits were done in straight segments. In interval #9 I was rowing in collision course with two swans, who seemed to be very cool about it. I don’t trust these animals at all, so I slowed down and turned, and I checked almost every stroke what they were up to. That slowed me down a bit.

The second set is faster than the first one. The power calculations seem to suggest that that is due to a more favorable wind. I thought it was because I had found the perfect head race stroke. Probably the wind.

Then I had a quick sip of water and continued to row up the river, now in head race pace. I turned at this point, where there is a small barrier in the river so you can’t row any further.

Here is a picture of another place I passed:

And here is a (spring) picture of the castle. I have shown it many times on this blog, but I simply love rowing in this scenery:

70852120

After turning back, I gradually came into a groove, trying to focus on technique. I was doing paces between 2:22 and 2:28 per 500m and gradually lowered the stroke rate from 22spm to 19spm.

figure_1-1

I took the average wind speed and direction to calculate the wind corrected pace. That is certainly correct for the river part (40 minutes and later) but I am not sure about rowing through the gorge. The water was mirror flat (or actually, green pea-soup flat because of an algae problem) on the row through the gorge. But yes, I think the 200W equivalent erg power is quite correct, considering my subjective rate of perceived exertion. Looking at the SPM part of the graph, you can nicely see how I dropped the rate during the row, while maintaining boat speed. One explanation is focus on technique. Another one is that it was helped by the wind.

figure_1-31

Total distance: 17.3km. I was on the water for 90 minutes, including a few drinking breaks.

By sanderroosendaal • Uncategorized • 1 • Tags: gorge, head race prep, lake, OTW, river, rowing, steady state, training

download-13

Sep 20 2016

Monday: 8x500m OTW

This week is a weird week. In my preparation for the 6km head race of October 7, I plan this as an intensive week, but at the same time we are getting guests from Wednesday afternoon to Sunday morning. Therefore, I had to plan my training with all OTW and the most important sessions on Monday to Wednesday.

Originally I wanted to do a 4x2km but I changed to 8x500m in the last minute, for three reasons:

  • Lack of time. With 4km vs 8km of work, the 8x500m is a faster workout
  • I hoped to be able to rate up to my head race stroke rate (27-29spm) a bit easier in the shorter pieces. A good opportunity to explore these stroke rates and learn how I am fastest at these intensities
  • A 2x3km (or full 6km) planned for Wednesday – too similar to 4x2km.

When I set out the lake was mirror flat, but as usual ripples started to form during the warming up. 20160919-072558-sanders-speedcoach-20160919-0726amo20160919-075314

I used the pre-programmed 8×500/2:30 rest from the SpeedCoach, failing to remember that the speedcoach doesn’t record data during the ‘rest’ period (they say that will be fixed in the next firmware update). The weather report for my location was:


Summary for your location at 2016-09-19T05:43:09Z: Mostly Cloudy. Temperature 54.19F/12.3C. Wind: 1.27 m/s. Wind Bearing: 22 degrees

I think that is about right. Seems consistent with my own observations.


Work Details
#-|SDist|-Split-|-SPace-|-SPM-|AvgHR|MaxHR|DPS-
01|00500| 01:58 |01:58.7| 27.3| 160 | 170 | 9.3 - tailwind
02|00500| 01:56 |01:56.5| 28.3| 165 | 174 | 9.1 - tailwind
03|00500| 01:58 |01:58.4| 27.9| 165 | 174 | 9.1 - tailwind
04|00500| 02:06 |02:06.0| 27.1| 167 | 175 | 8.8 - headwind
05|00500| 02:04 |02:04.5| 28.0| 167 | 176 | 8.6 - headwind
06|00500| 02:00 |02:00.5| 27.9| 163 | 173 | 8.9 - tailwind
07|00500| 01:59 |01:59.0| 27.7| 162 | 174 | 9.1 - tailwind
08|00500| 02:01 |02:01.2| 28.2| 160 | 172 | 8.8 - tailwind
Workout Summary
--|04000| 16:05 |02:00.6| 27.8| 164 | 176 | 8.9

The last time I did this workout was in June. Then I managed a 1:58 average at a stroke rate of 30spm. Today was a 2:01 average at 28spm. Sounds similar to me.

Also the pie chart looks similar:

I didn’t like how I was rowing. I had difficulty rating up and somehow I didn’t manage to get in the right rhythm. In the fourth rest period I understood why. I looked at my oarshaft and noticed I was rowing with a pair of sculls from our double. I have gotten used to the low-i sculls that I use in the single, and the normal sculls are now … different.

On rowsandall.com, I am working on a histogram of all erg strokes over a period of the past 12 months. Here is a prototype graph for my sessions:

download-13

The data are not really representative, because since the inception of rowsandall.com I have mainly rowed on the water, but still it’s an interesting graph to look at and see evolve over time. The beta testers had a lot of fun comparing each other’s graphs. One of the uses could be to check if you are really adhering to a polarized training plan.

By sanderroosendaal • Uncategorized • 1 • Tags: 8x500, lake, OTW, rowing, single, training

figure_1-29

Sep 18 2016

Power Measuring in Rowing – Book Review of “Training and Racing with a Power Meter” with a rowing angle

A few weeks ago, I ordered “Wattmessung im Radsport und Triathlon“, the German translation of the book “Training and Racing with a Power Meter” by Hunter Allen and Andrew Coggan.

[amazon_link asins=’1934030554′ template=’ProductAd’ store=’rowingdata-20′ marketplace=’US’ link_id=”]

The book is an interesting read for rowers, because I believe that power measurement systems for rowers are about to make the jump from Olympians (and state coaches) to the general rowing public, which means Masters rowers, and club and college programs. Regarding power measuring, rowing is a funny sport. On the erg, we have had power measurements for decennia, and since the Concept2 PM3 (and RowPro) we’ve had the ability to extract data from our rows and analyze them. On the water, we have nothing. We can measure speed with an impeller or a GPS unit, but data extraction was hard and analysis not really open to the general public. This may change in the near future.

Introduction – why Power measuring is cool

Cycling has been in the “dark” ages for a long time, but since power meter systems have become affordable, many riders use them. I have been reading through cycling and triathlon oriented discussion groups and there are many discussions on the use of power meters for training optimization, post-race analysis and other topics. A nice site to start to read about what’s available for cyclists is DC Rainmaker’s blog about triathlon/cycling tech.

An interesting parallel between cycling and rowing is that there are natural obstacles that make structured training messy. Where on the erg you can dial up your 8x500m and row like a machine, in OTW rowing there is wind, stream, turns, chop, coaching launches wakes and other things that make OTW rowing a bit more adventurous (and harder to quantify). Also, the length of your rowing water may make it difficult to row a straight 20 minute row. In cycling there are traffic lights, wind, climbs, descents, and other obstacles. Also here, it may be hard to execute a maximum effort 20 minute ride on flat terrain (unless you ride in a velodrome, of course).

In road cycling absolute speed doesn’t mean a lot. The introduction of the power meter gave cyclists data on average power, instantaneous power, average pedal force, and cadence. Finally some real data that could be compared from ride to ride. But because of the stochastic nature of the data (which is a fancy way of saying that there is a large random spread in the data), cyclists had to find ways to make the data collected with their power meters meaningful, using statistics. In rowing, these data will become available for those who invest in power measuring devices (like SmartOar, the products offered by Sweetzpot, and NK’s Empower Oarlock) and I think it is really time that rowers start basing their training analysis on power and force data, rather than on “splits”. Another good reason is that on the erg, the concept of “distance” and “split” is an illusion. The real thing that is measured is the force accelerating the flywheel and the power you put into keeping the flywheel spinning.

Therefore, it is very interesting to start looking at what is going on in the cycling world, and Allen and Hunter are a good starting point. With their backgrounds in training and sports science, being authors of many scientific publications, the metrics and plots they propose have a high probability of making sense. These are also the guys behind TrainingPeaks, the number one Triathlon On-line Workout log (which offers training analysis, training plans, and more in the paid version) and their principles are also used in the WKO+ and Golden Cheetah training analysis computer programs. In summary, their principles seem to be successful and widely adopted in the triathlon world.

The book review

The German edition is 388 pages full of text and graphs. It provides all the information a cyclist needs to start using a power meter. In the opening chapters, the authors explain what a cyclist can expect from using a power meter:

  • Know your strengths and weaknesses
  • Ability to share ride data with your trainer or team members
  • Goal oriented training
  • Tuning to optimum performance

It then proceeds to give an overview of what types of power meters are available on the market and lists pros and cons of the different ones, as well as giving an overview of the software available for data analysis (with the longest review dedicated to the author’s own software WKO+ and trainingpeaks.com, while spending only a few words on Golden Cheetah).

I like how the book is set up. You can really read it chapter by chapter and dig deeper and deeper into the matter. In the previous chapters, the reader got all the information needed to decide what gadget to invest in and what software to use for the data analysis. In the next chapter, the authors introduce one of the first metrics that they have developed to characterize yourself as a cyclist. The “FTP” (Functional Threshold Power) is simply the maximum average power that you are able to hold for an hour. It’s a key characteristic, just as rowers talk about their 2k time.

There are several ways to measure FTP. A straightforward way would be to do a maximum effort 60 minute ride (hoping there will be no red traffic lights etc). The authors suggest to do a 20 minute ride, which may be more practical for most cyclists, and then multiply the obtained average power by 0.95. (More on this in the rowing section below). Another interesting way is to load all your rides into training software and let the computer filter out your best segments for different durations. The authors explain the “Critical Power” model that can be fitted to the data, which enables you to predict your 60 minute maximum effort, kind of how rowers use “Paul’s Law” to predict paces for various ranking pieces.

Having found your FTP, the authors explain how to determine your training zones. Every training guru, every sport, and every national team has its own definition of training zones, and the book is no exception. Power cyclists live in a world with 7 zones, which I will not name because I am sure I will translate the German names back to English differently than in the original English text. The authors do explain that the training spectrum is not boxed into zones but a continuum, and provide a nice table with main training effects of the different zones, where you can see that each zones addresses multiple training effects with more or less intensity.

In a subsequent chapter, detailed examples are given of how you can use your maximum average power effort for different exercise duration to do a qualitative analysis of your strengths and weaknesses.

Measuring training “impact” and planning it is done using a TSS (“Training Stress Score”) which is calculated from the power profile. It is not just the average power, but the authors use the average of the fourth power to give more weight to high intensity peaks. The TSS is normalized to your personal FTP, and used to calculate an average training impact over the past 7 and 40 days which then translate into measures for “fitness” and “freshness”, one of the core features of the TrainingPeaks approach. The method is much more detailed than I am writing here, and the authors give all equations that enable you to calculate the values yourself. I have personally been  using a heart rate based approach, using heart rate as a proxy for power. It seems that one of the key “know how” of TrainingPeaks.com is that the site has a consistent way of calculating TSS for cross-training when no power data are available, using heart rate, or running speed, elevation, and your body weight for running. Graphs of “fitness” and “freshness” plotted over time can  be used to analyze race performance in the light of your training preparation and the effectiveness of the taper, and this knowledge can be used by the athlete or coach to create an optimized personal training and taper plan to peak at important races.

Finally there is a ton of specialized graphs that are introduced and explained. Some of those analyses go into how you use your power during a race. Cycling is complicated with escapes and sprints. Rowing is much more about pacing well and sticking to your optimum pace.

A strong point of the book is that the authors find a good balance between introducing the concepts to readers who are less strong in the physics and sports science behind, but at the same time don’t shy away to lay out exactly what they are doing with equations and theory, both in the main text and in special boxes that go a bit deeper into a certain detail. Knowledge sharing as it is supposed to be. The book also has a glossary and list of acronyms that come in handy when you lose track of the jargon. The only thing that is missing is a reference list of publications that provide the scientific background for readers who are into reading the primary sources. A few pages of references at the end of each chapter would have been nice. Less interested readers could just skip those pages.

Quadrant Analysis

A big concept is “Quadrant Analysis”, where a scatter plot of pedal rotation speed (m/s) vs average pedal force is used. The concept of power is “force x velocity”, and so there are different ways to achieve, say, a 300W average power. You can pedal fast at low force, or slow at high force. There are four quadrants:

  • High Force and High Cadence – Sprinting
  • High Force and Low Cadence – Big hills, big gear riding
  • Low Force and Low Cadence – Recovery ride
  • Low Force and High Cadence – Criterium or fast pedaling drills

For cycling, this makes a lot of sense, especially as you can chose your gear during a ride, so it is useful to know what you have done in training, and what works best for you.

Would I recommend the book to rowers? Yes! I think it is very important to keep your eyes open to what people in other sports are doing. Cycling and triathlon have the numbers of athletes that rowing can never achieve, so it is easier to see the trends and (but this is more tricky) to see what works and doesn’t work. Some parts of the book are less relevant, but especially triathletes are strong in pacing strategies, which is extremely relevant for rowing.

Also, it seems that the bike sports are much further in using sports science for individual athletes, not only the top performers. In contrast, I see many rowing programs still using training philosophies that are 20 or 30 years old, especially with Masters rowers (who continue to train like they used to when they were young) and small clubs with amateur coaches (who coach like they were coached back in the days). There is nothing wrong with that, as long as you can defend what you are doing in the light of what is currently known about training.

Power Training in Rowing

How would I see the methods of the book applied in rowing? For one, it would be great if rowers start to talk about the power they can hold for a certain amount of time. I think it is a much cleaner concept than talking about a pace for a certain distance, which mingles the concepts. First, there is only a virtual distance and a virtual pace on the erg, and second, the better you are, the shorter your 2k time. So, for a young girl with a 9 minute 2k,  it is much more an aerobic affair than for the young man with a 6:15 erg score. Instead of comparing 2k times, the athletes should compare power of a 5 minute (or a 10 or 30 minute) interval.

Races will still be over a fixed (virtual) distance, and the fastest (in time) will win. But for comparing rowing abilities, I would say that the time / power based measure is better. On rowsandall.com, I am starting to implement a few tools that make it easier to do this. download-12

In the plot above, for example, the red dots show a few of my ranking pieces rowed in the past 12 months, a 100m, a 500m, 2k, 5k, 6k, 30 min, 10k and half marathon row on the erg. The blue line is Paul’s law fitted to the data, the green line is a Critical Power model similar to what is used in the book. On the site, you can see what the two models predict for all Concept2 ranking pieces, plus a piece of your choice. I know there are many pace predictors out there, but I think this is a nice and graphical one (as long as you have enough data uploaded to the site). As a bonus, the blue dots are taken from shorter segments of my own rows, showing for example, that I have a 100m interval in the middle of my 500m effort which was faster than my 100m piece. I guess you can see the effect of a standing start here, but for the 2-10k pieces this can give interesting insights.

Another thing that I noticed, is that my 20 minute power is not at 105% of the 60 minute power but at 116%. I suspect that the shape of the power/duration curve may be different for  rowing compared to bike riding.

Nonathlon does a nice job of comparing your individual scores to the “gold standard” for your age, using world records and ranking scores collected on the Concept2 Logbook pages, but I am thinking about incorporating a Watts based comparison to the site. Here is an attempt in excel:

agerecords
Comparison of my erg SBs with Gold Standards from Concept2 logbook. I am slightly above “excellent” (90% percentile on C2 ranking) but relatively better at longer rows. In terms of percentile scores on the ranking, average is set at 25%, fair at 50%, good at 75%, excellent at 90% and World Class at 99%.

Here are a few other things that I may implement. I am not fully convinced of the usefulness of each of the plots for analysis, but my philosophy is to allow each and everyone to make any analysis he likes. All plots are taken from a single 4x2km interval erg session (both work and rest intervals), but in principle they could be made for all data accumulated on the site, or comparing two similar workouts. The plots have been inspired by the kind of analysis done in the book. Some of the data are currently only available for users of Painsled, an iOS app in beta.

figure_1-30
Average Drive Force vs Cadence. One can clearly distinguish the work and rest intervals.
figure_1-29
In this plot, the horizontal axis is the handle speed (obtained by dividing drive length by drive duration) and the vertical axis is the average drive force. It is interesting to see that most of the data seem to be close to a “curve”, indicating that both my “rest” and my “work” strokes are of the same nature. One could distinguish “short sliding” from such a plot.
figure_1-25
Close-up of the work intervals (4x2km) in terms of power vs cadence (SPM). I see a big spread and two “groups” of strokes. Will need to go back to my notes about the session to see what is going on.
figure_1-1
A power histogram, again clearly showing the two groups of “work” strokes and the “rest” strokes. I didn’t do too many rest strokes as some of the rest period was spent stretching and drinking water.

 

That’s it for today. More thoughts will follow. I hope to get some feedback in the comments section of this blog post.

By sanderroosendaal • Uncategorized • 15 • Tags: cycling, OTE, OTW, power, power based training, rowing, training

running-9-18-2016-power

Sep 18 2016

Recovery Run – through the woods

The title says it all. It’s a recovery run. I decided to run instead of erg, because the weather was unexpectedly dry (rain was forecasted) and I was really eager to start hitting the trails again.

I slowed down whenever my heart rate was approaching 160 bpm. First, I wanted to do my regular 12 km “benchmark” run, but in the end I decided to take it easy and use the opportunity to take some trails that I normally don’t run on. I made up the loop as I ran it, trying to be around 10km. In the end I ran 11km.

A few of the new trails I followed were actually “roads” for forest workers. The trails were soft, sandy, and at places muddy. Also, there were a lot of cut branches. I tripped only once and landed quite elegantly, in the mud. No damage to muscles or bones, luckily.

run3

run2 run1

SportTracks has a power estimation for running. I am not sure how accurate it is, but here are a few interesting plots from the Training Analysis in SportTracks:

2016-heart-rate-delayed-30-sec-speed

2016-distribution

running-9-18-2016-power

running-9-18-2016-elevation

All power values calculated using the Power Runner plugin for SportTracks.

In another post, I am going to write about using Power data for Rowing.

By sanderroosendaal • Uncategorized • 1 • Tags: power, running, trail

«< 66 67 68 69 70 >»

Calendar

May 2025
M T W T F S S
 1234
567891011
12131415161718
19202122232425
262728293031  
« Jan    

Tags

1x 2x 4x2km 6k 8+ 1000m concept2 crewnerd cross-training cross training crosstraining ctc double eight erg ergometer head race head race prep intervals lactate lake masters mix OTE OTW pete plan quad race race prep racing river rowing running single sprint sprintervals steady state strength taper technique test testing threshold training training plan

↑

© Rowsandall 2025
Powered by WordPress • Themify WordPress Themes
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.Ok