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
planner_cspace: publish empty path immediately after planning aborted #326
planner_cspace: publish empty path immediately after planning aborted #326
Conversation
[#911] PASSED on kineticAll tests passed
[#911] PASSED on lunarAll tests passed
[#911] PASSED on melodicAll tests passed
|
Codecov Report
@@ Coverage Diff @@
## master #326 +/- ##
=========================================
+ Coverage 64.26% 64.3% +0.03%
=========================================
Files 56 56
Lines 4016 4017 +1
=========================================
+ Hits 2581 2583 +2
+ Misses 1435 1434 -1
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.
Without this, the robot may still rotate for a while until next loop.
This rotation is under control of trajectory_tracker, not a kind of free running, which minimize the error to the desired final pose.
I agree to publish empty path immediately on abort.
But on success, publishing empty path means to abort orientation control; which is basically unintended behaviour.
Okey, if the delay is intended behavior, I'll remove empty path publishing snippet and add comment on success case. If we use action client to the |
[#912] PASSED on kineticAll tests passed
[#912] PASSED on lunarAll tests passed
[#912] PASSED on melodicAll tests passed
|
@at-wat PTAL when you have time. |
Actually, it's difficult to define STOP state of the 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.
LGTM
merging |
Good to know, thanks. |
This PR make a robot stop immediately after path planning completed; succeeded or aborted.
Without this, the robot may still rotate for a while until next loop.
e.g. rotates at least 0.25 sec. by the default parameter
freq=4Hz
).