SimpleScoredSamplingPlanner
- try fallback generators even if valid trajectories were found (option)
#1201
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 MR was created?
Currently It is impossible to use multiple trajectory generators that are treated equally (when second and next ones are not fallback generators). It is a clear limitation to local planner design.
What was done?
I've added extra parameter to the
SimpleScoredSamplingPlanner
constructor so user can actually select if, e.g., the second generator is the fallback one or should always be checked (just like the primary generator).Does it affect API of the previous applications?
No, because: