-
Notifications
You must be signed in to change notification settings - Fork 0
Motion Stack Refactor #374
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
Conversation
| double max_angular_velocity = 3.0; // rad/s | ||
| double max_angular_acceleration = 4.0; // rad/s^2 | ||
|
|
||
| double max_allowed_turn_angle = M_PI / 4.0; // radians |
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.
This variable name that I wrote is not great, probably need to come up with something more descriptive of what it actually does
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.
Realistically, we'll likely never find a name that's fully descriptive on its own and a variable like this needs a doc comment to explain it.
In this instance, though, a lot of these options are going to change / disappear in the upcoming path planning rewrite, so...... this problem will solve itself. 🙃
This PR centralizes our core motion stack, introducing the
MotionExecutorand motion intents.There should be minimal to no behavioral changes for the full system.