Running Power Estimator
· v3.4
About
A running power estimator using pace and gradient based on Manetti et. al. (https://www.ncbi.nlm.nih.gov/pubmed/12183501). The running power is saved to FIT. Note that GPS-calculated elevation may have major distortion and affecting Run Power results. The vertical oscillation is not considers like with the Stryd sensor, only the horizontal power.
Example: Running 95 minutes and burning 1400cal. 1400 * 4184 / (90 * 60) gives an average of 1084.7 Watt .
Settings:
In general: keep the defaults if you are not familiar with setting topic
Efficiency: Setting to 20-24% gives you approximately similar power out as for cycling, where as 100% is the energy you burn during running.
Averaging time interval of pace [s]: The time interval of paces to be averaged. Shorter time will give more updates, but with a greater chance of variation.
Distance frequency [m]: The distance for the grade to be calculated. Shorter distances will give more updates, but with a greater chance of variation.
Review:
https://www.prorun.nl/runtech/vermogensmeters/hardloopvermogensmeters-13-running-power-estimator-iq-app/
What's new
V 3.3.2
Add new supported watches
Upgrade to SDK 3.2.5
V 3.3.0
Upgrade to SDK 3.2.3
V 3.2.4.
Upgrade to SDK 3.2.2. Added newest watches.
V 3.2.3
Upgrade to SDK 3.1.7. Added newest watches.
V 3.2.0
Upgrade to SDK 3.0. Different float parsing for user settings.
V 3.0.0
Upgrade to SDK 2.4.4
V 2.2.0:
Upgrade to SDK 2.4.2
V 2.1.0:
Unique labels for chart and FIT entries
Fixed issue of gradient calculation
V 2.0.7:
Zero gradient at start until elapsed time greater than averaging time
Upgrade to SDK 2.4.1
V 2.0.5:
Most recent SDK 2.3.4. Should support also VivoActive3 et. al.
V 2.0:
Update for new watches. Added max power for summary and average and max for each lap to FIT file.
V 1.4:
Averaging damping factor of gradients
V 1.3:
Added running efficiency input; to adjust to corresponding cycling Watt's.
Added average running power to FIT.
V 1.2:
Use averaging of gradient and record to FIT. Using timer not elapsed time.