Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document why accelerometer values need to be negated #4

Open
dylanmckay opened this issue Mar 13, 2018 · 2 comments
Open

Document why accelerometer values need to be negated #4

dylanmckay opened this issue Mar 13, 2018 · 2 comments
Labels
information-needed We need to find out more information to document it

Comments

@dylanmckay
Copy link
Owner

No description provided.

@dylanmckay dylanmckay added the information-needed We need to find out more information to document it label Mar 13, 2018
@m-7761
Copy link

m-7761 commented Jun 22, 2018

They don't. The only interesting thing, is the X & Y components of the gyroscope are swapped, according to orthodoxy. The Madgwick algorithm available online uses the same convention, so it may not be unorthodox in the field, but it is for 3D video games, where X is normally for rotation about the X axis (pitch) and Y is about the Y axis (Yaw.)

@m-7761
Copy link

m-7761 commented Jun 22, 2018

ACTUALLY there is one reason to negate things... which is (I believe) constructing a quaternion, etc. without negating the values, yields something like an inverse matrix. I don't know if that is by design or not. Of course, an inverse matrix is a "model view" matrix. To get a picture of headset's movements (the object matrix) you invert it. To get what the eyes are meant to see (the view matrix) you leave it alone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
information-needed We need to find out more information to document it
Projects
None yet
Development

No branches or pull requests

2 participants