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.
Why
This is an edge case in my application, but if an obstacle suddenly appears in front of the robot, TEB's solution might diverge quite noticeably. As an example, I obtained the image below by suddenly dropping an obstacle in front of the robot in simulation.
Summary
After some investigation, I've observed that (given my configuration) the value of
chi2
in the optimizer statistics remains around 1 when the robot is navigating. Still, it increases drastically if the trajectory diverges, reaching values above 1000. This seemed to me to be the best parameter to monitor to detect divergence, but I might be missing the context of other applications (my robot is a differential drive one, which runs at most at 0.75 m/s).Related Issues
Might help with #61 #257 #7 #200