Followup on the Open Stack discussion at QS18 - Has anyone conducted a survey in the community about preferred sampling rate for different outputs?
« High Frequency Sampling » is something we talk about a lot, but it means different things to different people depending on the project or output being measured…
Obviously for building new equipment the ideal is to let the user define the sampling rate, but I’m curious what thoughts are in the community…
I think that to get meaningful answers you’d have to ask a question like: best sampling rate for [x]. Even then you’d still get some throat clearing like “it depends on the question.” That’s obviously true. But there is some good expertise out there about sampling different inputs, especially tricky ones like location, where battery life and geographical precision are anticorrelated.
Can’t resist one more comment on sampling rate controversies, which came up in our sleep tracking breakout. There’s an interest in/emphasis on getting higher resolution sleep data, increasing sampling and analytical capacity so that sleep stages can be reliably detected. But there’s also a history of QS projects where sleep quality is analyzed with a daily evaluation in the morning, sampling rate of once per night. Just an interesting example at far ends of the continuum.