-
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
Comp Merge #164
Comp Merge #164
Conversation
|
I will focus on making auto paths sometime tonight if I can. Here's the auto list I think is realistic for phr. Most of the autonomous work has already been done (sim is awesome); its mostly getting vision now and then tuning the auto pid/paths on the real bot. We also (and i cannot stress this enough) NEED to test driving on the opposing alliance. I'm almost confident that we need to flip the driver controls in some way. WING AUTOS:Start at Top of Subwoofer, score all 4 in a line into speaker CENTERLINE "DASH" AUTOS:Start in-between the top and bottom of subwoofer, immediately score in speaker then do a mad dash (top down) OTHER AUTOSStart at the top of sub, immediately score in the AMP Heres my elegant visualization of starting positions |
Opening this pr not because it's ready, but because I will forget to open it when it is |
Pull request was converted to draft
i will clean up this pr before Thursday (it is SO messy rn) |
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.
@TaylerUva Take your time getting to this comment/pr; i am incapable of taking a break
I glanced over this entire pr for bugs. It has 33 JAVA files and i think i almost died in the process. I left comments and made issues for major things i noticed; otherwise, I think its okay. This pr contains all of our testing from the past week or so so its obviously huge
AUTO TESTING:
-1. Finish adding event markers to the paths (Will be done before the meeting starts. its just intaking)