-
Notifications
You must be signed in to change notification settings - Fork 534
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
STOMP - MotionPlanDetailedResponse #2704
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2704 +/- ##
==========================================
- Coverage 50.74% 42.59% -8.15%
==========================================
Files 392 692 +300
Lines 32553 56369 +23816
Branches 0 7277 +7277
==========================================
+ Hits 16517 24005 +7488
- Misses 16036 32203 +16167
- Partials 0 161 +161 ☔ View full report in Codecov by Sentry. |
This current implementation runs |
This PR is stale because it has been open for 45 days with no activity. Please tag a maintainer for help on completing this PR, or close it if you think it has become obsolete. |
This PR is stale because it has been open for 45 days with no activity. Please tag a maintainer for help on completing this PR, or close it if you think it has become obsolete. |
Description
Attempt to implement the MotionPlanDetailedResponse function for the STOMP solver. Currently, I have implemented it similarly to CHOMP, which means there's only one element in the trajectories vector which is the solution of the MotionPlanResponse STOMP solver. This can be instead changed for the following implementations:
res.trajectory.back()
would contain the final optimized solution.EDIT:
As per #1708 since MotionPlanDetailedResponse is intended for debugging purposes, appending intermediate generated trajectories from STOMP seems like the way to go.
Fixes #2168
Checklist