I realized a couple of days ago that the HRM data coming from the chest belt can be very spiky, in particular when the phone is kept extremely close to the belt.
This is of course not very good, and some smart method for despiking this data is required.
Now, the problem is that, at least in certain cases, there are more spikes than data, and classical filters (e.g., median) fail.
Here's one of such cases, and the blue plot is the data (red) filtered using a median filter.
The green one is instead an experimental despiker i made,which seems to work very well for this particular case. It would be nice, however, to gather real workout spiky data, and see if it would behave as good..
If any meeTrainer user would like to contribute with their spiky data, i would very much appreciate!
Of course you have to wait till 0.2.2 will be available (still under QA), so that you can see the actual data and how spiky it is :)
After quite a while and a lot of work, finally the second release of meeTrainer, v0.2.2, is out and has been pushed to the store. Among the other things, it adds support for sportstracker bluetooth chest belts, charting of workouts time series data, and a better overview of the workouts, with per-months summaries. It also includes tons of bugfixes and improvements, as well as a lot core rework.
I want to take the chance and thank all the people that contributed with ideas, suggestions, bug reports, help, and more. In particular i would like to thank Martin for his help and feedback. It's also thanks to him if meeTrainer now supports sportstracker chest belt, and if it will have a nice UI in the future :) I also want to thank Rune, Gabriel and Suyog for having supported the development and for precious feedback. Finally i also want to thank the guys on #harmattan for all the tips and help, me being a beginner in the field!
So now here a couple of screenshots of the new feats
