-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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(controller-server): publish_zero_velocity
parameter
#4675
feat(controller-server): publish_zero_velocity
parameter
#4675
Conversation
For optionally publishing a zero velocity command reference on goal exit. Publishing a zero velocity is not desired when we are following consecutive path segments that end with a velocity. Signed-off-by: Rein Appeldoorn <[email protected]>
9964673
to
9f611a6
Compare
This pull request is in conflict. Could you fix it @reinzor? |
Codecov ReportAttention: Patch coverage is
|
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.
Just the usual migration + configuration guide update to introduce the new parameter.
476aa82
to
15698d4
Compare
Signed-off-by: Rein Appeldoorn <[email protected]>
15698d4
to
6e5e0c3
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.
LGTM. Add to the migration guide the change + new parameter and add to the controller server's configuration guide the new parameter for documentation for future lookers
Edit: Sorry that wasn't supposed to be an approval, but the remaining items are trivial
Signed-off-by: Rein Appeldoorn <[email protected]>
e61bd07
to
ea15808
Compare
@SteveMacenski can we backport this on Jazzy? I can alter the change so that we maintain ABI compatible. |
@reinzor sure! An altered version would need to be done, but should be easy enough - basically just use the existing method and add in a comment with this PR number to mention this backport for why the naming doesn't 100% line up |
…ation#4675) Backport of ros-navigation#4675 Signed-off-by: Rein Appeldoorn <[email protected]>
…ation#4675) Backport of ros-navigation#4675 Signed-off-by: Rein Appeldoorn <[email protected]>
…port (#4687) * feat(controller-server): `publish_zero_velocity` parameter (#4675) Backport of #4675 Signed-off-by: Rein Appeldoorn <[email protected]> * Update nav2_controller/src/controller_server.cpp Co-authored-by: Steve Macenski <[email protected]> Signed-off-by: Rein Appeldoorn <[email protected]> --------- Signed-off-by: Rein Appeldoorn <[email protected]> Signed-off-by: Rein Appeldoorn <[email protected]> Co-authored-by: Steve Macenski <[email protected]>
This feature has been verified in production 🙂 Would a Jazzy bloom release be in order? As the last one was from August. |
For optionally publishing a zero velocity command reference on goal exit. Publishing a zero velocity is not desired when we are following consecutive path segments that end with a velocity.
#4674