-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STAR test cases #2
Comments
Thanks for the link, I think this will be very useful. I just added a PR with the basic unittest framework. Our STAR implementation is pretty basic at the moment, no ties or anything, so I'm interested in reading through what you've done. There's some tie breaker documentation here and we have some javascript implementations here |
These tiebreakers get confusing fast. If you try to write out tests for every possible scenario, the scenarios keep branching off with ties within ties within ties. For example:
Totals are A=3, B=1, C=1, so A is a finalist, but B and C are tied. So find pairwise winner between B and C. 1 voter prefers B>C, one prefers C>B, so they're tied, no pairwise winner. "If needed you can also compare them each head-to-head against the highest scoring candidate." So if 2 voters prefer A>B, while 1 prefers A>C, then C goes to the runoff? (And then A wins.)
Totals are A=4, B=1, C=1, D=1, so A is a finalist, but B, C, D are tied. So try to find pairwise winner between B, C, and D. There is none, it's a tie. So compare with highest scoring candidate. 3 A>B So C and D are tied? Pick one randomly for the runoff? (Then A wins regardless.) Also minimax has three different interpretations when you allow equal rankings. https://en.wikipedia.org/wiki/Minimax_Condorcet_method#Variants_of_the_pairwise_score |
The link above should cover these scenarios. In your second case with a multi candidate tie, A is the Condorcet winner and C and D tie for runner up. I don't think there's a need to break the tie further. In other cases with true ties it's ok to just report that the result is a tie. |
But the instructions say "Take each candidate and compare them head-to-head with the others in the tie." So it doesn't matter that A is Condorcet winner for deciding the 2nd candidate who goes to the runoff. It needs to select one of them, if only to display who it was. |
OK I made a big table and found there are 12 possible scenarios with the "minimum tiebreaker" method, and made a test case for each (rows are voters, columns are candidates A B C, numbers are scores)
|
This has been a rabbit hole that we've been working on for a while. There's a few people deep diving on different tie breaker protocol including the minimax algorithm specified in the site. We're currently looking into an even simpler protocol based on the Ranked Robin voting method. For this reason I'd caution against putting too much more work into this rabbit hole. In the meantime we've updated the instructions to just
So in scenarios where there are multiple candidates who tie in the score round it will be labeled as a true tie and up to whoever is running the election to break it with their preferred tie breaking protocol. I'm hoping to get some of those protocols added to this repo so there are multiple options available. |
Wrote this in the slack but I'll copy it here. The 'simple' scenarios (i.e. 1, 2, 3, 4, or the unlisted scenario of one highest score, exactly two tied for second, with one preferred over the other) are already going to be rare, and the resolutions @mikefranze put above work great. Any of the other scenarios ("True Tie") would be so astronomically rare I don't think it's worth any of the added complexity to specify other protocols like Ranked Robin or 'Minimax' etc. etc. Even just introducing the concept of a Condorcet winner feels like an avoidable cognitive burden for voters. I agree that in general it is nice to elect a Condorcet winner, but in this kind of edge case I really don't think it matters. If it is necessary to specify exactly what to do in the case of a "True Tie," I would strongly recommend something more straightforward. Here are some examples:
And so on. |
This is still the same 12 scenarios I've described above, no? Or are three-way ties not included in "ties"? |
That's numbers 5 and 6
Simplicity is nice. I still haven't finished my STAR implementation because of handling the "three or more tied for highest-scoring" cases, where I need to find 2nd-place Condorcet winners, etc. |
Sorry for all the questions, I'm just trying to make sure my implementation is 100% correct.
So in this 3-voter, 4-candidate scenario
What would the "minimal tiebreaker" do? This is considered a "True Tie" because there is no Condorcet winner, so choose between A, B, C, D randomly? (Even though A wins more matchups over the alternatives?) And in this
All candidates get the same score, and there is no Condorcet winner, but you still need to identify the Smith Set(?) and choose randomly from within that set {A, B, C} because they all beat D pairwise? (Which is non-trivial?) |
I started writing a STAR implementation but got slowed down by the tie-breaking complexity. Here are my work in progress implementation and unit tests in case they're useful. (Some of the WDS examples are not correct, and he never responded to my emails.)
I'd like more examples of corner cases if you know of a list. Real-world election ballot lists would be good, too.
The text was updated successfully, but these errors were encountered: