You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 18, 2023. It is now read-only.
During testing the ambient noise plugin was recording much more data than the sensor was set to record. This problem persisted even after turning on the enforce all setting.
For example, the sensor was recording what appears to be 60 samples per second for a 30 second window, instead of 1 sample per second for a 30 second second window. The records look almost to be duplicates, except that the _id is different. This did not happen every sampling cycle, but looking at our data averaged over 1 minute intervals, it raised the average sampling rate from 30 records per five minutes for the iOS devices, to as much as 440 samples per every five minutes.
We experienced some variation on the oversampling frequency on all (4 of 4) Android devices during a three week test.
The text was updated successfully, but these errors were encountered:
During testing the ambient noise plugin was recording much more data than the sensor was set to record. This problem persisted even after turning on the enforce all setting.
For example, the sensor was recording what appears to be 60 samples per second for a 30 second window, instead of 1 sample per second for a 30 second second window. The records look almost to be duplicates, except that the _id is different. This did not happen every sampling cycle, but looking at our data averaged over 1 minute intervals, it raised the average sampling rate from 30 records per five minutes for the iOS devices, to as much as 440 samples per every five minutes.
We experienced some variation on the oversampling frequency on all (4 of 4) Android devices during a three week test.
The text was updated successfully, but these errors were encountered: