Better fix for #523 respecting planner_frequency intended behavior #622
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Essentially I'm reverting 679ee2b but adding this line: https://github.com/ros-planning/navigation/compare/kinetic-devel...corot:better_fix_for_523?expand=1#diff-d6afbf7b921c7c246a6ee2454dc05be4R609
Now seems to work as expected: the new parameter max_retries does as expected, the planner stops while recovering and keeps replanning while moving if planner_frequency > 0
Not thoroughly tested, so please, give it a good try!