Today’s rowing was 3,021 meters. Heart rate sputtered a bit and tried to get irregular but eventually gave up that tendency at about halfway through the distance and then stayed smooth and regular for the remainder.
Today’s indoor rowing goal was derived by referring to the time and distance rowed yesterday by one of my training partners. She rowed for a little over 20 minutes, so I converted her total session time to seconds and divided those by the average pace in time per 500 meters of my most recent session. Then I multiplied the resulting number by 500 meters which resulted in a distance of 4,593 meters. That was a bit less than I’d like to row today. I wanted to row at least 5K, so I added her total distance rowed during her 20 minute+ session to 4,593 meters and that resulted in 6,687 meters, which was today’s preset distance.
Today’s session was a bit shorter than yesterday’s but it was a lot more fun because heart rate returned to normal, all of its systems were “Go” and behaved A-OK, to borrow a little astronaut lingo.
The above YouTube video is placed at the top of this page simply because of it’s title, “All Systems Go”. This rowing session was NOT a 200,000 Watt effort like what Donna Summers claims her systems are capable of. 🙂
Today’s indoor rowing session was 1,278 seconds, to approximately match the time one of my training partners rowed yesterday. She rowed 1,278.4 seconds and I was going to round it up to 1,279 but that number is a prime, which cannot be subdivided into any number of equal splits.
So, I rounded the time down to the nearest second and divided 1,278 seconds into 18 splits.
Today’s indoor rowing session was interrupted once, briefly but otherwise it was a relatively constant effort session. The last part tapered off as a sort of warm down.
Today’s indoor rowing session was chosen to be equal in time to that of one of my training partner’s whose time yesterday was 31:40.
To decide on how many splits to have RowPro make of today’s session, I found the factors of the total time in seconds, which was 1,900 seconds. The number 1,900 is divisible by 19, so the session was divided into 19 splits.
While looking at the information available related to the number 1,900 I noticed that it is classified as a “happy number”. The story or stories behind the choice of that name for the particular properties of that number must be an interesting one, but I haven’t found it yet. Happy numbers are the subject of their own little happy field of mathematics. You can look it up, if you want to learn more about it and I will stop talking about it with the period after this sentence.
RowPro 5 for the Mac behaved happily and displayed none of its programming bugs during this session.
Today’s indoor rowing session was a set time of 37 minutes and 52 seconds. That’s because one of my “training partners” had rowed earlier, in the “just row” mode and because her session lasted 37:52.4 I thought I would use that as today’s goal, to match that time and do a fraction of a second more, making it 37:53 for my session.
Heart rate tried to be irregular during the first 1/3 of the time but then smoothed out for the remainder.
But when I calculated the number of seconds in 37 minutes 53 seconds, it came out to be 2,273 seconds. That was a problem, because I wanted a total time, in seconds, which could be divided by some integer greater than 1 and less than or equal to 30, which is the possible range for the number of splits that RowPro can make for a rowing session. I wanted to make each split the same as each of the other splits because otherwise RowPro 5 for the Mac always has some calculation errors with the last, unequal “remainder” split.
2,273 is a Prime Number, so it is not divisible by any integer greater than 1.
So, instead of rounding the time up to 37:53, I rounded it down to 37:52, which amounted to 2,272 seconds, which is divisible by several integers in the range from 2 to 30.
Nonetheless, RowPro managed to activate a different glitch and do some miscalculating for one of the splits anyway, the sixth split. I thought that the 6th split was the most appropriate split in which RowPro would manifest a programming error… Not that it matters in the grand scheme of things, but RowPro didn’t even record the correct amount of time for the 6th split. The erroneous numbers in the record of the 6th split are in the columns for Time, Meters and Avg DPS.
The main “bottom line” numbers, the grand totals, are correct and match what the PM-3 recorded on the rowing machine.
Today’s indoor rowing session was preset to a time of 45 minutes 36 seconds, so I could catch up to equal the time spent rowing this week by one of my “training partners”.
Today’s indoor rowing was the first in several days. I looked at my training partners and the most active training partner had rowed 8591 meters since the last day that I’d done any rowing.
So, I setup a RowPro session for that distance and that’s why the odd number was chosen.
Today’s indoor rowing session was a total of 10K but it was done as two 5Ks. The first 5K was done with a target pace of 2:25 and the second with a target pace of 2:20.