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:
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:
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.
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.
Total distance: 17.3km. I was on the water for 90 minutes, including a few drinking breaks.
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:
So I set out to do a long (5.2km) warming up to get to the start line at the Veveří castle.
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.
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”:
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.
By sanderroosendaal • Uncategorized • 1 • Tags: 6k, lake, OTW, river, rowing, test, training