Skip to content
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

WIP: Add AckermannDriveStamped control to steering library #1171

Open
wants to merge 13 commits into
base: iron
Choose a base branch
from

Conversation

wittenator
Copy link

This PR adds the option to use steering angle and linear velocity for controllers that inherit from the steering library. In anticipation of the merging and backport of the fixes in the ackermann controller, I branched off of the fix/steering_controllers_library_kinematics branch and cherry-picked the changes on top of the iron branch.

Status:

  • Fork the repository.
  • Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
  • Ensure local tests pass. (colcon test and pre-commit run (requires you to install pre-commit by pip3 install pre-commit)
  • Commit to your fork using clear commit messages.
  • Send a pull request, answering any default questions in the pull request interface.
  • Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.

Copy link
Contributor

mergify bot commented Jun 17, 2024

@wittenator, all pull requests must be targeted towards the master development branch.
Once merged into master, it is possible to backport to iron, but it must be in master
to have these changes reflected into new distributions.

@wittenator
Copy link
Author

Ah hmm, I can't move our software stack to Jazzy (due to Nvidia dependencies) and therefore have to develop these changes on Iron. Should I develop the feature completely on Iron and then cherry-pick the changes on top of the master? The drawback is that I can't really test in on the master besides a few unit tests maybe.

@christophfroehlich
Copy link
Contributor

Let's merge #1150 first, and then proceed with this one here. Could you please review it and give your feedback (Files changed -> Review changes)?

Copy link
Contributor

mergify bot commented Jun 19, 2024

This pull request is in conflict. Could you fix it @wittenator?

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.

None yet

2 participants