Skip to content
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

Enable recovery_behavior #1192

Merged
merged 5 commits into from
Jul 16, 2021

Conversation

YutoUchimi
Copy link
Contributor

Change parameters to enable recovery_behavior.
This can be useful when robot is stuck by obstacles.

Still testing with real robot.

@k-okada
Copy link
Member

k-okada commented Dec 20, 2019

Why you disabled at 60f8a5a#diff-b7c5d42e85d8c0ca16a95d0eafab7b60 and re-enabled?

@YutoUchimi
Copy link
Contributor Author

  • Why I disabled?
    According to http://wiki.ros.org/move_base#Parameters , the default value of ~max_planning_retries is -1, which means recovery_behavior is disabled by default.
    To notice this fact easily, I added a comment in b51f2c6 .

  • Why I (re-)enabled?
    The problem is how to deal with moving obstacles such as human.
    Assume that human is standing 2 meters in front of the robot, and robot rotates 180 degrees in place.
    Then a user commands the robot to go to the place the human was standing.
    In this case, even if the human went away, the robot fails to plan to reach the goal, since the robot cannot observe that the human has already gone.
    The robot has to rotate in place to update costmap, so I enabled recovery_behavior.

With this PR, move_base itself will give up on going to the target spot in some case.
If you want to retry forever, you must control from upper level such as euslisp (send *ri* :move-to coords :retry *inf*)

@k-okada k-okada merged commit 3d4f157 into jsk-ros-pkg:master Jul 16, 2021
@knorth55 knorth55 mentioned this pull request Sep 11, 2022
61 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants