-
Notifications
You must be signed in to change notification settings - Fork 494
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
Use constraint distance instead of bool validity in STOMP cost function #2418
Merged
sjahr
merged 2 commits into
moveit:main
from
henningkayser:pr-stomp_constraint_distance
Oct 24, 2023
Merged
Use constraint distance instead of bool validity in STOMP cost function #2418
sjahr
merged 2 commits into
moveit:main
from
henningkayser:pr-stomp_constraint_distance
Oct 24, 2023
Conversation
This file contains 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
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2418 +/- ##
==========================================
- Coverage 50.87% 50.47% -0.40%
==========================================
Files 386 385 -1
Lines 31983 31829 -154
==========================================
- Hits 16269 16062 -207
- Misses 15714 15767 +53 ☔ View full report in Codecov by Sentry. |
sjahr
approved these changes
Oct 11, 2023
henningkayser
added
the
backport-iron
Mergify label that triggers a PR backport to Iron
label
Oct 17, 2023
Jakubivan
pushed a commit
to Jakubivan/moveit2
that referenced
this pull request
Mar 13, 2024
…on (backport moveit#2418) (moveit#2476) * Use constraint distance instead of bool validity in STOMP cost function * Fix comment (cherry picked from commit c19d2aa) Co-authored-by: Henning Kayser <henningkayser@picknik.ai>
Jakubivan
pushed a commit
to Jakubivan/moveit2
that referenced
this pull request
Mar 13, 2024
…on (backport moveit#2418) (moveit#2476) * Use constraint distance instead of bool validity in STOMP cost function * Fix comment (cherry picked from commit c19d2aa) Co-authored-by: Henning Kayser <henningkayser@picknik.ai>
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 enables STOMP to optimize on the more precise distance gradient of a constraint set instead of the very imprecise const penalty.