![]() |
In b4 buttongate
As if UNH district finals couldn't get more weird...
|
Re: In b4 buttongate
I'll bite, what are you talking about? I'm 1800 miles away ......
|
Re: In b4 buttongate
Quote:
I am not sure if that had any effect on the outcome of the match, but the whole thing was very bizarre. |
Re: In b4 buttongate
i would very much like to see this, is there any video uploaded (or going to be uploaded soon?)
|
Re: In b4 buttongate
Quote:
|
Re: In b4 buttongate
I'm surprised at:
1) The button made it from the Chute to the Scoring Platform; and 2) The Ref's saw the button under the stack. In any case, the rule is the rule. Nothing can be between the Tote and the Platform except for another Tote. |
Re: In b4 buttongate
|
Re: In b4 buttongate
Quote:
|
Re: In b4 buttongate
I would have thought they'd get a foul for putting something other than a tote through the human feeder chute.
|
Re: In b4 buttongate
Quote:
|
Re: In b4 buttongate
Quote:
Luckily, there were no fouls! I think we were all way too confused and surprised to think about it, I know I was :p |
Re: In b4 buttongate
1 Attachment(s)
THE button
|
Re: In b4 buttongate
I am the human player from 4564. The button was one of the funniest things that has happened to me in FIRST. I thought you may want to see the button! I am #buttongate
|
Re: In b4 buttongate
Also to note, this was a replay of match 1. The first match was stopped due to all of the lights going out in the middle of that match. This was followed by a 142-141 finish in finals match two. Such a fun, entertaining way to end an event.
|
Re: In b4 buttongate
For what it is worth, Counting the stack would not have changed the outcome. Instead of 155 to 84 it would have been 155 to 126. Congratulations Team 133, BERT, 213, The Dirty Birds and 501, The Power Knights! The 142-141 finale was awesome! This event had a plethora of high scores and terrific robots. I am looking forward to seeing and working with all the teams again at WPI for the District Championship.
|
Re: In b4 buttongate
Surprised that Chief Delphi isn't exploding over this right now.
|
Re: In b4 buttongate
Quote:
|
Re: In b4 buttongate
Quote:
|
Re: In b4 buttongate
Quote:
If I were a ref (which I'm not) the deciding factor for me would be if I could easily dislodge that button from the stack - i.e. is it just there on the edge of a TOTE, or is it really wedged in there? If the former, it scores - there is unambiguously no support being provided by the button. If the latter, then it doesn't score. From the picture, it could go either way. Of course, I defer to the ref at the match for the ruling, which was that it didn't score. |
Re: In b4 buttongate
It should be noted that Frank Merrick was field side while the refs were discussing so the refs weren't coming to their own conclusion and they have to follow the rules put before them even if it might seem silly. The refs at UNH were extremely consistent with upholding the rule book including clarifying the rules when "can wars" started dictating who placed robots first.
While an honest mistake the rules are the rules and at the end of the day the decision had no bearing on the outcome of the match. Thanks to 58, 126, 133, 213, 501, and 4564 for making for an exciting finals match up. |
Re: In b4 buttongate
Quote:
|
Re: In b4 buttongate
Quote:
|
Re: In b4 buttongate
Quote:
|
Re: In b4 buttongate
Quote:
I think it was primarily meant to acknowledge that litter would be strewn all over the field and that one of the challenges would be to make sure the tote was not stacked on top of litter (allowing this could also be a safety issue if the stack became unstable). A button that accidentally fell down, though? That seems like bureaucratic ruling to me. A lot of the rules in the handbook say "The INTENT of this rule is to ___ while making exceptions for ___", this could have been one of them. |
Re: In b4 buttongate
Quote:
|
Re: In b4 buttongate
Quote:
I'm just saying that the rule could have been worded differently. For example, G25 says "ROBOTS may not intentionally detach or leave parts on the FIELD" but then the blue box clarifies that "G25 is not intended to penalize ROBOTS that encounter accidental breakage (e.g. a failed MECHANISM that falls off), as those actions are not intentional." They could have worded the "fully supported" rule differently. Granted it would probably be futile trying to define what was OK and what was not, hence the all-sweeping rule. |
Re: In b4 buttongate
Quote:
Overly concerned with procedure at the expense of efficiency or common sense. |
Re: In b4 buttongate
Quote:
Quote:
Thanks to everyone who participated and congratulations to all the teams. Too bad about the button thing, that was unfortunate, but as bob mentioned, it wouldn't have changed the outcome of that match. The UNH District was a HOOT! |
Re: In b4 buttongate
Interesting.
It's a sad thing to occur but the rules are very clear on this and I think the call was fair. It didn't determine the outcome of the match so there shouldn't be too much drama over it, thanks for sharing. |
Re: In b4 buttongate
Quote:
On to WPI....Think DIRTY (Dirty Birds) |
Re: In b4 buttongate
Thanks to everyone who played in the finals and there keeping cool on both alliances. Thanks to Bert for assembling the alliance of misfit robots 501 and 213.
Also, a big thanks to Abby! She was the head ref who had to deal with this odd circumstance. As, a previous ref, I can assure you none of the training/testing accounted for this kind of thing. |
Re: In b4 buttongate
A big thank you to Teams 213 and 501 for being such great alliance partners!
Our scouting team did an amazing job in identifying the teams that would compliment our strengths and weaknesses perfectly to build a powerhouse alliance. Who would have thought that the #6 alliance captain picking the #30 seed and #33 seed would be a force to be reckoned with! It just goes to show that you can't trust the rankings and having good scouting is key. We had a blast at UNH and can't wait to see you guys at WPI! |
| All times are GMT -5. The time now is 18:25. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi