W3C home > Mailing lists > Public > public-device-apis-log@w3.org > February 2017

Re: [sensors] Javascript 120Hz devicemotion events for high end inertial applications

From: Ashod Donikian via GitHub <sysbot+gh@w3.org>
Date: Mon, 20 Feb 2017 20:50:14 +0000
To: public-device-apis-log@w3.org
Message-ID: <issue_comment.created-281178354-1487623813-sysbot+gh@w3.org>
@tobie my response to: 

> The sampling intervals need to be consistent. And it's critical that
 no samples are lost. [Ed: I'd love to understand more about about why
 that's important.]

This is very important, because most applications using inertial 
sensors use incremental estimation where the current state (e.g. 
position, velocity, attitude) is composed of a a set of successive 
relative state estimates. For inertial sensors, this is not just 
dependent on the sensor readings but also having correct timing 
information, since the sensor readings are often integrated. Thus, if 
a sample is lost, it is generally unrecoverable (other than trying to 
compensate with global information such as the magnetometer).

GitHub Notification of comment by adonikian
Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/98#issuecomment-281178354 using 
your GitHub account
Received on Monday, 20 February 2017 20:50:21 UTC

This archive was generated by hypermail 2.4.0 : Monday, 4 July 2022 12:47:53 UTC