View Single Post
  #176   Spotlight this post!  
Unread 01-05-2012, 03:34
EricH's Avatar
EricH EricH is offline
New year, new team
FRC #1197 (Torbots)
Team Role: Engineer
 
Join Date: Jan 2005
Rookie Year: 2003
Location: SoCal
Posts: 19,755
EricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond repute
Re: Einstein Field issues Handled correctly?

Given the overall situation (extended history of problems), no, the issues weren't handled properly.

Given the immediate situation on Einstein... Tough call, but I have to go with yes, under the circumstances.

Overall, the "it's not the field it's your robot" type of statements--and the fact that much of the time, doing something to the robot made the situation better--served to not get the problem addressed sooner. Overall, that's an issue. Sweeping a problem under the rug doesn't make it go away. It's better to face it head-on and try to run some tests--I know at an internship after some testing of a troublesome part we were able to tell a customer, "When properly set up, the whatsits perform as advertised. We see they haven't been set up properly in your situation." (We were also looking at possible alternative methods to perform the function of the whatsits in case of inability to set up properly.) If you think there's an issue, go for the root cause.

For the immediate situation, there are a lot of factors going into this one.
First, you have the published documentation. Replays are by field fault or true tie only under the rules. And you can't for sure say that this is a field fault (we're assuming that you're looking at only Einstein). So, by ruling it a field fault and replaying the first two semis matches, when there was no concrete evidence that it was a field fault, they did do their best to accommodate teams. Positive point.
Second, you have the big picture. Looking beyond just Einstein, the robots worked better on the divisional fields. This puts the weight towards it being a field fault, so more replays should have happened. Negative points.
Third, you have the schedule. The Championship traditionally runs over--the only question is, how far? By issuing more replays, you lengthen the time--and shorten the night out--and possibly force teams to choose between staying or heading for home in time to get some sleep before Monday's return to the daily grind. This balances out the big picture look, so you do limited replays. Positive point.
Fourth, the weather. In bad weather, staying inside is the place to be--and you don't want to be running to vehicles in a hailstorm. But, it has the potential to interfere with all types of electromagnetic radiation, including the field control system wireless. The thing is, most electronics will be built to handle that interference these days, because it's a known potential issue. So that's a moot point (other than the keeping people inside because of weather part--a positive but unrelated point).

With the scale being balanced like that, it's time to play "benefit of the doubt" and "20/20 hindsight" cards and say that FIRST handled the immediate Einstein issues as best as they could under less-than-ideal circumstances, but needs to be more proactive in looking into possible root causes when untraceable issues crop up in large-ish numbers.
__________________
Past teams:
2003-2007: FRC0330 BeachBots
2008: FRC1135 Shmoebotics
2012: FRC4046 Schroedinger's Dragons

"Rockets are tricky..."--Elon Musk

Reply With Quote