Quote:
Originally Posted by Kris Verdeyen
Don't have anything to add except to say that this is not true. The problems in CT were never diagnosed. We swapped out a cRio in Houston because we saw the same thing in a practice match, and couldn't bear the thought of doing nothing, even though the cRio swap didn't make much sense. We had no problems after that swap until what you saw on Einstein.
|
I'm glad to hear you state this. This is what I had heard through the channels, but I had yet to hear it firsthand. I recall the announcement at CT, that there was "no way that the field could have caused a robot's cRIO to reboot." I subsequently talked to about a dozen engineers who said (while never saying "that's not true") words to the effect "there's no way you can make such a blanket statement as that."
I'm split when it comes to answering the OP question. There is not much else the field administrators could have done. To put it as simply as possible, there IS an issue. The issue has affected teams that have the BEST software and engineering minds. The problem/s remain elusive and diagnoses have been numerous and varied.
Administration needed to make a decision, and they did not have all day to do so. It looked like a no-win decision.
Robonauts, we all ached for you. We hope we get to see you triple-balance at least one more time!
Let's not forget to congratulate the champions.