Quote:
Originally Posted by Dezion
It's really not fair to have your robot not compete because of this. I agree it is a huge issue for a lot of teams, but I don't believe punishing the team that did it in this scenario is the right response. I believe that it should be expected that this can occur, and teams should be prepared for this. Teams have to prepare for the game in all aspects. Having your driver station crash by being hit by the force caused by a robot prevents you from playing; having your robot break by bring hit by the force caused by another robot prevents you from playing. With the chance of a driver station crashing, causing the same effect as a robot breaking, shouldn't teams prepare for a robot hitting their castle wall as well as hitting their own robot?
Basically, I agree with this:
|
If you are going to take this stance I have a question,
How do you plan to prevent your laptop from blue screening assuming your driver station is attached with velcro?
Currently the sentiment from FIRST would indicate to me that if I wrote an autonomous that ran our robot in the alliance wall on purpose there isn't much they would do to stop this.
FIRST has so far seems to have ignored the intent of someone hitting the wall. I'm sure if we blatantly hit the wall in an attempt to disable our opponents people wouldn't be very happy with us.
I'd like to see a change so that all teams shouldn't have to worry about this situation. As said in another thread
Quote:
Originally Posted by Richard Wallace
Lazy auto programming should not be rewarded.
|
Most instances seem to be people not writing a proper autonomous code and ignoring the consequences by hiding behind the team update.
I want to see a better option than the current one.