Replies: 1 comment 1 reply
-
The approach that our team settled on this year is to create an auto for each possible branch in the decision tree. (We place all of these related autos in a folder to keep them organized.) We then introduce the conditional logic in the command that we build in the Robot Container class. For example, here is the code for our 4-note source-side auto:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What advice would you give to making an auto conditional? We've had a lot of luck with simply defining paths, and connection them together with commands and other paths in autos. But we would now like to explore some conditional behavior. For example, if going to get a note, and failing (because it's been removed), getting a different note instead, before returning to a shooting position, etc. I'm sure it's possible, but I'd like not just to do it, but to do it well (especially as I'm a mentor, so I'd like to give the students good advice).
Beta Was this translation helpful? Give feedback.
All reactions