Quote:
Originally Posted by Zyik
What if a team is just beginning to develop their autonomous? If they had something that told the robot to go forwards x amount of feet to cross the first line, but somehow came out as x amount of inches, it might be seen as a "defensive autonomous" when it wasn't. If a robot hit them the first time they tested this and they didn't know it did this, should they be given a yellow card?
If they were, that would really discourage teams from attempting to write and autonomous mode in the middle of a regional. Writing code halfway through Friday is a time honored tradition, and I'd hate to see it go away. 
The point being, until you see the team do this multiple times in a row, don't assume anything. |
Good point. Last year, our Friday written rookie autonomous was supposed to drive to the center of the field and stop to prepare for playing defense. The first time we ran it, our robot drove clear across the field and rammed an opposing robot because I guessed a time wrong. Getting a yellow card wouldn't have made me very happy.
Quote:
Originally Posted by Jack Jones
YES! FIRST has been raising the bar and aiming high for some time now. A failure to prepare should have consequences.
|
No! Why would you want to discourage rookies that had a hard enough time getting a working robot in the crate on time (and everyone else, for that matter) from trying something simple but effective? The line violations in autonomous are discouragement enough from trying as it is. Wouldn't you prefer your alliance partners go for those 4 points?
and...
Quote:
Originally Posted by Drwurm
As soon as the robot makes a turn, your IR board becomes somewhat useless.
|
Not if you have an omni drive like us!
