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

Unify BehaviorRobot into floating-base robot paradigm (e.g. Tiago), perhaps through common base class #883

Open
cgokmen opened this issue Sep 14, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@cgokmen
Copy link
Contributor

cgokmen commented Sep 14, 2024

The BehaviorRobot behaves differently from the Tiago robot: Tiago keeps the real base link at the origin, but the BehaviorRobot moves it. We should unify. We should also get rid of the BRPart system as much as possible.

@cgokmen cgokmen added the bug Something isn't working label Sep 14, 2024
@ChengshuLi
Copy link
Member

ChengshuLi commented Sep 16, 2024

The command / control limits of the 6 DoF torso / arm / head joints are also wrong - the 3 DoF orientation should have range [-2 pi, 2 pi] rather than [-1000, 1000]. Currently robot_control_example.py is broken for BehaviorRobot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants