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:
Blades not too deep at the catch, gentle leg push, not biting off more of the stroke than I can swallow
Strong middle and second half of stroke by “shoulder swing”
Clean, distinct, hard tap-down
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:
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
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:
Follow me in social mediaShare this:
Like this:
By sanderroosendaal • Uncategorized • 0 • Tags: lake, OTW, RIM, rowing, rowing data, rowinginmotion, single, steady state