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

question: about imu_data.angular_velocity correction. #34

Open
asimay opened this issue Oct 12, 2016 · 1 comment
Open

question: about imu_data.angular_velocity correction. #34

asimay opened this issue Oct 12, 2016 · 1 comment

Comments

@asimay
Copy link

asimay commented Oct 12, 2016

Hi, dear,
sorry for stupid question here, I didn't understand the code at here:

https://github.com/turtlebot/turtlebot_create/blob/indigo/create_node/src/create_node/gyro.py#L82

I cannot understand why we divide /self.cal_offset here to do angular velocity correction, shouldn't we use(gyro_measurement_range-self.cal_offset) to divide by here?

I cannot understand the meaning of the formular's denominator.
Please instruct me. Thank you very much!

@asimay
Copy link
Author

asimay commented Oct 12, 2016

another stupid question:
about raw data without correction, code at here:
https://github.com/turtlebot/turtlebot_create/blob/indigo/create_node/src/create_node/gyro.py#L91
why we use sensor_state.user_analog_input/self.gyro_measurement_range ? what does it mean? shouldn't we mutiply self.gyro_measurement_range here?
Thank you very much for your detail instruction!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant