![]() |
FRC Blogged - Doing the Right Thing
Taken from the FRC Blog, 3/26/13: http://www.usfirst.org/roboticsprogr...he-right-thing
Quote:
|
Re: FRC Blogged - Doing the Right Thing
Hats off to both alliances on this one. That must have been a very tough call and I'm glad everything went ok.
|
Re: FRC Blogged - Doing the Right Thing
What? Wait a minute? Since when did we start deciding tied elimination matches based on obscure rules, rather than playing a tie breaking match?
Okay... I know the rule must have been changed at some point and I must have missed that in the rules book (and likely a lengthy discussion on CD)... but that is the part of this blog post that really bugs me. Bring back "Finals Match 4"! Sorry to hear how the rest of it went down, but at least everyone agrees that an alliance won by outscoring the other, even if it took a couple tries to get it right. That's better than deciding such a close final based upon a penalty. Tie-breakers! Tie-breakers! Settle the match the old fashioned way, where someone actually wins on the field! Jason |
Re: FRC Blogged - Doing the Right Thing
Quote:
Edit: Section 5.4.4 of the 2012 game manual does describe the same tie breaker system in place now. Can't say for the beginning of this year. |
Re: FRC Blogged - Doing the Right Thing
Quote:
|
Quote:
I remember IRI 2010 and it got to a point when I didn't care who won. I just wanted it to be over. |
Re: FRC Blogged - Doing the Right Thing
Quote:
I can't deny the efficiency of settling an elimination series this way, but really... in all the FRC, FTC and VRC events that I've attended that have gone "over time", I don't think the "tie breaker match" has ever been the main cause. No doubt it happened at IRI once, but it seems weird that an anomaly at an off-season event should impact 'real' FRC events. Anyway, thanks for the update... and I should really be focusing on the GP shown last weekend, as described in the blog post... but I will be cheerfully grumpy for the next while about how "it was better in the old days when we settled ties the honorable way!" Jason |
Re: FRC Blogged - Doing the Right Thing
Quote:
There is a fairness aspect to it as well. Once again going to the WPI quarterfinals, the other two alliances both had essentially an hour+ of downtime waiting for their opponents to be decided. Meanwhile, the #2 seed had to go straight into semis after a grueling 3 extra matches, the last of which with only the standard 6 minute break in between. Their first semifinal was a tie as well, leading to another two back-to-back matches before they made it through to finals. 1735's drive motors overheated in the finals after having played 9 nearly consecutive matches. When all was said and done, 1735 and their partners 2370 and 663 played 11 matches in eliminations, only one less than they did through qualifiers. This was an extreme example, but it and other similar episodes around the country did prompt the tiebreaker rules to come into play for the sake of the teams, as well as the audience and volunteers. I guarantee that alliance would have performed significantly better in the finals had their robot and driveteam not run through the equivalent of a second regional in just 3 hours. While the games since have not had the propensity for ties that 2010 did, it has come up a few times (including Galileo Semifinals in 2011). I agree with you that it's much more exciting (in general) to play out ties...but after having been through WPI 2010, I understand the necessity of having tiebreakers in place. |
Re: FRC Blogged - Doing the Right Thing
Quote:
In 2011, ties occurred in ~4% of qualification matches in 2012, ties occurred in ~3% of qualification matches So far in 2013, ties have occurred in ~1% of qualification matches |
Re: FRC Blogged - Doing the Right Thing
Quote:
I'll admit that five tiebreakers is a bit excessive, and could be seen as being responsible for delaying the completion of the event, however there were a total of 22 elimination matches played, including the tiebreakers. An event should be prepared for 21 elimination matches, assuming each of the seven series goes to three matches. So technically, even with all those extra tiebreakers, the event would have gone one match... six minutes... beyond what would be achieved in a "longest case" scenario using the current rules. I submit that based on the 2010 elimination rounds that tiebreakers are an anomaly and are rarely (if ever) the root cause for an event running beyond time limits. I'll admit that there needs to be something in the rules to allow events to finish at a reasonable time, however I'll also submit that saving six minutes is hardly worth giving up the "tiebreaker" match. And while I'm happy to admit that this totally falls into the category of "first world problems", I'll argue that we should settle ties on the field... in the finals at the very least! Jason P.S. at the other two events that had tiebreakers, they both ocurred in the finals... the perfect time! Oh, yeah... full disclosure... I'm a bit of a hockey fan, and playoff games aren't considered "epic" until at least the third overtime period, so there might be a bit of a pre-existing bias. |
Perhaps open up one tiebreaker match. If no team has two wins by the third match the team with more wins takes the set. If the number of wins is equal play a fourth match. If the fourth match is a tie use the tiebreakers. It allows for a tiebreaker match without the possibility of dragging things out forever.
|
Re: FRC Blogged - Doing the Right Thing
Quote:
|
Re: FRC Blogged - Doing the Right Thing
I might be alone here but I think after what happened it's only fair to let both alliances go to Championship. Yes, one alliance didn't win, but to be given something, and then taking it back just seems wrong. ~400 teams will go to Championship. This is a rare mistake. What's 3 more teams?
|
Re: FRC Blogged - Doing the Right Thing
Quote:
|
Re: FRC Blogged - Doing the Right Thing
Quote:
EDIT: 1,000th Post |
| All times are GMT -5. The time now is 04:59. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi