-
Notifications
You must be signed in to change notification settings - Fork 381
JTC add more options for tolerance configuration #1677
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
base: master
Are you sure you want to change the base?
JTC add more options for tolerance configuration #1677
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1677 +/- ##
=======================================
Coverage 85.69% 85.69%
=======================================
Files 123 123
Lines 11897 11900 +3
Branches 1015 1015
=======================================
+ Hits 10195 10198 +3
Misses 1379 1379
Partials 323 323
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
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.
Thanks for tackling this issue.
This PR is not functional yet, right? However, I added some early review comments.
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.
I think the initial idea was to have them per-joint, as it is used in the action
https://github.com/ros-controls/control_msgs/blob/master/control_msgs/action/FollowJointTrajectory.action
and defined here
https://github.com/ros-controls/control_msgs/blob/master/control_msgs/msg/JointTolerance.msg
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.
I suggest adding the parameters constraints.__map_joints.trajectory_velocity
, constraints.__map_joints.goal_velocity
etc. We cannot easily rename the old parameters, as it would change existing code. If necessary, we have to deprecate the old parameters and add something like
constraints.__map_joints.path.position
constraints.__map_joints.path.velocity
constraints.__map_joints.path.acceleration
// Read new velocity and acceleration tolerances | ||
velocity_tolerance_ = get_node()->get_parameter("constraints.velocity_tolerance").as_double(); | ||
acceleration_tolerance_ = | ||
get_node()->get_parameter("constraints.acceleration_tolerance").as_double(); |
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 don't need to use get_parameter() method. Have a look at the structure params_ , generate_parameter_library automatically fills this.
Yes this PR is still a work in progress, have been busy with other work hence haven't got enough time to complete this. |
Closes #1180
Added new Parameters velocity_tolerance and acceleration_tolerance, to the Joint Trajectory Controller.