Skip to content

Conversation

@barulicm
Copy link
Contributor

This PR centralizes our core motion stack, introducing the MotionExecutor and motion intents.

There should be minimal to no behavioral changes for the full system.

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
Copy link
Contributor

@chachmu chachmu Sep 29, 2025

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

Copy link
Contributor Author

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. 🙃

@barulicm barulicm merged commit 9f9eaaf into main Oct 12, 2025
1 check passed
@barulicm barulicm deleted the dev/barulicm/motion_refactor branch October 12, 2025 22:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants