View Single Post
  #11   Spotlight this post!  
Unread 10-02-2007, 14:35
Tristan Lall's Avatar
Tristan Lall Tristan Lall is offline
Registered User
FRC #0188 (Woburn Robotics)
 
Join Date: Aug 2001
Rookie Year: 1999
Location: Toronto, ON
Posts: 2,484
Tristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond reputeTristan Lall has a reputation beyond repute
Re: [YMTC]: field of view

Quote:
Originally Posted by Kevin Sevcik View Post
If you're saying driver on the proper side of the road is just at much at fault as the driver on the wrong side of the road, and, therefore, no tickets (penalties) should be given.... Well then I'll be sure to avoid Toronto.
That's not what I said. The wrong-side driver is at fault for being on the wrong side, and he's guilty of something serious (e.g. dangerous driving, crossing a solid dividing line, wrong-way driving, etc.). But if the driver on the correct side of the road, having observed that there's an oncoming car in his lane, doesn't attempt to take precautions to avoid a collision, he's guilty of careless driving (though as a practical matter, this is probably unenforced). If the situation is so dangerous that it is to be avoided at all times (a traffic collision, for example), you're required to choose your actions responsibly, even if not at fault. In any event, I disagree that not being able to see your robot is (always) that dangerous.
Quote:
Originally Posted by Kevin Sevcik View Post
<S01> discusses robots creating unsafe situations. Not field elements. Teams are, presumably, planning on having their vision partially obstructed by the rack. Teams are not planning on having their sight completely and utterly blocked by another robot that can run around the field blocking vision anywhere it likes. The point is that field elements, etc, are a known quantity. Robots tossing in additional unsafe situations are an unknown and to be avoided.
In the hypothetical case of the rack causing a visual obstruction, the robot creating the unsafe situation would be the one moving outside of the driver's field of view. The driver chooses where to position the robot, and has the option of not passing behind the rack. If the result (i.e. the robot is uncontrolled because it is not visible) is a severe hazard, worthy of enforcement under <S01>, then making a conscious choice to create that hazard ought to be treated equivalently—whether your robot is the obstacle or the obscured.

Isn't the real issue here that it screws up the game for the team being blocked, and not that it's always a serious safety risk? And isn't that an issue to be dealt with on a gameplay basis, not on a safety basis?
Reply With Quote