-
Notifications
You must be signed in to change notification settings - Fork 111
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
Motion planning cleanup #1629
Motion planning cleanup #1629
Conversation
Love the chart, BTW. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're already addressing my comments, but in my opinion, nothing I've picked out needs to be adjusted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! I left a bunch of comments about organization. Going to come back to this for a second pass and take a closer look at the smoothing we're doing because there are documented algorithms that we might want to look into rather than do our own thing
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This is a followup to this PR: #1604
It does a lot of organizational things that would have been nice to have in the original but were left out, for time/size purposes, namely:
planner
generic from which all of our planners inheritAdditionally, it makes the following behavior changes to improve quality of path: