Thread: Team Update #18
View Single Post
  #10   Spotlight this post!  
Unread 20-03-2007, 22:37
ChuckDickerson's Avatar
ChuckDickerson ChuckDickerson is offline
Mentor / Bayou & CMP Division LRI
FRC #0456 (Siege Robotics)
Team Role: Mentor
 
Join Date: May 2004
Rookie Year: 2004
Location: Vicksburg, MS
Posts: 877
ChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond reputeChuckDickerson has a reputation beyond repute
Re: Team Update #18

Why is it inherently unsafe? Shouldn’t it be a decision between the three teams of the alliance if they think they can pull it off safely not someone in NH that isn’t even there? If the refs feel that a robot is precariously placed or otherwise unsafe before a match begins then they should call the team(s) out to fix it whether they are stacked or not. I fail to see why this is a safety issue at all. Again, this year FIRST is forcing a veteran team on each alliance so they should be able lead the younger teams as to whether a stack is a good idea or not. The reason this is such a brilliant play is that there is HUGE risk involved and weighing whether it is a safe play or not is part of the game. If the scheduling algorithm was like in the past and you had 3 rookie teams on an alliance unsafely trying to pull of a stack without any one telling them that it is a bad idea then I might understand but that is and impossibility this year and the refs are always there as a backup plan anyway to keep us all safe with the big red buttons.
Reply With Quote