Apr 20 2015
First OTW 8×500 – Are my hard days too easy?
Time for the first 8x500m training of this season. I spent some time on Sunday to prepare the training plan between now and the next race, which will be a 1000m sprint on May 30. Time to get accustomed to the high stroke rates. My training being based on the Pete Plan, from now on I will push for short intervals rather than long intervals. I want to replace the “hard distance” with 1km or 2km efforts with long warming up and cooling down steady state.
I did the last OTW 8x500m a year ago, on 18 April 2014, achieving roughly 2:00 pace on average, roughly 28spm, in light wind (0.8m/s average). The temperature was 16 degrees C.
In June 2014, I did a 10x500m/500m rest which looked roughly like this:
That really looks painful1.
Today’s session had to be early in the morning, because there is stronger wind predicted for the afternoon. So I pushed off at 6:18 which is early for me.
The weather was slightly different than a year ago. Average temperature during the session 3 degrees C, and a wind speed of 1.1 m/s. So colder and slightly stronger wind. My year old report doesn’t say anything about waves. Today there were some, and there was some varying wind. Rowing from Rokle (northwest corner of lake) to Sirka (south) I had both tailwind and headwind conditions.
Here are the data:
|Dist_|Time_|Pace__|_SPM__|avg HR|max HR|DPS|Remarks
|02059|12:37|03:03.8| 19.0 | 132 | 145 |08.6|Warming up
|00499|01:58|01:58.3| 28.3 | 159 | 168 |09.0|#1; tailwind
|00500|02:00|01:59.9| 28.6 | 163 | 172 |08.8|#2; tailwind
|00498|02:06|02:06.5| 29.5 | 165 | 174 |08.0|#3; varying wind
|00501|02:03|02:02.8| 28.9 | 166 | 175 |08.5|#4; varying wind
|00500|02:16|02:15.9| 26.9 | 165 | 174 |08.2|#5; headwind
|00501|02:10|02:09.8| 28.2 | 171 | 176 |08.2|#6; headwind
|00500|01:57|01:57.0| 31.0 | 171 | 179 |08.3|#7; tailwind
|00499|01:59|01:59.2| 30.8 | 171 | 178 |08.2|#8; tailwind
|01006|06:52|03:24.8| 18.3 | 139 | 178 |08.0|cooling down
And the overall summary:
dist_____|time_____|_pace___|_HR__|_SPM__|_DPS|comment
2059_____|_12:37____|_3:03.8|132|19.0|8.6|warmup
3998_____|_16:29____|_2:03.7|166|29.0|8.4|Main set
1006_____|_06:52____|_3:24.8|139|18.3|8.0|Cool down
3532_____|_20:58____|_2:58.1|149|19.0|8.9|rest meters
10595____|_56:56____|_2:41.2|149|21.1|8.8|_Total
Hm, so I am a bit slower at a bit higher pace, but at lower HR. Should I be worried that my hard days are too easy? Whatever the answer to that question is, this a good marker for the season, although I am wondering if I should keep the 8x500m / 3:00 rest format or switch to the 10x500m/500m format. I want to see the red next time1.
I can also happily report that I made some additional changes to my CrewNerd TCX spreadsheet and above summaries are now almost produced automatically. XGPS160 and CrewNerd were well behaved today. I did “swipe up” to completely switch off CrewNerd before the row, as Greg suggested.
Apr 21 2015
Steady State: Are my easy days too hard?
Yes! They are hard. Because working on technique is hard. But I don’t think they are too hard.
Another morning row because of the wind forecasts. It is actually quite beautiful to be out in the morning:
Sunrise and all:
The problem is that when I drive to work from the lake at 7:45 I hit the main traffic jams which I so elegantly avoid with my usual route and departure time. That’s really frustrating. You know there is work waiting for you, but you can’t do anything else than wait in traffic.
I did a 10km row but the graph below shows only the last 8km. I was using the Rowing in Motion (RIM) app and I have trouble with the calibration. I push off the dock, put my feet in the shoes, and start up the app, then wait a few seconds, then start rowing. When I see “catch efficiency” around 0.5 and lower, I know the calibration is off. I need to be above 1.5, ideally 2 and higher.
I also have the feeling this is limiting the comparison between rows. For example here is a picture with three strokes,
The yellow stroke is from today with tailwind, while the purple one is from November. Stroke efficiency was 2.2 today at 18spm, which was pretty much the maximum I saw during the row, but in November I seemed to be able to hit 2.96. Or was it a different calibration? A slight offset in the acceleration may have been the problem.
Perhaps the boat should not be moving when you switch on the app, as I guess it can measure acceleration but not velocity for the calibration?
Nevertheless, I feel the “stroke efficiency” is a good metric to monitor during one row. I saw it going up when I was focusing on my flaws:
I need to exaggerate to get (2) and (3) right. I am sure an observer on the bank wouldn’t see what I call “shoulder swing” but it feels pretty dramatic. Also, the tap-down probably is just rather sloppy when I don’t pay attention.
So today I was just alternating 18, 20 and 22spm in roughly two minute intervals, trying work on those three points mentioned above while keeping an eye on the RIM metrics every 5th stroke. This is hard work but when it works I am rewarded with splits that are 1 or 2 seconds faster, and the check factor numbers moved to values greater than 2. Sloppy rowing is between 1 and 1.5. I am guessing on the split numbers, because it is hard to judge what is due to good rowing and what is due to changing wind conditions.
Anyway, here are the pretty graphs. Slightly more noisy pace values as I didn’t use the XGPS160. It’s not compatible with RIM yet:
By sanderroosendaal • Uncategorized • 0 • Tags: lake, OTW, RIM, rowing, rowing data, rowinginmotion, single, steady state