I’ve pushed a few new builds, tweaking the algo until I’m more or less happy with it.
Outstanding items:
Speed and cadence sensors have approx. 3-second latency. If you add another 2-3 seconds on top, that increases the latency between you starting a climb, and the power displaying. No problem for later analysis.
Given that it is an estimate, using 3-second power might not be that useful - maybe make 5- or 10-second averages the default.
Occasional crashes trying to load the app on my watch with “maximum number of Suuntoplus apps reached”, which seem completely independent of what the app does. Restarting the watch always fixes it. Waiting a while also does, but not sure how long - 5 minutes to 2 hours from what I’ve seen.
Once I trust it enough, retrieve the rider’s weight from the watch settings once again as it used to - but I suspected that of causing the error mentioned above.
Grade calculation is a pain - the altimeter only knows 20 cm increments. On say, 8 metres, that’s 2.5% grade over 1-2 seconds riding reasonably fast - this will cause false and/or jumpy readings at any speeds below 35 kph. I’m curious to see how Suunto’s running power or NGP take grade into account.