-
Notifications
You must be signed in to change notification settings - Fork 170
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
ROS 2 Branch #133
Comments
Sure. I have created a rolling-devel branch.
The Panda has a very specific URDF with its coarse collision geometries. This is not handled nicely by MSA's automated collision checking (essentially the coarse models always collide). Please inherit from the noetic-devel configuration and only apply required changes for ROS2. |
Thanks @rhaschke.
Will do. |
I've started in #136 |
Hi @rhaschke,
Would a pull request for ROS 2 configuration files be welcomed?
I also wished to ask, how are you deciding on what links to enable collisions for? I have been using MSA to generate a self-collision matrix, despite this I have encountered some collisions while planning. I suspect this is due to the coarse collision geometries specified in the urdf of my robot (inherited from the default description files provided by Franka Emika).
The text was updated successfully, but these errors were encountered: