-
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
nav2_simple_commander skips waypoints after every recovery action #3107
Comments
Can you provide logs? It could be that navigation straight up failed and said it was moving onto the next waypoint because you had Also, do you have some reproducable set of waypoints / map you can share? That would make helping fix this much easier. |
Can you see if #3130 also fixes your problem? From a bunch of testing in that, I could not reproduce any kind of skipping, but I could see how this might be the same root cause. If some extraneous But logs would be superbly helpful if this doesn't fix your issue @MrOCW |
Here is a portion of the logs. It seems that the waypoints move on immediately once the goal fails now. Is this expected behaviour? If i would like the robot to try several times, I should increase the number of retries parameter in the behaviour tree?
|
Yes, retry mechanisms should be exhausted as part of the behavior tree. If navigation tells us it has failed, the waypoint follow are basically have to take it at face value. You can stop on failure using a parameter though if you’d rather stop the waypoint following task entirely on a failure.
That would be my recommendation. Optionally, we could consider adding a retry mechanism into the waypoint follower. but it seems like the likely best place for it is the behavior tree itself so it can be more informed. Sounds like the PR / that explanation buttons things up! |
Bug report
Required Info:
Steps to reproduce issue
Use more goal poses in example_waypoint_follower.py
Expected behavior
Only execute next waypoint when robot is near the waypoint
Actual behavior
The waypoints are skipped very quickly, presumably during the recovery actions
The text was updated successfully, but these errors were encountered: