gvcormac wrote: ↑May 31st, 2022, 7:45 am
I'd be very interested to learn more about the history of C2
see
https://www.youtube.com/watch?v=sFkfcxZS58w, I really love their down to earth approach.
gvcormac wrote: ↑May 31st, 2022, 7:45 am
I have read the original C2 patent and I think it is quite clever. I don't agree that it makes wild assumptions in calculating power to the flywheel. It needs to know the angular moment and velocity of the flywheel, which are, respectively, constant and measured quite readily. It then needs to numerically calculate the derivative (acceleration) and an integral (power to energy).
As the paper you mentioned notes, if the acceleration is very jerky, these numerical calculations can be off a bit, but only by a couple of percent.
Good idea, I picked up these old patents, they nicely describe how we do things as well. I never saw them, but they are a work of beauty. I think that Prof. van Holst and Anu Dudhia deserve all the credits: they have written down the real physics and are the basis for every open source rowing monitor out there (see
http://eodg.atm.ox.ac.uk/user/dudhia/ro ... meter.html).
We indeed initially started with a numerical approximation as the formula's of Anu Dudhia suggest that. When it comes down to implementation, you see that time between impulses is indeed a bit noisy. This makes Angular Velocity a bit more noisy and Angular Acceleration even much more noisy. So I implemented a different engine based on linear regression to calculate the slopes, which delivers much more stable results and is more robust to noise and outliers.
The essence of the patent describes the backbone of a stable calculation quite well: you calculate the drag in the recovery phase, and then use that to convert angular displacement into linear displacement, with the Peter's magic number 2.8 and the drag between them. As the patent suggests, From there on, all displayed metrics can be calculated from linear displacement. This delivers quite stable results, and that is why the new version of Open Rowing Minotr is within 0.03% of C2's results.
C2's approach makes some critical shortcuts, the most important being that they don't take in account the angular velocity changes across strokes. Both our validation and the research of the university of Ulm confirm this (see
https://www.researchgate.net/publicatio ... d_Test_Rig). Their conclusion is that when the rower isn't using a real steady state row, the power metrics are off considerably. I understand why they took the shortcut (the alternative is a more accurate but much more vulnerable to small errors), we made the same shortcuts, but that is the typicall trade-off you have to make when you have limited resources and still want to display things real-time.
gvcormac wrote: ↑May 31st, 2022, 7:45 am
They do report Calories which is another measure of work but -- correct me if I'm wrong -- this is not calories at the flywheel (1 cal = 4.18 joule) but some wild-assed estimate of metabolic calories.
It is one of the many shortcuts you need to make to get to some meaningful number. From the description of Anu Dudhia according to a named source within Concept2:
The 300 kC/hour has always been our best approximation for keeping alive and awake and going through the rowing motion at a reasonable stroke rate on an erg with the flywheel removed. This was arrived at from internal experiments and observations, data from Fritz Hagerman and studies done at Ball State.
It isn't a wild assumption per se, but it is an population average applied to a single individual. So by definition, it won't fit anyone well. Here a couple of additional parameters (rower weight, SPM, etc.) might make it a better model, but this simplicity makes the calculation robust and simple. And as long as nobody makes life or death decission based on these metrics, why should one care.
And that is the fundamental issue with most models: when you find out that 2 metrics account for 95% of your outcome, it makes sense to remove all other metrics. This is fine when the remaining 5% at best is dissapointed, but for some applications you can't take that risk (like the applications Frank proposed here).