Apr 11 2016
Tame Session – new mesocycle
No time to go rowing OTW. First day of a new 5 week mesocycle. Maintaining base fitness, continuing with endurance power and then slowly gearing up for the 1000m sprint race season.
For the non-rowers: What we call sprint is a 4 minute effort.
Anyway, today I eased into the first week of the new cycle. A light endurance session of about 60 minutes. Decided to row it as 5×12 minutes and use the “Wolverine Plan” rate ladders to keep me busy.
I love Painsled. Nice export of stroke data to CSV files. I was curious to see what the rate ladders would do with my stroke length, average force, drive time and recovery time. It turned out to be no surprise. The recovery time is varied, all other parameters staying roughly the same.
Workout Summary - sled_2016-04-11T19-28-49ZGMT+2.strokes.csv
--|Total|-Total-|--Avg--|Avg-|-Avg-|-Max-|-Avg
--|Dist-|-Time--|-Pace--|SPM-|-HR--|-HR--|-DPS
--|14428|62:12.0|02:09.4|20.2|141.8|157.0|11.5
Workout Details
#-|SDist|-Split-|-SPace-|SPM-|AvgHR|MaxHR|DPS-
00|02861|12:03.3|02:06.4|19.9|134.1|147.0|11.9
04|02876|12:07.0|02:06.4|20.0|138.7|148.0|11.9
08|02869|12:07.1|02:06.7|20.0|142.9|153.0|11.8
12|02890|12:07.3|02:05.8|20.4|146.9|157.0|11.7
16|02914|12:07.7|02:04.9|20.8|146.4|155.0|11.5
Apr 12 2016
OTW Steady State
Mirror flat water this morning. I copied the workout from yesterday, but for time reasons I had to skip the final 12 minute interval.
A little problem with the XGPS160. I have noticed that it works perfectly if you switch it on while CrewNerd is already running. My natural behaviour is to attach the XGPS160 to the boat and switch it on while still on the dock. I only switch on CrewNerd when I am already sitting in the boat and on the water. I need to remember to do it in the right order. This led to noisy data and suspicious pace values in the first two intervals (especially in the second one, which apparently I had rowed in 1:56 average pace.
I also suspect that the system doesn’t work well when other apps using GPS position are running in the background (like Waze, in this case).
Workout Summary - 2016-04-12-0726.CSV
--|Total|-Total-|--Avg--|Avg-|-Avg-|-Max-|-Avg
--|Dist-|-Time--|-Pace--|SPM-|-HR--|-HR--|-DPS
--|13271|59:52.0|02:16.7|19.1|148.2|157.2|11.5
Workout Details
#-|SDist|-Split-|-SPace-|SPM-|AvgHR|MaxHR|DPS-
01|01345| 05:55 |02:11.6|17.8|125.0|139.0|12.8 | warming up
02|02721| 12:00 |02:12.3|18.9|149.0|160.0|12.0 | interval 1
03|03089| 12:00 |01:56.4|19.7|156.0|166.0|13.1 | suspicious
04|02502| 12:00 |02:23.9|20.3|160.0|167.0|10.3 | interval 3
05|02513| 12:00 |02:23.2|20.1|159.0|166.0|10.4 | interval 4
06|01101| 05:57 |02:41.9|17.8|140.0|145.0|10.4 | cooling down
Here is a map of the row from Strava, from the CrewNerd app:
You can see the straight line for the third and fourth intervals, after I had reset the XGPS160, and the wobbly line from the first and second intervals, before the reset.
Here is the same segment as recorded by the Garmin Forerunner:
The colorful plots:
By sanderroosendaal • Uncategorized • 3 • Tags: lake, OTW, rowing, single, steady state, training