Currently, we're detecting tremors at a much higher rate than intended. The root cause seems to be because we're looking at accelerometer values as "points in time" rather than a true window of activity. Refactor the code to accommodate this behavior.
gavination
commented
2 years ago
Currently, we're detecting tremors at a much higher rate than intended. The root cause seems to be because we're looking at accelerometer values as "points in time" rather than a true window of activity. Refactor the code to accommodate this behavior.