-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: integrate collision detection feature into robot model #163
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read and understood the Contributor License Agreement and hereby sign it |
recheck |
1 similar comment
recheck |
Co-authored-by: Dominic Reber <71256590+domire8@users.noreply.github.com>
…nology/control-libraries into feat/collision-detection-robot
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks better, would like to leave that here for more reviews
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hold on a sec, how do we use these new constructors now?
The existing one is unchanged, clear to me. The new one has an std::optional function, so what if you want to load the collision but you already know that the URDF has correct absolute paths? Do you do provide a nullptr
to the constructor?
Co-authored-by: Enrico Eberhard <32450951+eeberhard@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost good to go, thanks for the patience here!
Co-authored-by: Dominic Reber <71256590+domire8@users.noreply.github.com>
Co-authored-by: Dominic Reber <71256590+domire8@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great piece of work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to set version 7.3.10 manually now
./update_version --version 7.3.10 --commit
Co-authored-by: Dominic Reber <71256590+domire8@users.noreply.github.com>
This still |
done! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing work and thanks for the patience!
Description
This PR solves the issue by implementing 3 new attributes to the
robot::Model
class, namelycheck_collision
andget_number_of_collision_pairs
andis_geometry_model_initialized
. These new attributes along with the default new parameter in the constructor allows for self-collision checking based on the URDF and geometries of the robot.Accordingly by providing paths to the URDF and it's corresponding collision meshes when initializing/creating
robot::Model
class, a user can allow for collision checking given a certain joint positions configuration.One possible improvement yet to consider is the paths of the meshes inside the URDFs used in the test.
Review guidelines
Estimated Time of Review: 15 minutes
Checklist before merging: