You are reading a single comment by @jeansnorth and its replies. Click here to read the full conversation.
  • I have already started considering (at least) a different approach to this. There do exist libraries which take in only accelerometer data from a device fixed to the lower back and use some more advanced statistics to gauge speed and other things from there. What I really want is the speed. Cadence and foot contact time are also on the wishlist, and it seems that the statisticians can manage these.

    One more thing on that subject. I do use a Polar H10 when running, and, as has been mentioned on these forums, it has a hidden accelerometer. If there are good open source algorithms which take data from the chest as input, then we can actually forget the puck :D (I'm not saying I wouldn't miss it) As far as I know, a Garmin chest strap basically does this, with the caveat that it only works if you're using a Garmin watch. Most likely they run the algorithms on the watch, rather than on the strap. I suppose that a modern Garmin watch has more computational power than a Bangle.js 2? What are the specs on Bangle.js 3? ;)

    What I described above is an idea I had brewing for a bit until I had some time to code. Maybe it is a bit simplistic, but if it can be made work, then that would be fantastic, I won't give up on it just yet.

About

Avatar for jeansnorth @jeansnorth started