-
Notifications
You must be signed in to change notification settings - Fork 82
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
Custom robot model loader does not respect joint_limits.yaml files #42
Comments
which version of MoveIt do you use? The helper function you mention should not actually be called anymore because MoveIt prefers an initializer that passes the robot model from MoveIt directly. So yes, there is (at least one) issue with this code, but it also should not matter and the code could be deleted from what I can see. |
I'm using ROS Kinetic and I can confirm on my version of Your point does seem correct that for newer versions of moveit (melodic for example) a different version of |
This repository has a Other group members might disagree. |
FWIW, I'm not using the In my opinion, the custom loader is incorrect regardless of which version of moveit is being used. As a result, I think you're completely correct in asserting that the ideal PR would remove that loader. |
Many tools in MoveIt! use a
RobotModelLoader
create amoveit::core::RobotModel
. Inbio_ik
a custom helper function is used. Unfortunately, this custom loader does not look at ajoint_limits.yaml
file (like theRobotModelLoader
does). What this means is that if you have a URDF that defines one set of joint limits, and you usejoint_limits.yaml
file to set a different set of joint limits for the purposes of planning (a setup that is commonly used in MoveIt, including packages generated with the setup assistant). Then, when usingbio_ik
it's possible to get IK solutions (for example fromrobot_state::RobotState::setFromIK
) that are outside of the motion planning limits defined by thejoint_limits.yaml
file, but inside of the limits defined in the URDF.The text was updated successfully, but these errors were encountered: