View Single Post
  #16   Spotlight this post!  
Unread 04-03-2016, 22:17
Sperkowsky's Avatar
Sperkowsky Sperkowsky is offline
Professional Multitasker
AKA: Samuel Perkowsky
FRC #2869 (Regal Eagles)
Team Role: Leadership
 
Join Date: Jan 2015
Rookie Year: 2014
Location: Bethpage, NY
Posts: 1,893
Sperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond reputeSperkowsky has a reputation beyond repute
Quote:
Originally Posted by orangemoore View Post
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
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.
If your laptop is properly secured there is a higher probability that the opposing robot will break itself then your laptop although it's definitely possible.

Id recommend everyone changing out hard drives in their laptops to ssds. You can get a 60gb model for under $50 and will most likely prevent your laptop from bsoding after impact.
Reply With Quote