I found out, that there is a bug in the value " Avg. Watt". After a training it should display the avg. watts for the training like avg Speed or Calories. But it shows the actual value, so there is no average value. Maybe this could be fixed sometime.
Admin said: 'Well the power calculation is 100% based upon the calorie calculation (it's actually the same, only different units).'
How is that? For example, according to Run.gps, for my ride on Dec 1st I used a total of 1341 KCal (My Polar HR monitor said 1372 Kcal, so very accurate), or 771 KCal/hr (I was celebrating a whole 36 hours of no rain in UK by going quite hard ;), but Run.gps returned a Avg Power of 897 W. That does not look the same to me? Not only is not the same, its just totally wrong. I have never used a power meter on my bicycle (but will soon purchase a indoor trainer with power meter), but I think for my standard of riding/age a avg figure of more like 250 W is more appropriate?
Well the power calculation is 100% based upon the calorie calculation (it's actually the same, only different units).
For the calorie calculation there are 2 options:
- not using a HRM: really difficult to estimate, very dependent on many body parameters (the formula in Run.GPS uses: body parameters, ascent, speed, duration and is different for all pre-configured sports)
- using a HRM: calculation using empirical formula based on heart rate and body parameters
I can't remember if I posted this before- the search facility on this forum wont find all my previous posts.
The current and average power (watts) calculations while cycling/race-biking are just so wrong they are worthless. I'd love to be able to produce an average of 700W for 2 hours, but its just not going to happen! Can we get a more realistic algorithm please. Even going up a steady slope (less wind resistance, friction etc) on a known route (gradient), the current and average power outputs are totally wrong.
Start by user-inputing body AND bicycle weight, and tyres (simple race [thin] vs mtb [fat] would do).