-
Notifications
You must be signed in to change notification settings - Fork 531
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
Declare joint limit parameters #408
Conversation
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.
Generally looks good! I'm not very familiar with ROS2 so somebody else should def review this.
moveit_ros/planning/robot_model_loader/src/robot_model_loader.cpp
Outdated
Show resolved
Hide resolved
moveit_ros/planning/robot_model_loader/src/robot_model_loader.cpp
Outdated
Show resolved
Hide resolved
e962ad4
to
a051d57
Compare
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.
This looks good. Just a small comment to check.
Also adding some tests would be nice.
moveit_ros/planning/robot_model_loader/src/robot_model_loader.cpp
Outdated
Show resolved
Hide resolved
a051d57
to
ee173df
Compare
Joint position, velocity, and accleration parameter limits where not declared in the `robot_model_loader`. This prevented the use of joint limits.
ee173df
to
1eb8269
Compare
Codecov Report
@@ Coverage Diff @@
## main #408 +/- ##
==========================================
- Coverage 53.04% 52.97% -0.06%
==========================================
Files 212 212
Lines 22612 22622 +10
==========================================
- Hits 11992 11982 -10
- Misses 10620 10640 +20
Continue to review full report at Codecov.
|
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.
LGTM
But I'm not sure if we should explicitly specify the default values (0.0 & false) when declaring the parameters,
Currently, if the user didn't load the joint limit parameters and in another function, they called get_parameter
for one of the joint limit parameters they will get 0.0/false rather than PARAMETER_NOT_SET
which may not be expected
@AndyZe @destogl @henningkayser what do you think .?
moveit_ros/planning/robot_model_loader/src/robot_model_loader.cpp
Outdated
Show resolved
Hide resolved
I would rather not set defaults |
That is a good point. Will update to remove the default parameters. |
Removed defualt values for joint limits and print error message if a limit is indicated but not limit is specified.
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.
lgtm, would it be difficult to add a test of this? Just have a test that sets the parameters using the c++ ros parameter interface or via loading a yaml and checks that those are parsed correctly by this code?
Writing a useful test for this is somewhat difficult. The robot loader does not have a method to easily retrieve the joint limits. If I use a node to set them and get them then I am really only testing whether or not the loader will throw and exception. |
3x +1's --> let's get this merged and make an issue to write a test |
Joint position, velocity, and accleration parameter limits
where not declared in the
robot_model_loader
. This preventedthe use of joint limits.
Checklist