![]() |
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) |
| 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