Quote:
Originally Posted by Chris Hibner
In the original match in question, the clock malfunctioned with approximately 15-20 seconds to go in the match. It was not after the deployment period had begun.
Team 903 from the blue alliance was lined up with the tower waiting to deploy their minibot and did not deploy at the 10 second mark because they didn't know how much time was left and they didn't want to risk getting their tower disabled. They ended up deploying well after the start of the deployment period and lost the minibot race. I believe the red alliance won the original match by 5 points, so the minibot race affected the outcome of the match.
I was sitting in the stands and the referee question circle was right in front of me (about 6 feet away). Members from 903 stood in the circle after the match. No one from team 51 was present while I was in the stands. Just about the time the head referee came to talk to the 903 student representative, I left the stands so I guess it's possible that someone from 51 later showed up. At that time, 903 was ranked in the top 8 so a win was very important for them.
I didn't find out the match would be replayed until about an hour later.
To be honest, at the time I was more upset at us for losing that match so I didn't care about the the clock issue. We delayed significantly before deploying our minibot (due to the clock issue) so we weren't going to win the race, but just getting the minibot up the pole would have won the match. That was the ONLY unsuccessful deploy we had all weekend (the minibot bounced off the pole) so all I could think about was what were we going to do to keep that from happening again. The clock issue was a bit of an afterthought at the time.
|
Thanks for clearing this up for me!
When I asked the head ref, he said that a member of team 51 came to him, and that the clock malfunctioned with 4-8 seconds left, so the information I had was incorrect.