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

Bugfix/localization - Segway Twist #11

Merged
merged 3 commits into from
Aug 12, 2015

Conversation

ClintLiddick
Copy link
Member

Launch robot_localization using Segway's twist data only, not pose. Resolves #7

@mkoval
Copy link
Member

mkoval commented Aug 12, 2015

N.B. This depends on personalrobotics/segway_rmp#1.

false, false, false, # x, y, z
false, false, false, # roll, pitch, yaw
true, true, false, # x dot, y dot, z dot
false, false, true, # roll dot, pitch dot, yaw dot
false, false, false # x ddot, y ddot, z ddot
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix the alignment on these comments.

@mkoval
Copy link
Member

mkoval commented Aug 12, 2015

👍 LGTM besides those two formatting nitpicks.

🎊 🎉 🎊 We finally have a configuration that both makes sense and works!

@ClintLiddick
Copy link
Member Author

Formatted.

@mkoval
Copy link
Member

mkoval commented Aug 12, 2015

Looks good to me. Thanks @ClintLiddick!

Note that we'll have to build segway_rmp from our fork until this gets merged into upstream and the Debian packages are re-built. Here is the pull request I made againsegway_rmp: segwayrmp/segway_rmp#28.

mkoval added a commit that referenced this pull request Aug 12, 2015
Changed robot_localization to use twists from segway_rmp.
@mkoval mkoval merged commit d3aa911 into personalrobotics:master Aug 12, 2015
@ClintLiddick ClintLiddick deleted the bugfix/localization branch August 13, 2015 13:12
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

Successfully merging this pull request may close these issues.

2 participants