[OMPL] also check constraints in StateValidityCallback (backport #3586)#3649
Open
mergify[bot] wants to merge 1 commit intokiltedfrom
Open
[OMPL] also check constraints in StateValidityCallback (backport #3586)#3649mergify[bot] wants to merge 1 commit intokiltedfrom
mergify[bot] wants to merge 1 commit intokiltedfrom
Conversation
(cherry picked from commit ca2bb1b)
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## kilted #3649 +/- ##
========================================
Coverage ? 0.00%
========================================
Files ? 207
Lines ? 23096
Branches ? 3145
========================================
Hits ? 0
Misses ? 23096
Partials ? 0 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This allows the IK solver to continue finding a valid solution, which also satisfies the kinematic constraints.
In the old situation the IK solver would return a solution, which it thinks is valid, but it is not. The sampler will keep calling the IK solver. Though for IK solvers, which are not that random. There is a high chance of returning the same solution over and over. Which keeps failing the constraints.
By checking the constraints in the callback the IK solver will continue and return a valid solution.
Please backport to Jazzy and others
Checklist
This is an automatic backport of pull request #3586 done by [Mergify](https://mergify.com).