- From: Tobie Langel via GitHub <sysbot+gh@w3.org>
- Date: Fri, 26 May 2017 13:36:12 +0000
- To: public-device-apis-log@w3.org
So outside of the terminology issue between polling and sampling, which I think is a red herring, I still don't think I agree with your assessment if we use the terminology I outlined above: >>> Android does the same >> Does it really? I thought these referred to the polling period (1/f). > I meant it allows to pass same two things : sampling period (not polling period!!) which is "The rate sensor events are delivered at" i.e. reporting frequency in our terms + reporting latency hint "Maximum time in microseconds that events can be delayed before being reported to the application." Would you agree that: Android's `samplingPeriodUs` ~= to 1,000,000/`samplingFrequency`, and: Android's `maxReportLatencyUs` ~= (1,000,000/`reportingFrequency` - 1,000,000/`samplingFrequency`), given `samplingFrequency` and `reportingFrequency` as described in https://github.com/w3c/sensors/issues/209#issuecomment-304242470, and `reportingFrequency` set to the same value as `samplingFrequency` if unset? -- GitHub Notification of comment by tobie Please view or discuss this issue at https://github.com/w3c/sensors/issues/209#issuecomment-304284155 using your GitHub account
Received on Friday, 26 May 2017 13:36:18 UTC