Quote:
|
Originally Posted by Andrew Schuetze
Are any teams planning sense capability for other robots during autonomous 
I know we haven't as of yet. We're still working on design ideas and actually hitting the target.
How are teams planning for the possibility that a second or third robot is going to "Aim High" during autonomous? A lot of alliance talk is needed before a match but how do the robots keep from hitting each other?
APS |
You write different autonomous programs to deal with this. Last year, I believe, our autonomous students wrote something like 32 different programs for the robot. We probably only used 3 total during the whole competition season, but we had the others ready, just in case. (i.e., MOEbius could quickly and reliably block the center goal in autonomous last year, in case we went up against some team capable of capping with a vision tetra. Never had to use it though.)
Having so many options in autonomous helps meld your robot into an overall alliance strategy. Each robot should have a minimum of four autonomous options this year: scoring in the right goal, scoring in the left goal, shooting at the center goal, and just sitting still. In past years, with a longer autonomous period, you could delay a bit before your robot moved. I'm not sure you have the luxury of using that strategy this year.
If you want to play aggressively, you can write an autonomous program to go disrupt the other alliance. A bit riskier, since you are initiating contact without control. Hopefully, you don't run into someone elses "roundhouse right" autonomous program.
