Assume line 1 - is original code / filter.
As this is actual walking data - I would not expect the state machine to have to do much work or show much difference for that dataset. When I collected this data I tend to walk fairly quickly the 1 mile walk or so. I think there will be big difference when you run against the non walking recordings.
1) driving log 0 steps in 36 minutes
2) driving log 0 steps in 29 minutes
Its the driving that is the weakest part now. I suspect tweaking things to get these to 0 will massively reduce the accuracy of when counting actual steps.
Here are the things I think can be tweaked.
1) X steps in X seconds could be 5 or 6 or 7 - after 7 I think it starts to work against accuracy
2) The Raw threshold to gate the output of the filter, Currently +-10. Can go higher.
3) The time we want the raw signal to be over or under threshold before we open / close the gate.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Assume line 1 - is original code / filter.
As this is actual walking data - I would not expect the state machine to have to do much work or show much difference for that dataset. When I collected this data I tend to walk fairly quickly the 1 mile walk or so. I think there will be big difference when you run against the non walking recordings.
1) driving log 0 steps in 36 minutes
2) driving log 0 steps in 29 minutes
Its the driving that is the weakest part now. I suspect tweaking things to get these to 0 will massively reduce the accuracy of when counting actual steps.
Here are the things I think can be tweaked.
1) X steps in X seconds could be 5 or 6 or 7 - after 7 I think it starts to work against accuracy
2) The Raw threshold to gate the output of the filter, Currently +-10. Can go higher.
3) The time we want the raw signal to be over or under threshold before we open / close the gate.
2 Attachments