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

Update Auto Score (Manual Strafing) #37

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

Update Auto Score (Manual Strafing) #37

wants to merge 13 commits into from

Conversation

ezi-0
Copy link
Contributor

@ezi-0 ezi-0 commented Feb 22, 2025

Added capability to strafe using magnitude and binary direction (left or right), currently bound to LEFT and RIGHT TRIGGER
This is intended to be the basis of the auto-alignment subcommand within the Auto Score command; strafing will be needed to align with the side of the reef we wish to score on, whether manual or not this function is needed.

Update also includes framework for the rest of Auto Score, such as the sequence of every command involved and a folder in which those commands should be found (autoscore).

@smoser-frc
Copy link
Contributor

I pulled out the strafing trigger binds and put it into #40 .
I think the rest of this is more a work in progress, but I think that bit has real value right now (i think it will really help our driver, thanks).

@ezi-0
Copy link
Contributor Author

ezi-0 commented Feb 24, 2025

I pulled out the strafing trigger binds and put it into #40 . I think the rest of this is more a work in progress, but I think that bit has real value right now (i think it will really help our driver, thanks).

That's cool for now, the other parts were all experimental anyways; I'll keep working on the rest in this branch (my goal is to hopefully have a command which will do both strafing and rotational alignment during autoscore, the manual strafe was really just a starting point but it will definitely be useful on Friday & Saturday). Thanks for trimming some of the fat on this code.

BTW, I was thinking of making some slight tweaks to the numbers to allow for more fine control. We can look at this and try different values on Monday.

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.

2 participants