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

Add ability to move collision objects #59

Merged

Conversation

amalnanavati
Copy link
Contributor

Description

This PR implements the ability to move collision objects, and extends corresponding examples.

Testing

  • Launch the simulated panda arm: ros2 launch panda_moveit_config ex_fake_control.launch.py
  • Add a collision primitive: ros2 run pymoveit2 ex_collision_primitive.py --ros-args -p shape:="sphere" -p position:="[0.5, 0.0, 0.5]" -p dimensions:="[0.04]"
  • Move the motion primitive, verify it moves in RVIZ: ros2 run pymoveit2 ex_collision_primitive.py --ros-args -p action:="move" -p shape:="sphere" -p position:="[0.2, 0.0, 0.2]"
  • Add the default collision mesh: ros2 run pymoveit2 ex_collision_mesh.py --ros-args -p position:="[0.5, 0.0, 0.5]" -p quat_xyzw:="[0.0, 0.0, -0.7071, 0.7071]"
  • Move the collision mesh, verify it moves in RVIZ: ros2 run pymoveit2 ex_collision_mesh.py --ros-args -p action:="move" -p position:="[0.2, 0.0, 0.2]"

Copy link
Owner

@AndrejOrsula AndrejOrsula left a comment

Choose a reason for hiding this comment

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

Looks good! Thank you very much @amalnanavati for your contributions!

@AndrejOrsula AndrejOrsula merged commit 4b73e33 into AndrejOrsula:devel Apr 8, 2024
2 checks passed
@amalnanavati amalnanavati deleted the amaln/move_collision branch April 23, 2024 17:13
AndrejOrsula pushed a commit that referenced this pull request May 10, 2024
* Added a function to move collision objects

* Add examples
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