Quote:
Originally Posted by masoug
Once in 2010 Breakaway competition, our autonomous code "shorted out" and our robot ran at full speed at a graceful curve and slammed into another robot, flipping it over.
The other team forgave us...
|
My code from 2010 calgames made up for that sort of, that was a seriously sweet drift around the robots that all piled up in the middle of the field. Concerning that year, I
did *cough cough* say just keep the robot turned around and it won't end up toppling another robot. In my defense, the code was right, I was just using the wrong workspace, and I'm glad Pally (I didn't actually see it happen, I was in the pit, so excuse me if I'm wrong) was forgiving about it. The best autonomous code ended up being us sitting there running the compressor. But really, you should know by now that when I say the code works, I'm wrong, but when I say I'm right about something, robot code included, I'm right.
Basically, it's a thin line between admitting you're wrong and making an argument of why your right so poorly put together it can't be taken apart any more, making it just about as good as a solid one.
On an somewhat unrelated note, I do remember something in '08 where we knocked down all 3 of the opposing alliances driver stations in possibly 2 consecutive matches during autonomous. All I can say is that, while they were quite professional about it, they weren't horribly pleased my our sudden movement of the entire field.