# Stroke Profile Continued

I have been trying to find some artificial stroke profiles that come close to simulate my measured acceleration on a 30 spm stroke (measured with Rowing in Motion). Then I did 4 quite coarse variations to that stroke profile and ran a simulation for 25 to 35 spm using those profiles. Here are the stroke profiles I used:

The stroke profiles used in the simulation

Simulating the power-velocity graphs for these strokes gives the following result:

Average Boat Speed vs Average Power Consumption

So T3 is better than T2, T4 and T5 which are roughly equal, and all are better than T1. Again, we have to remember that these values depend on the catch angle and I need to rerun the simulation for a different catch angle, which I took at 63 degrees for this simulation.

Here is what CrewNerd check would give:

Crewnerd Check numbers

The actual check values in CrewNerd would be different, but I am using the equivalent formula, just scaled, that CrewNerd is using. Lower check is better, so we have roughly two situations:

1. At lower stroke rates, T3, T4 and T5 are “best”, T2 is in the middle and “T1” is the worst
2. At higher stroke rates T3 is the best, followed by T2, T4, T5 and T1

In conclusion, for this setting, CrewNerd Check factor would give the right feedback. If you would be able to reduce check at constant speed, you are probably moving to a more economic stroke profile.

The RIM Check metric has a similar name but is calculated differently:

RIM check vs average boat speed

So here, roughly, T2 is the best, followed by T3, then T1 and finally T4 and T5. Something weird is going on with T1. Looking at the stroke velocity plot at 30spm, it is clear:

Speed vs time for one stroke with T1 profile

I guess the simulation is not entirely realistic here around the catch (between 0 and 0.15 seconds in the graph). Such a profile is not realistic in a real boat.

Finally, I will look at RIM “stroke efficiency”:

RIM Stroke Efficiency vs Speed

Here, a higher value is better. So we have T1>T5>T4=T2>T3. This looks like the exact opposite of what we should get. This parameter depends a lot on the value of the minimum velocity. For the stroke profiles I have chosen that minimum velocity is determined really by the force around and immediately after the catch. By “checking” the boat (meaning pushing hard on the footstretcher around the catch) we are making this a low value, which helps the parameter, which is a double integral of boat acceleration, so quite sensitive to calibration accuracies in the RIM app.

So it seems it will be better to look at RIM Check or CrewNerd check for live technique feedback in the boat.

Next, I am going to rerun the simulations looking at catch angle.