-
Notifications
You must be signed in to change notification settings - Fork 0
Choreo accuracy & improved mobility autos #70
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
base: main
Are you sure you want to change the base?
Conversation
* terminate the command. | ||
* @return A command to drive to the target pose, terminating once at acceptable error. | ||
*/ | ||
public static Command simpleGoToPoint(Drive drive, Pose2d target) { |
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.
From how far away did you test this PID-only pathing, and what did it behave like? It seems like it was good, or else you wouldn't recommend it. I can watch tomorrow too.
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.
Tested from about 2.7178 m and 180 degrees. Seems decently smooth, although a bit slow
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.
Looks fine. I would like to see the dynamic pathing myself and a quick test of the new mobility paths.
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.
assuming that you have the testing to back it up, which im pretty sure you do, this looks like an improvement to me
Give Choreo real robot numbers, lengthen mobility autos as requested by strategy, minor refactor of choreo trajectories, and use exclusively PID for driver assist
TODO: