-
Notifications
You must be signed in to change notification settings - Fork 113
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
Rsdk-2806: Movement sensor distance to meters #2275
Conversation
Warning your change may break code samples. If your change modifies any of the following functions please contact @viamrobotics/fleet-management. Thanks!
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh! I had expected to need to change more units, but the only things that actually return their accuracy return hDOP
and vDOP
, which are the horizontal and vertical dilution of precision in GPS systems, and thus have nothing to do with millimeters after all! I'm surprised that this has been misnamed the whole time. 😳
Fix the 2 comments, and the rest LGTM!
@@ -277,7 +277,7 @@ func toLinearAcceleration(data []byte) r3.Vector { | |||
z := int(rutils.Int16FromBytesBE(data[4:6])) | |||
|
|||
// The scale is +/- 2G's, but our units should be mm/sec/sec. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change this comment to match
@@ -479,7 +479,7 @@ func toLinearAcceleration(data []byte) r3.Vector { | |||
z := int(rutils.Int16FromBytesLE(data[4:6])) | |||
|
|||
// The default scale is +/- 2G's, but our units should be mm/sec/sec. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change this comment, too.
3c67c39
to
0d9ca03
Compare
|
No description provided.