-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feat/swerve #3
Feat/swerve #3
Conversation
don't merge yet. going to delete the jank pathplanner stuff; leave empty slate for future dev |
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.
Changes look good but I think because you did swerve related stuff we should wait until it is tested on Saturday to merge into dev. I merged Derek and I's changes today which were really just removing pp errors (so mostly deleting stuff, you basically have the same changes here). So dev should be pretty good rn, and we can use this branch on Sat for swerve testing.
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 this code today and it functions, swerve values need to be tuned but this code can be merged into dev
Implement Phoenix 6 swerve builder, should function very similarly (for basic drive, not sure about odometry, have to look into that)
In order to get rid of unrelated errors to work on swerve I... very messily commented out/deleted the offending files. So, anything related to pathplanner had been commented out and it's very messy (like GOOD GOD is it messy). Should I just delete those files so later pathplanner developments can just fill them in?Deleted all pathplanner-related files, left a blank-ish slate for future development
Also not entirely sure about how good the swerve implementation is.