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

Overlapping move-groups don't share state #2717

Closed
dsandber opened this issue Feb 28, 2024 · 1 comment
Closed

Overlapping move-groups don't share state #2717

dsandber opened this issue Feb 28, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@dsandber
Copy link

Because of this issue:

moveit/moveit#3161

I have multiple move-groups.

MoveGroup #1 contains joints A and B.

MoveGroup #2 contains joint A.

Querying RobotState through MoveGroup #1 will give different positions than querying RobotState through MoveGroup #2, depending on which move-group the last move was done through,

There should be some kind of shared state for joint positions, so that the joint position is reported accurately no matter which joint group it is queried through.

Your environment

  • ROS Distro: Iron
@dsandber dsandber added the enhancement New feature or request label Feb 28, 2024
@dsandber
Copy link
Author

dsandber commented Mar 4, 2024

This ticket was based on my misunderstanding of RobotState -- I didn't realize you need to retrieve the state from the planning scene for it to be accurate.

@dsandber dsandber closed this as completed Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant