V
VoteFair
Wed, May 26, 2021 4:17 PM
I'm getting very interesting results from creating a scatter plot that
shows success rates for Clone Independence (CI) versus Independence of
Irrelevant Alternatives (IIA). Of course these success-rate percentages
convert into failure rates simply by subtracting them from 100.
Specifically the following chart shows the success-rate percentages for
different vote-counting methods using different numbers of candidates.
https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
The numbers "2" and "9" (in the method labels) indicate how many
candidates were used for those data points. The other points along each
line indicate the intermediate candidate counts.
Disclaimer: My software probably still has some bugs. Plus I might have
made mistakes when I pieced together this formally formatted scatter
plot. I'm hoping that your feedback will help me identify any errors.
The Clone Independence (CI) test adds two clone candidates (who are
similar to one of the original candidates) and identifies how often the
winner changes.
Note: This scatter plot does NOT separate CI failures into their
different types: (1) helps the similar candidate, (2) harms the similar
candidate, (3) causes one of the clones to win, or (4) causes some other
candidate to win.
The Independence of Irrelevant Alternatives (IIA) test removes each
non-winning candidate, one at a time, to identify if the winner changes.
If any of these removals causes the winner to change, then the method
fails that IIA test.
Note: The IIA test cannot fail when there are just two candidates
because removing the non-winning candidate always causes the winner to
still win. As a consequence, the scatter-plot points along the right
edge (which have the digit "2) only indicate the success rate for Clone
Independence.
When a set of randomly generated ballots yields a tie -- for winner --
according to the Condorcet-Kemeny method or IRV method or Plurality
method, then that attempted test is ignored for all the methods.
Without these omissions too many tests would yield a "tie" result, which
cannot be meaningfully categorized as either a failure or success.
Ties that occur at earlier stages of a method's computation are resolved
in simple ways if the method does not define a way to resolve such ties.
In particular, when a set of ballots causes IRV to reach a tie in an
earlier elimination round, all those tied candidates are eliminated in
the same round. This is why the IRV method sometimes fails the Clone
Independence test even though IRV would never fail if lower-level ties
were never encountered.
This use of randomly generated ballots often yields tied results and
Condorcet cycles, especially compared to real-life elections where clear
popularity differences are common.
Yet instead of interpreting these results as "unrealistic," I suggest
that these tests be regarded as a kind of "stress test" where the
method's fairness is tested in these challenging test cases.
Specifically, high fairness rates in these challenging cases provides
evidence of greater fairness in less-challenging real elections.
With these considerations in mind, here are some notable results:
-
Approval voting has the lowest success rates for both clone
independence (CI) and IIA. About simulation: To convert from a ranking
ballot to an Approval ballot, the candidates above the halfway
preference level are approved. When there is an odd number of
candidates, the middle candidate gets one-half of an approval vote.
-
Borda count has lower CI (clone) success rates (higher failure rates)
compared to the other methods, except Approval. About simulation: These
simulations assume non-tactical voting, yet in real elections
Borda-count ballots would be marked tactically (using burying, betrayal,
etc. and ranking multiple candidates at the same preference level) to
increase the voter's influence.
-
IRV-BTR -- Instant-runoff voting with bottom-two runoff -- yields
about the same results as IRV. I included this method in hopes that the
results would help Robert in his reform efforts in Burlington. Alas,
unless I've got a bug in the code -- which is very possible -- IRV-BTR
isn't looking better than IRV for these two fairness criteria (CI and IIA).
-
IRV -- Instant Runoff Voting -- becomes more vulnerable to IIA
failures as the number of candidates increases, especially compared to
the other methods (except Approval). This vulnerability might be a
consequence of the method having a zero CI failure rate (when there are
no ties at any level).
-
Plurality voting reverses back to fewer IIA failures as the number of
candidates increases, which is different from the other methods. Also,
plurality voting has a less-predictable pattern compared to the other
methods, which might be because it collects so little preference
information. The need for tactical voting in plurality elections means
that real-life plurality failure rates (for close elections) will be
higher than in these non-tactical simulations. About simulation: The
ballot's single vote goes to the candidate who is ranked highest.
-
The Condorcet-Kemeny method has higher failure rates for Clone
Independence when there are just two or three candidates. The failure
rate decreases when there are more candidates. As a reminder, this
scatter plot does not separate clone-independence failures into their
different kinds of failures, which is important information regarding
whether a method is vulnerable to money-based election tactics.
-
STAR voting -- Score Then Automatic Runoff -- always uses six
preference levels, so only the data point for six candidates
meaningfully matches this method. About simulation: The other data
points for "STAR" voting simulate a STAR-like ballot on which the number
of preference levels matches the number of candidates. Also, these
tests simulate non-tactical ballot marking, but human voters using STAR
voting in a real-life election, especially a US general election, would
use ballot-marking tactics that exploit the method's ability to express
strong preferences.
-
RCIPE -- Ranked Choice Including Pairwise Elimination -- has fewer CI
failures compared to the other methods. About this method: RCIPE is
similar to IRV except that if an elimination round includes a "pairwise
losing candidate" (a.k.a. Condorcet loser) then this candidate is
eliminated instead of the fewest-transferred-votes candidate. When an
elimination round involves a tie, this method resolves the tie using the
IPE counting method.
-
IPE -- Instant Pairwise Elimination -- has the lowest failure rates
compared to the other methods. About this method: IPE eliminates the
candidate who has the highest "opposition" count, where the opposition
count for a candidate is the number of remaining candidates who (on a
ballot) are ranked higher than that candidate, summed across all the
ballots. If there is a tie, it's resolved using the lowest "support"
count, which counts the remaining candidates who are ranked lower than
the specified candidate. Method clarification: This counting method
does not actually re-count the ballots for each elimination round;
instead a calculator and pen and paper can be used with the overall
pairwise-count table to calculate the opposition and support counts
(which change after each elimination).
If someone wants a closer look at the actual numbers used in this
scatter plot, they are at the bottom of this text file:
https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/results_from_generate_random_ballots.txt
Here's a link to the C++ program (which mostly uses the C language
subset) that generates random ballots, supplies these ballots to
separate software where the winners are calculated, and analyzes the
results:
https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/generate_random_ballots.cpp
I hope you agree that these results are very helpful for comparing
vote-counting methods.
For perspective, my interest in CI and IIA failure/success rates is
based on my frustration that money-based tactics are used to manipulate
election results by exploiting CI and IIA failures in ways that achieve
strategic nomination. These money-based tactics include:
-
Financially supporting clones (similar candidates) who split votes
away from a popular reform-minded candidate
-
Removing financial support from clones (similar candidates) who split
votes away from the status-quo-supporting (puppet-like) candidate
-
Possibly supporting distracting (irrelevant) candidates
In contrast, I believe it's more difficult to use money to manipulate an
election by exploiting other kinds of failures such as: monotonicity,
favorite betrayal, later no help/harm, etc. In other words, I believe
these other fairness criteria too often get more attention than they
deserve (under current money-dominant political conditions).
Here's a final note to those of you who are in the academic world. I
invite you to reproduce these results and add other methods and publish
the results. Why is this important? The improvement of Wikipedia
articles about better vote-counting methods requires peer-reviewed
academic articles that meaningfully compare vote-counting methods in
ways that go beyond Wikipedia's simple pass/fail checklist in the
"Comparison of electoral systems" article. Alas, too often that
over-simplistic checklist gets cited as evidence of support for inferior
vote-counting methods.
In other words, flagging vote-counting failures as either zero or
non-zero is primitive. We need more measurements of HOW OFTEN the
non-zero failures occur.
Richard Fobes
"The VoteFair guy"
I'm getting very interesting results from creating a scatter plot that
shows success rates for Clone Independence (CI) versus Independence of
Irrelevant Alternatives (IIA). Of course these success-rate percentages
convert into failure rates simply by subtracting them from 100.
Specifically the following chart shows the success-rate percentages for
different vote-counting methods using different numbers of candidates.
https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
The numbers "2" and "9" (in the method labels) indicate how many
candidates were used for those data points. The other points along each
line indicate the intermediate candidate counts.
Disclaimer: My software probably still has some bugs. Plus I might have
made mistakes when I pieced together this formally formatted scatter
plot. I'm hoping that your feedback will help me identify any errors.
The Clone Independence (CI) test adds two clone candidates (who are
similar to one of the original candidates) and identifies how often the
winner changes.
Note: This scatter plot does NOT separate CI failures into their
different types: (1) helps the similar candidate, (2) harms the similar
candidate, (3) causes one of the clones to win, or (4) causes some other
candidate to win.
The Independence of Irrelevant Alternatives (IIA) test removes each
non-winning candidate, one at a time, to identify if the winner changes.
If any of these removals causes the winner to change, then the method
fails that IIA test.
Note: The IIA test cannot fail when there are just two candidates
because removing the non-winning candidate always causes the winner to
still win. As a consequence, the scatter-plot points along the right
edge (which have the digit "2) only indicate the success rate for Clone
Independence.
When a set of randomly generated ballots yields a tie -- for winner --
according to the Condorcet-Kemeny method or IRV method or Plurality
method, then that attempted test is ignored for all the methods.
Without these omissions too many tests would yield a "tie" result, which
cannot be meaningfully categorized as either a failure or success.
Ties that occur at earlier stages of a method's computation are resolved
in simple ways if the method does not define a way to resolve such ties.
In particular, when a set of ballots causes IRV to reach a tie in an
earlier elimination round, all those tied candidates are eliminated in
the same round. This is why the IRV method sometimes fails the Clone
Independence test even though IRV would never fail if lower-level ties
were never encountered.
This use of randomly generated ballots often yields tied results and
Condorcet cycles, especially compared to real-life elections where clear
popularity differences are common.
Yet instead of interpreting these results as "unrealistic," I suggest
that these tests be regarded as a kind of "stress test" where the
method's fairness is tested in these challenging test cases.
Specifically, high fairness rates in these challenging cases provides
evidence of greater fairness in less-challenging real elections.
With these considerations in mind, here are some notable results:
* Approval voting has the lowest success rates for both clone
independence (CI) and IIA. About simulation: To convert from a ranking
ballot to an Approval ballot, the candidates above the halfway
preference level are approved. When there is an odd number of
candidates, the middle candidate gets one-half of an approval vote.
* Borda count has lower CI (clone) success rates (higher failure rates)
compared to the other methods, except Approval. About simulation: These
simulations assume non-tactical voting, yet in real elections
Borda-count ballots would be marked tactically (using burying, betrayal,
etc. and ranking multiple candidates at the same preference level) to
increase the voter's influence.
* IRV-BTR -- Instant-runoff voting with bottom-two runoff -- yields
about the same results as IRV. I included this method in hopes that the
results would help Robert in his reform efforts in Burlington. Alas,
unless I've got a bug in the code -- which is very possible -- IRV-BTR
isn't looking better than IRV for these two fairness criteria (CI and IIA).
* IRV -- Instant Runoff Voting -- becomes more vulnerable to IIA
failures as the number of candidates increases, especially compared to
the other methods (except Approval). This vulnerability might be a
consequence of the method having a zero CI failure rate (when there are
no ties at any level).
* Plurality voting reverses back to fewer IIA failures as the number of
candidates increases, which is different from the other methods. Also,
plurality voting has a less-predictable pattern compared to the other
methods, which might be because it collects so little preference
information. The need for tactical voting in plurality elections means
that real-life plurality failure rates (for close elections) will be
higher than in these non-tactical simulations. About simulation: The
ballot's single vote goes to the candidate who is ranked highest.
* The Condorcet-Kemeny method has higher failure rates for Clone
Independence when there are just two or three candidates. The failure
rate decreases when there are more candidates. As a reminder, this
scatter plot does not separate clone-independence failures into their
different kinds of failures, which is important information regarding
whether a method is vulnerable to money-based election tactics.
* STAR voting -- Score Then Automatic Runoff -- always uses six
preference levels, so only the data point for six candidates
meaningfully matches this method. About simulation: The other data
points for "STAR" voting simulate a STAR-like ballot on which the number
of preference levels matches the number of candidates. Also, these
tests simulate non-tactical ballot marking, but human voters using STAR
voting in a real-life election, especially a US general election, would
use ballot-marking tactics that exploit the method's ability to express
strong preferences.
* RCIPE -- Ranked Choice Including Pairwise Elimination -- has fewer CI
failures compared to the other methods. About this method: RCIPE is
similar to IRV except that if an elimination round includes a "pairwise
losing candidate" (a.k.a. Condorcet loser) then this candidate is
eliminated instead of the fewest-transferred-votes candidate. When an
elimination round involves a tie, this method resolves the tie using the
IPE counting method.
* IPE -- Instant Pairwise Elimination -- has the lowest failure rates
compared to the other methods. About this method: IPE eliminates the
candidate who has the highest "opposition" count, where the opposition
count for a candidate is the number of remaining candidates who (on a
ballot) are ranked higher than that candidate, summed across all the
ballots. If there is a tie, it's resolved using the lowest "support"
count, which counts the remaining candidates who are ranked lower than
the specified candidate. Method clarification: This counting method
does not actually re-count the ballots for each elimination round;
instead a calculator and pen and paper can be used with the overall
pairwise-count table to calculate the opposition and support counts
(which change after each elimination).
If someone wants a closer look at the actual numbers used in this
scatter plot, they are at the bottom of this text file:
https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/results_from_generate_random_ballots.txt
Here's a link to the C++ program (which mostly uses the C language
subset) that generates random ballots, supplies these ballots to
separate software where the winners are calculated, and analyzes the
results:
https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/generate_random_ballots.cpp
I hope you agree that these results are very helpful for comparing
vote-counting methods.
For perspective, my interest in CI and IIA failure/success rates is
based on my frustration that money-based tactics are used to manipulate
election results by exploiting CI and IIA failures in ways that achieve
strategic nomination. These money-based tactics include:
* Financially supporting clones (similar candidates) who split votes
away from a popular reform-minded candidate
* Removing financial support from clones (similar candidates) who split
votes away from the status-quo-supporting (puppet-like) candidate
* Possibly supporting distracting (irrelevant) candidates
In contrast, I believe it's more difficult to use money to manipulate an
election by exploiting other kinds of failures such as: monotonicity,
favorite betrayal, later no help/harm, etc. In other words, I believe
these other fairness criteria too often get more attention than they
deserve (under current money-dominant political conditions).
Here's a final note to those of you who are in the academic world. I
invite you to reproduce these results and add other methods and publish
the results. Why is this important? The improvement of Wikipedia
articles about better vote-counting methods requires peer-reviewed
academic articles that meaningfully compare vote-counting methods in
ways that go beyond Wikipedia's simple pass/fail checklist in the
"Comparison of electoral systems" article. Alas, too often that
over-simplistic checklist gets cited as evidence of support for inferior
vote-counting methods.
In other words, flagging vote-counting failures as either zero or
non-zero is primitive. We need more measurements of HOW OFTEN the
non-zero failures occur.
Richard Fobes
"The VoteFair guy"
RB
robert bristow-johnson
Wed, May 26, 2021 5:00 PM
On 05/26/2021 12:17 PM VoteFair electionmethods@votefair.org wrote:
I'm getting very interesting results from creating a scatter plot that
shows success rates for Clone Independence (CI) versus Independence of
Irrelevant Alternatives (IIA). Of course these success-rate percentages
convert into failure rates simply by subtracting them from 100.
Specifically the following chart shows the success-rate percentages for
different vote-counting methods using different numbers of candidates.
https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
- IRV-BTR -- Instant-runoff voting with bottom-two runoff -- yields
about the same results as IRV. I included this method in hopes that the
results would help Robert in his reform efforts in Burlington. Alas,
unless I've got a bug in the code -- which is very possible -- IRV-BTR
isn't looking better than IRV for these two fairness criteria (CI and IIA).
of course the only difference in behavior will be when there is a case like Burlington where a Condorcet winner exists but does not make into the final round with Hare IRV. i dunno the details of your simulation but i might wonder how many (as a percent) times that happens and how many times a cycle occurred.
my sole selling point (maybe this becomes 4 or 5 selling points as i have enumerated in my paper at https://drive.google.com/file/d/14assN41UL7Mib9PpwsjM63ZT17k9admC/view ) is that plain-language advantages of RCV that are presented to the public are going to be better attained with a Condorcet method. but most people following RCV don't know what that is. so i translate "satisfy Condorcet criterion" to "Majority Rule" and i translate "satisfy IIA" to "eliminate the Spoiler Effect" and the only voting tactic i worry about is "compromising" because that is the most common problem and is directly related to the spoiler effect. and i am also trying to appeal to the Precinct Summability issue because it relates directly to transparency in elections and decentralization of the tallying of ballots. that speaks to election integrity and puts up another bulwark against hacking and corruption in elections.
in other words, i want to make RCV live up to its promise.
Here is a Vermont update: Because, because city charter changes require state legislative approval and because of heavy load on the legislature regarding covid and the economic consequences, the Gov Ops committee was too busy to deal with the RCV charter change even though it passed the voters of Burlington with a 64% majority. Some legislators read my paper and it has influenced them. It is not dead, but it is in hibernation until 2022. Then we're gonna have a big fight and, again, I will be asking for help in advocacy. https://vtdigger.org/2021/05/21/burlington-charter-change-package-stalls-in-committee/
BTW, i got involved in a Ranked-Pairs advocacy group centered mostly in Madison Wisconsin, but they got Nicolas Tideman in it. People here might remember that before I was told about BTR-STV (which is the name I am giving it), that RP with margins was my fav Condorcet method (only because I saw it as simpler than Schulze and easier to sell). But BTR-STV is even simpler and even easier to sell. And I can compare it directly to Hare STV.
My hope is that when the "big presentation" happens at the Statehouse in 2022, that I might be able to get both Nicolas and Markus and Richard and some others here to testify (via Zoom) before the committee. I need to fight off the accusation that I am a constituency of 1 and that nobody else cares about this "detail".
Thank you to all for your help and encouragement. That FairVote train is rolling with a lot of momentum.
--
r b-j rbj@audioimagination.com
"Imagination is more important than knowledge."
> On 05/26/2021 12:17 PM VoteFair <electionmethods@votefair.org> wrote:
>
>
> I'm getting very interesting results from creating a scatter plot that
> shows success rates for Clone Independence (CI) versus Independence of
> Irrelevant Alternatives (IIA). Of course these success-rate percentages
> convert into failure rates simply by subtracting them from 100.
>
> Specifically the following chart shows the success-rate percentages for
> different vote-counting methods using different numbers of candidates.
>
> https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
>
...
>
> * IRV-BTR -- Instant-runoff voting with bottom-two runoff -- yields
> about the same results as IRV. I included this method in hopes that the
> results would help Robert in his reform efforts in Burlington. Alas,
> unless I've got a bug in the code -- which is very possible -- IRV-BTR
> isn't looking better than IRV for these two fairness criteria (CI and IIA).
>
of course the only difference in behavior will be when there is a case like Burlington where a Condorcet winner exists but does not make into the final round with Hare IRV. i dunno the details of your simulation but i might wonder how many (as a percent) times that happens and how many times a cycle occurred.
my sole selling point (maybe this becomes 4 or 5 selling points as i have enumerated in my paper at https://drive.google.com/file/d/14assN41UL7Mib9PpwsjM63ZT17k9admC/view ) is that plain-language advantages of RCV that are presented to the public are going to be better attained with a Condorcet method. but most people following RCV don't know what that is. so i translate "satisfy Condorcet criterion" to "Majority Rule" and i translate "satisfy IIA" to "eliminate the Spoiler Effect" and the only voting tactic i worry about is "compromising" because that is the most common problem and is directly related to the spoiler effect. and i am also trying to appeal to the Precinct Summability issue because it relates directly to transparency in elections and decentralization of the tallying of ballots. that speaks to election integrity and puts up another bulwark against hacking and corruption in elections.
in other words, i want to make RCV live up to its promise.
Here is a Vermont update: Because, because city charter changes require state legislative approval and because of heavy load on the legislature regarding covid and the economic consequences, the Gov Ops committee was too busy to deal with the RCV charter change even though it passed the voters of Burlington with a 64% majority. Some legislators read my paper and it has influenced them. It is not dead, but it is in hibernation until 2022. Then we're gonna have a big fight and, again, I will be asking for help in advocacy. https://vtdigger.org/2021/05/21/burlington-charter-change-package-stalls-in-committee/
BTW, i got involved in a Ranked-Pairs advocacy group centered mostly in Madison Wisconsin, but they got Nicolas Tideman in it. People here might remember that before I was told about BTR-STV (which is the name I am giving it), that RP with margins was my fav Condorcet method (only because I saw it as simpler than Schulze and easier to sell). But BTR-STV is even simpler and even easier to sell. And I can compare it directly to Hare STV.
My hope is that when the "big presentation" happens at the Statehouse in 2022, that I might be able to get *both* Nicolas and Markus and Richard and some others here to testify (via Zoom) before the committee. I need to fight off the accusation that I am a constituency of 1 and that nobody else cares about this "detail".
Thank you to all for your help and encouragement. That FairVote train is rolling with a lot of momentum.
--
r b-j rbj@audioimagination.com
"Imagination is more important than knowledge."
V
VoteFair
Sun, Jun 20, 2021 12:41 AM
I have updated the scatter plot that charts Clone Independence and IIA
(Independence of Irrelevant Alternatives) for various methods. The
scatter plot is (still) at:
https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
Here are the most important changes to the software and chart:
-
The Clone Independence test now categorizes the case of a clone
candidate displacing the similar candidate as a success, not a failure.
This interpretation was requested on the r/EndFPTP subreddit, and it
makes sense to me. The other three kinds of CI failures continue to be
categorized as failures. This means that when the original candidate
who is similar to the clones (is there a name for this candidate?) wins
without the clones, and then loses to one of the clones (when they are
added), that displacement is not regarded as a failure of clone
independence. The wording in the Wikipedia article on Clone
Independence implies that such displacements are failures, so that's the
interpretation I originally used. I'm not suggesting that the Wikipedia
wording is incorrect; rather I'm suggesting that when measuring CI
success/failure rates it's important to also measure how often each kind
of CI failure occurs (which is what I wrote earlier), and because this
scatter plot is intended to be a meaningful summary of the measurements.
-
Because of this change, the success rates for the Condorcet-Kemeny
method and the Borda count method are much higher.
-
The success rates for the Condorcet-Kemeny method are now very similar
to the Instant Pairwise Elimination (IPE) success rates. This is not
surprising to me because I designed opposition counts -- which are used
in the IPE method -- as a quick way to estimate Condorcet-Kemeny
results. (I had been surprised by the earlier results.)
-
The Instant Pairwise Elimination (IPE) method calculations now
correctly eliminate Condorcet losers when they occur. The previous
calculations just used the pairwise opposition counts. The resulting CI
and IIA measurements remain about the same. (Typically when there is a
Condorcet loser, the Condorcet loser has an opposition count that is
very close to the highest opposition count.)
-
I've eliminated the Approval method from the plot. As someone pointed
out on r/EndFPTP, converting ranked ballots into Approval ballots is not
meaningful. This is especially true for these tests because my counting
software is separate from the ballot-generation software, so the clone
candidates often do not get the same approval rating as the original
similar candidate.
-
Minor change: Now that the Approval results are gone, the scale starts
at 50 percent compliance.
Additional details are in the software, which is on Github here:
https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/generate_random_ballots.cpp
As a reminder (and because someone on Reddit asked), I chose CI and IIA
because they measure vulnerability to strategic nomination, which is
easily exploited through the control of campaign contributions.
Richard Fobes
On 5/26/2021 9:17 AM, VoteFair wrote:
I'm getting very interesting results from creating a scatter plot that
shows success rates for Clone Independence (CI) versus Independence of
Irrelevant Alternatives (IIA). Of course these success-rate percentages
convert into failure rates simply by subtracting them from 100.
Specifically the following chart shows the success-rate percentages for
different vote-counting methods using different numbers of candidates.
https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
The numbers "2" and "9" (in the method labels) indicate how many
candidates were used for those data points. The other points along each
line indicate the intermediate candidate counts.
Disclaimer: My software probably still has some bugs. Plus I might have
made mistakes when I pieced together this formally formatted scatter
plot. I'm hoping that your feedback will help me identify any errors.
The Clone Independence (CI) test adds two clone candidates (who are
similar to one of the original candidates) and identifies how often the
winner changes.
Note: This scatter plot does NOT separate CI failures into their
different types: (1) helps the similar candidate, (2) harms the similar
candidate, (3) causes one of the clones to win, or (4) causes some other
candidate to win.
The Independence of Irrelevant Alternatives (IIA) test removes each
non-winning candidate, one at a time, to identify if the winner changes.
If any of these removals causes the winner to change, then the method
fails that IIA test.
Note: The IIA test cannot fail when there are just two candidates
because removing the non-winning candidate always causes the winner to
still win. As a consequence, the scatter-plot points along the right
edge (which have the digit "2) only indicate the success rate for Clone
Independence.
When a set of randomly generated ballots yields a tie -- for winner --
according to the Condorcet-Kemeny method or IRV method or Plurality
method, then that attempted test is ignored for all the methods. Without
these omissions too many tests would yield a "tie" result, which cannot
be meaningfully categorized as either a failure or success.
Ties that occur at earlier stages of a method's computation are resolved
in simple ways if the method does not define a way to resolve such ties.
In particular, when a set of ballots causes IRV to reach a tie in an
earlier elimination round, all those tied candidates are eliminated in
the same round. This is why the IRV method sometimes fails the Clone
Independence test even though IRV would never fail if lower-level ties
were never encountered.
This use of randomly generated ballots often yields tied results and
Condorcet cycles, especially compared to real-life elections where clear
popularity differences are common.
Yet instead of interpreting these results as "unrealistic," I suggest
that these tests be regarded as a kind of "stress test" where the
method's fairness is tested in these challenging test cases.
Specifically, high fairness rates in these challenging cases provides
evidence of greater fairness in less-challenging real elections.
With these considerations in mind, here are some notable results:
-
Approval voting has the lowest success rates for both clone
independence (CI) and IIA. About simulation: To convert from a ranking
ballot to an Approval ballot, the candidates above the halfway
preference level are approved. When there is an odd number of
candidates, the middle candidate gets one-half of an approval vote.
-
Borda count has lower CI (clone) success rates (higher failure rates)
compared to the other methods, except Approval. About simulation: These
simulations assume non-tactical voting, yet in real elections
Borda-count ballots would be marked tactically (using burying, betrayal,
etc. and ranking multiple candidates at the same preference level) to
increase the voter's influence.
-
IRV-BTR -- Instant-runoff voting with bottom-two runoff -- yields
about the same results as IRV. I included this method in hopes that the
results would help Robert in his reform efforts in Burlington. Alas,
unless I've got a bug in the code -- which is very possible -- IRV-BTR
isn't looking better than IRV for these two fairness criteria (CI and IIA).
-
IRV -- Instant Runoff Voting -- becomes more vulnerable to IIA
failures as the number of candidates increases, especially compared to
the other methods (except Approval). This vulnerability might be a
consequence of the method having a zero CI failure rate (when there are
no ties at any level).
-
Plurality voting reverses back to fewer IIA failures as the number of
candidates increases, which is different from the other methods. Also,
plurality voting has a less-predictable pattern compared to the other
methods, which might be because it collects so little preference
information. The need for tactical voting in plurality elections means
that real-life plurality failure rates (for close elections) will be
higher than in these non-tactical simulations. About simulation: The
ballot's single vote goes to the candidate who is ranked highest.
-
The Condorcet-Kemeny method has higher failure rates for Clone
Independence when there are just two or three candidates. The failure
rate decreases when there are more candidates. As a reminder, this
scatter plot does not separate clone-independence failures into their
different kinds of failures, which is important information regarding
whether a method is vulnerable to money-based election tactics.
-
STAR voting -- Score Then Automatic Runoff -- always uses six
preference levels, so only the data point for six candidates
meaningfully matches this method. About simulation: The other data
points for "STAR" voting simulate a STAR-like ballot on which the number
of preference levels matches the number of candidates. Also, these
tests simulate non-tactical ballot marking, but human voters using STAR
voting in a real-life election, especially a US general election, would
use ballot-marking tactics that exploit the method's ability to express
strong preferences.
-
RCIPE -- Ranked Choice Including Pairwise Elimination -- has fewer CI
failures compared to the other methods. About this method: RCIPE is
similar to IRV except that if an elimination round includes a "pairwise
losing candidate" (a.k.a. Condorcet loser) then this candidate is
eliminated instead of the fewest-transferred-votes candidate. When an
elimination round involves a tie, this method resolves the tie using the
IPE counting method.
-
IPE -- Instant Pairwise Elimination -- has the lowest failure rates
compared to the other methods. About this method: IPE eliminates the
candidate who has the highest "opposition" count, where the opposition
count for a candidate is the number of remaining candidates who (on a
ballot) are ranked higher than that candidate, summed across all the
ballots. If there is a tie, it's resolved using the lowest "support"
count, which counts the remaining candidates who are ranked lower than
the specified candidate. Method clarification: This counting method
does not actually re-count the ballots for each elimination round;
instead a calculator and pen and paper can be used with the overall
pairwise-count table to calculate the opposition and support counts
(which change after each elimination).
If someone wants a closer look at the actual numbers used in this
scatter plot, they are at the bottom of this text file:
https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/results_from_generate_random_ballots.txt
Here's a link to the C++ program (which mostly uses the C language
subset) that generates random ballots, supplies these ballots to
separate software where the winners are calculated, and analyzes the
results:
https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/generate_random_ballots.cpp
I hope you agree that these results are very helpful for comparing
vote-counting methods.
For perspective, my interest in CI and IIA failure/success rates is
based on my frustration that money-based tactics are used to manipulate
election results by exploiting CI and IIA failures in ways that achieve
strategic nomination. These money-based tactics include:
-
Financially supporting clones (similar candidates) who split votes
away from a popular reform-minded candidate
-
Removing financial support from clones (similar candidates) who split
votes away from the status-quo-supporting (puppet-like) candidate
-
Possibly supporting distracting (irrelevant) candidates
In contrast, I believe it's more difficult to use money to manipulate an
election by exploiting other kinds of failures such as: monotonicity,
favorite betrayal, later no help/harm, etc. In other words, I believe
these other fairness criteria too often get more attention than they
deserve (under current money-dominant political conditions).
Here's a final note to those of you who are in the academic world. I
invite you to reproduce these results and add other methods and publish
the results. Why is this important? The improvement of Wikipedia
articles about better vote-counting methods requires peer-reviewed
academic articles that meaningfully compare vote-counting methods in
ways that go beyond Wikipedia's simple pass/fail checklist in the
"Comparison of electoral systems" article. Alas, too often that
over-simplistic checklist gets cited as evidence of support for inferior
vote-counting methods.
In other words, flagging vote-counting failures as either zero or
non-zero is primitive. We need more measurements of HOW OFTEN the
non-zero failures occur.
Richard Fobes
"The VoteFair guy"
Election-Methods mailing list - see https://electorama.com/em for list info
I have updated the scatter plot that charts Clone Independence and IIA
(Independence of Irrelevant Alternatives) for various methods. The
scatter plot is (still) at:
https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
Here are the most important changes to the software and chart:
* The Clone Independence test now categorizes the case of a clone
candidate displacing the similar candidate as a success, not a failure.
This interpretation was requested on the r/EndFPTP subreddit, and it
makes sense to me. The other three kinds of CI failures continue to be
categorized as failures. This means that when the original candidate
who is similar to the clones (is there a name for this candidate?) wins
without the clones, and then loses to one of the clones (when they are
added), that displacement is not regarded as a failure of clone
independence. The wording in the Wikipedia article on Clone
Independence implies that such displacements are failures, so that's the
interpretation I originally used. I'm not suggesting that the Wikipedia
wording is incorrect; rather I'm suggesting that when measuring CI
success/failure rates it's important to also measure how often each kind
of CI failure occurs (which is what I wrote earlier), and because this
scatter plot is intended to be a meaningful summary of the measurements.
* Because of this change, the success rates for the Condorcet-Kemeny
method and the Borda count method are much higher.
* The success rates for the Condorcet-Kemeny method are now very similar
to the Instant Pairwise Elimination (IPE) success rates. This is not
surprising to me because I designed opposition counts -- which are used
in the IPE method -- as a quick way to estimate Condorcet-Kemeny
results. (I had been surprised by the earlier results.)
* The Instant Pairwise Elimination (IPE) method calculations now
correctly eliminate Condorcet losers when they occur. The previous
calculations just used the pairwise opposition counts. The resulting CI
and IIA measurements remain about the same. (Typically when there is a
Condorcet loser, the Condorcet loser has an opposition count that is
very close to the highest opposition count.)
* I've eliminated the Approval method from the plot. As someone pointed
out on r/EndFPTP, converting ranked ballots into Approval ballots is not
meaningful. This is especially true for these tests because my counting
software is separate from the ballot-generation software, so the clone
candidates often do not get the same approval rating as the original
similar candidate.
* Minor change: Now that the Approval results are gone, the scale starts
at 50 percent compliance.
Additional details are in the software, which is on Github here:
https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/generate_random_ballots.cpp
As a reminder (and because someone on Reddit asked), I chose CI and IIA
because they measure vulnerability to strategic nomination, which is
easily exploited through the control of campaign contributions.
Richard Fobes
On 5/26/2021 9:17 AM, VoteFair wrote:
> I'm getting very interesting results from creating a scatter plot that
> shows success rates for Clone Independence (CI) versus Independence of
> Irrelevant Alternatives (IIA). Of course these success-rate percentages
> convert into failure rates simply by subtracting them from 100.
>
> Specifically the following chart shows the success-rate percentages for
> different vote-counting methods using different numbers of candidates.
>
> https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
>
> The numbers "2" and "9" (in the method labels) indicate how many
> candidates were used for those data points. The other points along each
> line indicate the intermediate candidate counts.
>
> Disclaimer: My software probably still has some bugs. Plus I might have
> made mistakes when I pieced together this formally formatted scatter
> plot. I'm hoping that your feedback will help me identify any errors.
>
> The Clone Independence (CI) test adds two clone candidates (who are
> similar to one of the original candidates) and identifies how often the
> winner changes.
>
> Note: This scatter plot does NOT separate CI failures into their
> different types: (1) helps the similar candidate, (2) harms the similar
> candidate, (3) causes one of the clones to win, or (4) causes some other
> candidate to win.
>
> The Independence of Irrelevant Alternatives (IIA) test removes each
> non-winning candidate, one at a time, to identify if the winner changes.
> If any of these removals causes the winner to change, then the method
> fails that IIA test.
>
> Note: The IIA test cannot fail when there are just two candidates
> because removing the non-winning candidate always causes the winner to
> still win. As a consequence, the scatter-plot points along the right
> edge (which have the digit "2) only indicate the success rate for Clone
> Independence.
>
> When a set of randomly generated ballots yields a tie -- for winner --
> according to the Condorcet-Kemeny method or IRV method or Plurality
> method, then that attempted test is ignored for all the methods. Without
> these omissions too many tests would yield a "tie" result, which cannot
> be meaningfully categorized as either a failure or success.
>
> Ties that occur at earlier stages of a method's computation are resolved
> in simple ways if the method does not define a way to resolve such ties.
> In particular, when a set of ballots causes IRV to reach a tie in an
> earlier elimination round, all those tied candidates are eliminated in
> the same round. This is why the IRV method sometimes fails the Clone
> Independence test even though IRV would never fail if lower-level ties
> were never encountered.
>
> This use of randomly generated ballots often yields tied results and
> Condorcet cycles, especially compared to real-life elections where clear
> popularity differences are common.
>
> Yet instead of interpreting these results as "unrealistic," I suggest
> that these tests be regarded as a kind of "stress test" where the
> method's fairness is tested in these challenging test cases.
> Specifically, high fairness rates in these challenging cases provides
> evidence of greater fairness in less-challenging real elections.
>
> With these considerations in mind, here are some notable results:
>
> * Approval voting has the lowest success rates for both clone
> independence (CI) and IIA. About simulation: To convert from a ranking
> ballot to an Approval ballot, the candidates above the halfway
> preference level are approved. When there is an odd number of
> candidates, the middle candidate gets one-half of an approval vote.
>
> * Borda count has lower CI (clone) success rates (higher failure rates)
> compared to the other methods, except Approval. About simulation: These
> simulations assume non-tactical voting, yet in real elections
> Borda-count ballots would be marked tactically (using burying, betrayal,
> etc. and ranking multiple candidates at the same preference level) to
> increase the voter's influence.
>
> * IRV-BTR -- Instant-runoff voting with bottom-two runoff -- yields
> about the same results as IRV. I included this method in hopes that the
> results would help Robert in his reform efforts in Burlington. Alas,
> unless I've got a bug in the code -- which is very possible -- IRV-BTR
> isn't looking better than IRV for these two fairness criteria (CI and IIA).
>
> * IRV -- Instant Runoff Voting -- becomes more vulnerable to IIA
> failures as the number of candidates increases, especially compared to
> the other methods (except Approval). This vulnerability might be a
> consequence of the method having a zero CI failure rate (when there are
> no ties at any level).
>
> * Plurality voting reverses back to fewer IIA failures as the number of
> candidates increases, which is different from the other methods. Also,
> plurality voting has a less-predictable pattern compared to the other
> methods, which might be because it collects so little preference
> information. The need for tactical voting in plurality elections means
> that real-life plurality failure rates (for close elections) will be
> higher than in these non-tactical simulations. About simulation: The
> ballot's single vote goes to the candidate who is ranked highest.
>
> * The Condorcet-Kemeny method has higher failure rates for Clone
> Independence when there are just two or three candidates. The failure
> rate decreases when there are more candidates. As a reminder, this
> scatter plot does not separate clone-independence failures into their
> different kinds of failures, which is important information regarding
> whether a method is vulnerable to money-based election tactics.
>
> * STAR voting -- Score Then Automatic Runoff -- always uses six
> preference levels, so only the data point for six candidates
> meaningfully matches this method. About simulation: The other data
> points for "STAR" voting simulate a STAR-like ballot on which the number
> of preference levels matches the number of candidates. Also, these
> tests simulate non-tactical ballot marking, but human voters using STAR
> voting in a real-life election, especially a US general election, would
> use ballot-marking tactics that exploit the method's ability to express
> strong preferences.
>
> * RCIPE -- Ranked Choice Including Pairwise Elimination -- has fewer CI
> failures compared to the other methods. About this method: RCIPE is
> similar to IRV except that if an elimination round includes a "pairwise
> losing candidate" (a.k.a. Condorcet loser) then this candidate is
> eliminated instead of the fewest-transferred-votes candidate. When an
> elimination round involves a tie, this method resolves the tie using the
> IPE counting method.
>
> * IPE -- Instant Pairwise Elimination -- has the lowest failure rates
> compared to the other methods. About this method: IPE eliminates the
> candidate who has the highest "opposition" count, where the opposition
> count for a candidate is the number of remaining candidates who (on a
> ballot) are ranked higher than that candidate, summed across all the
> ballots. If there is a tie, it's resolved using the lowest "support"
> count, which counts the remaining candidates who are ranked lower than
> the specified candidate. Method clarification: This counting method
> does not actually re-count the ballots for each elimination round;
> instead a calculator and pen and paper can be used with the overall
> pairwise-count table to calculate the opposition and support counts
> (which change after each elimination).
>
> If someone wants a closer look at the actual numbers used in this
> scatter plot, they are at the bottom of this text file:
>
> https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/results_from_generate_random_ballots.txt
>
>
> Here's a link to the C++ program (which mostly uses the C language
> subset) that generates random ballots, supplies these ballots to
> separate software where the winners are calculated, and analyzes the
> results:
>
> https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/generate_random_ballots.cpp
>
>
> I hope you agree that these results are very helpful for comparing
> vote-counting methods.
>
> For perspective, my interest in CI and IIA failure/success rates is
> based on my frustration that money-based tactics are used to manipulate
> election results by exploiting CI and IIA failures in ways that achieve
> strategic nomination. These money-based tactics include:
>
> * Financially supporting clones (similar candidates) who split votes
> away from a popular reform-minded candidate
>
> * Removing financial support from clones (similar candidates) who split
> votes away from the status-quo-supporting (puppet-like) candidate
>
> * Possibly supporting distracting (irrelevant) candidates
>
> In contrast, I believe it's more difficult to use money to manipulate an
> election by exploiting other kinds of failures such as: monotonicity,
> favorite betrayal, later no help/harm, etc. In other words, I believe
> these other fairness criteria too often get more attention than they
> deserve (under current money-dominant political conditions).
>
> Here's a final note to those of you who are in the academic world. I
> invite you to reproduce these results and add other methods and publish
> the results. Why is this important? The improvement of Wikipedia
> articles about better vote-counting methods requires peer-reviewed
> academic articles that meaningfully compare vote-counting methods in
> ways that go beyond Wikipedia's simple pass/fail checklist in the
> "Comparison of electoral systems" article. Alas, too often that
> over-simplistic checklist gets cited as evidence of support for inferior
> vote-counting methods.
>
> In other words, flagging vote-counting failures as either zero or
> non-zero is primitive. We need more measurements of HOW OFTEN the
> non-zero failures occur.
>
> Richard Fobes
> "The VoteFair guy"
> ----
> Election-Methods mailing list - see https://electorama.com/em for list info
>
KM
Kristofer Munsterhjelm
Sun, Jun 20, 2021 1:53 PM
On 20.06.2021 02:41, VoteFair wrote:
I have updated the scatter plot that charts Clone Independence and IIA
(Independence of Irrelevant Alternatives) for various methods. The
scatter plot is (still) at:
https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
Here are the most important changes to the software and chart:
- The Clone Independence test now categorizes the case of a clone
candidate displacing the similar candidate as a success, not a failure.
This interpretation was requested on the r/EndFPTP subreddit, and it
makes sense to me. The other three kinds of CI failures continue to be
categorized as failures. This means that when the original candidate
who is similar to the clones (is there a name for this candidate?) wins
without the clones, and then loses to one of the clones (when they are
added), that displacement is not regarded as a failure of clone
independence. The wording in the Wikipedia article on Clone
Independence implies that such displacements are failures, so that's the
interpretation I originally used. I'm not suggesting that the Wikipedia
wording is incorrect; rather I'm suggesting that when measuring CI
success/failure rates it's important to also measure how often each kind
of CI failure occurs (which is what I wrote earlier), and because this
scatter plot is intended to be a meaningful summary of the measurements.
I'd say the three clone failure types are:
Suppose A is cloned into A1 and A2. Then, for any two other candidates B
and C from the original election:
- If A won before cloning, but B wins after, that's vote-splitting.
- If B won before cloning, but A1 or A2 wins after, that's teaming.
- If B won before cloning, but C wins after, that's crowding.
Everything else (A->A1, A->A2, B->B, C->C) is a pass.
- Because of this change, the success rates for the Condorcet-Kemeny
method and the Borda count method are much higher.
James Green-Armytage's paper on IRV shows that even though IRV is
theoretically cloneproof, it's unusually vulnerable to candidate exit
(where similar candidates leave the race to get a candidate elected).
Does your plot try to find such "near clone independence" failures?
If it doesn't, then something's still off: IRV is strictly speaking
clone independent, so its clone independence rate should be 100%.
On 20.06.2021 02:41, VoteFair wrote:
> I have updated the scatter plot that charts Clone Independence and IIA
> (Independence of Irrelevant Alternatives) for various methods. The
> scatter plot is (still) at:
>
> https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
>
> Here are the most important changes to the software and chart:
>
> * The Clone Independence test now categorizes the case of a clone
> candidate displacing the similar candidate as a success, not a failure.
> This interpretation was requested on the r/EndFPTP subreddit, and it
> makes sense to me. The other three kinds of CI failures continue to be
> categorized as failures. This means that when the original candidate
> who is similar to the clones (is there a name for this candidate?) wins
> without the clones, and then loses to one of the clones (when they are
> added), that displacement is not regarded as a failure of clone
> independence. The wording in the Wikipedia article on Clone
> Independence implies that such displacements are failures, so that's the
> interpretation I originally used. I'm not suggesting that the Wikipedia
> wording is incorrect; rather I'm suggesting that when measuring CI
> success/failure rates it's important to also measure how often each kind
> of CI failure occurs (which is what I wrote earlier), and because this
> scatter plot is intended to be a meaningful summary of the measurements.
I'd say the three clone failure types are:
Suppose A is cloned into A1 and A2. Then, for any two other candidates B
and C from the original election:
1. If A won before cloning, but B wins after, that's vote-splitting.
2. If B won before cloning, but A1 or A2 wins after, that's teaming.
3. If B won before cloning, but C wins after, that's crowding.
Everything else (A->A1, A->A2, B->B, C->C) is a pass.
> * Because of this change, the success rates for the Condorcet-Kemeny
> method and the Borda count method are much higher.
>
>
> https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/generate_random_ballots.cpp
>
>
> As a reminder (and because someone on Reddit asked), I chose CI and IIA
> because they measure vulnerability to strategic nomination, which is
> easily exploited through the control of campaign contributions.
James Green-Armytage's paper on IRV shows that even though IRV is
theoretically cloneproof, it's unusually vulnerable to candidate exit
(where similar candidates leave the race to get a candidate elected).
Does your plot try to find such "near clone independence" failures?
If it doesn't, then something's still off: IRV is strictly speaking
clone independent, so its clone independence rate should be 100%.
V
VoteFair
Tue, Jun 22, 2021 6:36 PM
On 6/20/2021 6:53 AM, Kristofer Munsterhjelm wrote:
...
I'd say the three clone failure types are:
Suppose A is cloned into A1 and A2. Then, for any two other candidates B
and C from the original election:
- If A won before cloning, but B wins after, that's vote-splitting.
- If B won before cloning, but A1 or A2 wins after, that's teaming.
- If B won before cloning, but C wins after, that's crowding.
Everything else (A->A1, A->A2, B->B, C->C) is a pass.
I see four categories:
-
A wins without clone, but B wins with clone: clone "hurts" similar
candidate (yes usually because of vote splitting but I'm not sure that's
always the case)
-
B wins without clone, but A or A1 or A2 wins with clone: clone
"helps" similar candidate (A/A1) (yes usually intentionally if teaming
used, but can be accidental)
-
B wins without clone, but C wins with clone: similar to IIA (I don't
have a name for this category)
-
A wins without clone, but A2 wins with clone: clone "displaces"
similar candidate
James Green-Armytage's paper on IRV shows that even though IRV is
theoretically cloneproof, it's unusually vulnerable to candidate exit
(where similar candidates leave the race to get a candidate elected).
Does your plot try to find such "near clone independence" failures?
No it does not try to isolate this kind of failure. Instead, the IIA
(independence of irrelevant alternatives) test does this kind of testing
where removing any candidate is a failure. In the IIA tests there are
no clones, so no my tests don't measure this specific kind of failure.
Such failures would just contribute toward the IIA failures.
If it doesn't, then something's still off: IRV is strictly speaking
clone independent, so its clone independence rate should be 100%.
This bothers me too, yet I've looked for bugs that might affect this and
I haven't found any -- although of course that doesn't mean they aren't
there.
If I were only testing IRV failures without comparing the results to
other methods using the same ballots, then I could simply ignore cases
where there is a tie for the fewest transferred votes (during any of the
intermediate, but not final, elimination rounds). And then it would
have 100% clone independence.
How does the academic paper resolve such ties? Or does the math assume
such ties do not occur?
I do ignore cases where IRV yields a tie for winner. And also I ignore
cases where the Condorcet-Kemeny method or plurality yield a tie for who
wins. That makes sense because those cases are actual ties.
But I can't justify ignoring cases that are problematic for just one
method. That could cause higher failure rates for the other methods,
especially the ones that include tie-breaking rules. That would not be
a fair comparison across the different methods.
I regard this as one of the reasons why such measurements have not
already been done. It's challenging!
Yet being able to yield numeric comparisons is essential to move beyond
the simplistic zero versus non-zero failure-rate arguments.
Kristofer, as always I greatly appreciate your wise feedback!!
Richard Fobes
On 6/20/2021 6:53 AM, Kristofer Munsterhjelm wrote:
On 20.06.2021 02:41, VoteFair wrote:
I have updated the scatter plot that charts Clone Independence and IIA
(Independence of Irrelevant Alternatives) for various methods. The
scatter plot is (still) at:
https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
Here are the most important changes to the software and chart:
- The Clone Independence test now categorizes the case of a clone
candidate displacing the similar candidate as a success, not a failure.
This interpretation was requested on the r/EndFPTP subreddit, and it
makes sense to me. The other three kinds of CI failures continue to be
categorized as failures. This means that when the original candidate
who is similar to the clones (is there a name for this candidate?) wins
without the clones, and then loses to one of the clones (when they are
added), that displacement is not regarded as a failure of clone
independence. The wording in the Wikipedia article on Clone
Independence implies that such displacements are failures, so that's the
interpretation I originally used. I'm not suggesting that the Wikipedia
wording is incorrect; rather I'm suggesting that when measuring CI
success/failure rates it's important to also measure how often each kind
of CI failure occurs (which is what I wrote earlier), and because this
scatter plot is intended to be a meaningful summary of the measurements.
I'd say the three clone failure types are:
Suppose A is cloned into A1 and A2. Then, for any two other candidates B
and C from the original election:
- If A won before cloning, but B wins after, that's vote-splitting.
- If B won before cloning, but A1 or A2 wins after, that's teaming.
- If B won before cloning, but C wins after, that's crowding.
Everything else (A->A1, A->A2, B->B, C->C) is a pass.
- Because of this change, the success rates for the Condorcet-Kemeny
method and the Borda count method are much higher.
James Green-Armytage's paper on IRV shows that even though IRV is
theoretically cloneproof, it's unusually vulnerable to candidate exit
(where similar candidates leave the race to get a candidate elected).
Does your plot try to find such "near clone independence" failures?
If it doesn't, then something's still off: IRV is strictly speaking
clone independent, so its clone independence rate should be 100%.
On 6/20/2021 6:53 AM, Kristofer Munsterhjelm wrote:
> ...
> I'd say the three clone failure types are:
>
> Suppose A is cloned into A1 and A2. Then, for any two other candidates B
> and C from the original election:
>
> 1. If A won before cloning, but B wins after, that's vote-splitting.
> 2. If B won before cloning, but A1 or A2 wins after, that's teaming.
> 3. If B won before cloning, but C wins after, that's crowding.
>
> Everything else (A->A1, A->A2, B->B, C->C) is a pass.
I see four categories:
1. A wins without clone, but B wins with clone: clone "hurts" similar
candidate (yes usually because of vote splitting but I'm not sure that's
always the case)
2. B wins without clone, but A or A1 or A2 wins with clone: clone
"helps" similar candidate (A/A1) (yes usually intentionally if teaming
used, but can be accidental)
3. B wins without clone, but C wins with clone: similar to IIA (I don't
have a name for this category)
4. A wins without clone, but A2 wins with clone: clone "displaces"
similar candidate
> James Green-Armytage's paper on IRV shows that even though IRV is
> theoretically cloneproof, it's unusually vulnerable to candidate exit
> (where similar candidates leave the race to get a candidate elected).
> Does your plot try to find such "near clone independence" failures?
No it does not try to isolate this kind of failure. Instead, the IIA
(independence of irrelevant alternatives) test does this kind of testing
where removing any candidate is a failure. In the IIA tests there are
no clones, so no my tests don't measure this specific kind of failure.
Such failures would just contribute toward the IIA failures.
> If it doesn't, then something's still off: IRV is strictly speaking
> clone independent, so its clone independence rate should be 100%.
This bothers me too, yet I've looked for bugs that might affect this and
I haven't found any -- although of course that doesn't mean they aren't
there.
If I were only testing IRV failures without comparing the results to
other methods using the same ballots, then I could simply ignore cases
where there is a tie for the fewest transferred votes (during any of the
intermediate, but not final, elimination rounds). And then it would
have 100% clone independence.
How does the academic paper resolve such ties? Or does the math assume
such ties do not occur?
I do ignore cases where IRV yields a tie for winner. And also I ignore
cases where the Condorcet-Kemeny method or plurality yield a tie for who
wins. That makes sense because those cases are actual ties.
But I can't justify ignoring cases that are problematic for just one
method. That could cause higher failure rates for the other methods,
especially the ones that include tie-breaking rules. That would not be
a fair comparison across the different methods.
I regard this as one of the reasons why such measurements have not
already been done. It's challenging!
Yet being able to yield numeric comparisons is essential to move beyond
the simplistic zero versus non-zero failure-rate arguments.
Kristofer, as always I greatly appreciate your wise feedback!!
Richard Fobes
On 6/20/2021 6:53 AM, Kristofer Munsterhjelm wrote:
> On 20.06.2021 02:41, VoteFair wrote:
>> I have updated the scatter plot that charts Clone Independence and IIA
>> (Independence of Irrelevant Alternatives) for various methods. The
>> scatter plot is (still) at:
>>
>> https://www.rankedchoiceoregon.org/img/clone_iia_success_rates.jpg
>>
>> Here are the most important changes to the software and chart:
>>
>> * The Clone Independence test now categorizes the case of a clone
>> candidate displacing the similar candidate as a success, not a failure.
>> This interpretation was requested on the r/EndFPTP subreddit, and it
>> makes sense to me. The other three kinds of CI failures continue to be
>> categorized as failures. This means that when the original candidate
>> who is similar to the clones (is there a name for this candidate?) wins
>> without the clones, and then loses to one of the clones (when they are
>> added), that displacement is not regarded as a failure of clone
>> independence. The wording in the Wikipedia article on Clone
>> Independence implies that such displacements are failures, so that's the
>> interpretation I originally used. I'm not suggesting that the Wikipedia
>> wording is incorrect; rather I'm suggesting that when measuring CI
>> success/failure rates it's important to also measure how often each kind
>> of CI failure occurs (which is what I wrote earlier), and because this
>> scatter plot is intended to be a meaningful summary of the measurements.
>
> I'd say the three clone failure types are:
>
> Suppose A is cloned into A1 and A2. Then, for any two other candidates B
> and C from the original election:
>
> 1. If A won before cloning, but B wins after, that's vote-splitting.
> 2. If B won before cloning, but A1 or A2 wins after, that's teaming.
> 3. If B won before cloning, but C wins after, that's crowding.
>
> Everything else (A->A1, A->A2, B->B, C->C) is a pass.
>
>> * Because of this change, the success rates for the Condorcet-Kemeny
>> method and the Borda count method are much higher.
>
>>
>>
>> https://github.com/cpsolver/VoteFair-ranking-cpp/blob/master/generate_random_ballots.cpp
>>
>>
>> As a reminder (and because someone on Reddit asked), I chose CI and IIA
>> because they measure vulnerability to strategic nomination, which is
>> easily exploited through the control of campaign contributions.
>
> James Green-Armytage's paper on IRV shows that even though IRV is
> theoretically cloneproof, it's unusually vulnerable to candidate exit
> (where similar candidates leave the race to get a candidate elected).
> Does your plot try to find such "near clone independence" failures?
>
> If it doesn't, then something's still off: IRV is strictly speaking
> clone independent, so its clone independence rate should be 100%.
>
KM
Kristofer Munsterhjelm
Sun, Jun 27, 2021 5:32 PM
On 22.06.2021 20:36, VoteFair wrote:
On 6/20/2021 6:53 AM, Kristofer Munsterhjelm wrote:
...
I'd say the three clone failure types are:
Suppose A is cloned into A1 and A2. Then, for any two other candidates B
and C from the original election:
- If A won before cloning, but B wins after, that's vote-splitting.
- If B won before cloning, but A1 or A2 wins after, that's teaming.
- If B won before cloning, but C wins after, that's crowding.
Everything else (A->A1, A->A2, B->B, C->C) is a pass.
I see four categories:
1. A wins without clone, but B wins with clone: clone "hurts" similar
candidate (yes usually because of vote splitting but I'm not sure that's
always the case)
2. B wins without clone, but A or A1 or A2 wins with clone: clone
"helps" similar candidate (A/A1) (yes usually intentionally if teaming
used, but can be accidental)
3. B wins without clone, but C wins with clone: similar to IIA (I don't
have a name for this category)
4. A wins without clone, but A2 wins with clone: clone "displaces"
similar candidate
The third category is usually called "crowding". This terminology seems
to be due to Blake Cretney, see
http://lists.electorama.com/pipermail/election-methods-electorama.com//2002-February/105357.html.
The earliest instance I can find of his jargon page is this:
https://web.archive.org/web/19991001204109/http://www.fortunecity.com/meltingpot/harrow/124/defn.html
As for the fourth, I don't think that's a failure, because for any
election where A is cloned into A and A2, there's an equivalent election
where A is cloned into A2 and A. Since clones only obey the property
everybody ranks them next to each other, it's not possible to determine
who's the original and who's the clone; to distinguish A and A2 would be
a failure of the neutrality criterion.
Or to put it differently, suppose you have an election like this, call
it election eX:
45: A>B>C
33: B>C>A
30: C>A>B
Without loss of generality, suppose A wins. Now make two clone
elections, eY:
45: A>A2>B>C
33: B>C>A2>A
30: C>A>A2>B
and eZ:
45: A2>A>B>C
33: B>C>A>A2
30: C>A2>A>B
Now in eY, either a member of the clone set wins with positive
probability, or someone outside the clone set does. If it's the latter,
you have a straightforward clone failure. So suppose the winner/s in eY
is/are part of the clone set.
If A and A2 tie, then A has gone from winning with certainty to winning
with 50% probability, which is a failure of the fourth criterion. If A2
wins, then it's also a failure of the fourth criterion. This only leaves
the possibility that A wins in eY.
But if A wins, then by neutrality A2 must win in election Z, which would
be a failure of the fourth criterion. So no method can be cloneproof: it
will either fail when going from eX to eY, or when going from eX to eZ.
James Green-Armytage's paper on IRV shows that even though IRV is
theoretically cloneproof, it's unusually vulnerable to candidate exit
(where similar candidates leave the race to get a candidate elected).
Does your plot try to find such "near clone independence" failures?
No it does not try to isolate this kind of failure. Instead, the IIA
(independence of irrelevant alternatives) test does this kind of testing
where removing any candidate is a failure. In the IIA tests there are
no clones, so no my tests don't measure this specific kind of failure.
Such failures would just contribute toward the IIA failures.
If it doesn't, then something's still off: IRV is strictly speaking
clone independent, so its clone independence rate should be 100%.
This bothers me too, yet I've looked for bugs that might affect this and
I haven't found any -- although of course that doesn't mean they aren't
there.
If I were only testing IRV failures without comparing the results to
other methods using the same ballots, then I could simply ignore cases
where there is a tie for the fewest transferred votes (during any of the
intermediate, but not final, elimination rounds). And then it would
have 100% clone independence.
How does the academic paper resolve such ties? Or does the math assume
such ties do not occur?
Suppose that you break ties with a tiebreaker that itself is cloneproof.
Then the cloning doesn't get someone who would've been eliminated later,
eliminated earlier (since there's no teaming or crowding in either the
tiebreak or in Plurality). So the elimination order is the same up until
either A or A2 is eliminated and the other one remains. After that
happens, the remaining candidate gets all of the clone set's first
preference votes and the method proceeds as it would without the clone.
Finding an appropriate tiebreaker is the difficult part. I don't know
how JGA did it, but here's a suggestion that should be cloneproof.
Let's say the tiebreaker consists of a ranking, where in a tie between
some candidates, you eliminate the tied candidate that's ranked last on
that ranking. You have one ranking before the cloning and another one after.
Then the proof says that as long as you eliminate candidates one at a
time, and the rankings before and after are the same, except that the
candidate cloned is replaced with the clone set in some order, IRV will
be cloneproof.
The usual way to get such a ranking would be to pick a random ballot and
use the ranking on that ballot (completing it with random voter
hierarchy if there's equal-rank or truncation:
https://electowiki.org/wiki/Maximize_Affirmed_Majorities#Random_Voter_Hierarchy_tiebreak_procedure).
So you could implement this using random ballot to create the ranking
before the cloning, and use the exact same ballot to create the ranking
after the cloning.
One could argue that this leaves too much to chance: it could be that
IRV is cloneproof only for some random ballot rankings, but not for
every such ranking. But the proof shows that it's either cloneproof for
none of them or for all of them. So in the particular case of IRV, this
will suffice to show that IRV is cloneproof - the randomness has no
effect as far as clone resistance goes.
I do ignore cases where IRV yields a tie for winner. And also I ignore
cases where the Condorcet-Kemeny method or plurality yield a tie for who
wins. That makes sense because those cases are actual ties.
I think you can handle clone failure in the presence of winning ties.
If the winner set doesn't contain A, you clone A, and now it contains A,
then that's teaming.
If the winner set contains A, you clone A, and A is kicked off the set,
that's vote-splitting.
If you clone A and someone who isn't A is either kicked off or added to
the winner set, then that's crowding.
This doesn't properly classify some clone failures, but some of them
defy classification into just one category when you're dealing with
winner ties. For instance, suppose the winner set before cloning is A
and B; and after, it is A, B, and C. This has aspects both of
vote-splitting (because the chance of a tie-breaker choosing A is
reduced) and crowding (because C got admitted).
More generally, suppose you have a cloneproof tiebreaker like Random
Ballot (choose a random ballot, pick the winner who's listed first on
it). Then something like:
-
if the probability that the winner comes from the clone set after
cloning is reduced, that's vote-splitting;
-
if the probability that the winner comes from the clone set after
cloning is increased, that's teaming;
-
and if the conditional probability of electing some candidate X not in
the clone set, given that you elect a candidate outside the clone set,
changes, that's crowding.
But I can't justify ignoring cases that are problematic for just one
method. That could cause higher failure rates for the other methods,
especially the ones that include tie-breaking rules. That would not be
a fair comparison across the different methods.
I regard this as one of the reasons why such measurements have not
already been done. It's challenging!
There's another problem as well that I've been mentioning numerous times
:-) When you count "how often" or "how likely", you have to assume some
probability distribution - i.e. how often a particular election is going
to appear. This probability distribution may well change as voters come
to learn the method.
FairVote makes a big deal (as I understand it) about IRV tending to
elect Condorcet winners. However, this is under the probability
distribution inherited from Plurality, where you have two large parties
and a bunch of fringe ones whose only danger is splitting the vote of
major-party voters.
Given some time, the voters may think that now they can vote for third
parties without any harm; but when a third party gets large enough and
is everybody's second choice, cue Burlington.
How often does IRV fail to elect the Condorcet winner? That depends on
whether there are any third parties around.
So any "how often" calculation should be qualified by noting just what
kind of distribution/voter behavior the calculation assumes. Whether
it's uniform utilities, impartial culture, something spatial, or based
on polling data like Armytage's analysis.
Yet being able to yield numeric comparisons is essential to move beyond
the simplistic zero versus non-zero failure-rate arguments.
Kristofer, as always I greatly appreciate your wise feedback!!
On 22.06.2021 20:36, VoteFair wrote:
> On 6/20/2021 6:53 AM, Kristofer Munsterhjelm wrote:
>> ...
>> I'd say the three clone failure types are:
>>
>> Suppose A is cloned into A1 and A2. Then, for any two other candidates B
>> and C from the original election:
>>
>> 1. If A won before cloning, but B wins after, that's vote-splitting.
>> 2. If B won before cloning, but A1 or A2 wins after, that's teaming.
>> 3. If B won before cloning, but C wins after, that's crowding.
>>
>> Everything else (A->A1, A->A2, B->B, C->C) is a pass.
>
>
> I see four categories:
>
> 1. A wins without clone, but B wins with clone: clone "hurts" similar
> candidate (yes usually because of vote splitting but I'm not sure that's
> always the case)
>
> 2. B wins without clone, but A or A1 or A2 wins with clone: clone
> "helps" similar candidate (A/A1) (yes usually intentionally if teaming
> used, but can be accidental)
>
> 3. B wins without clone, but C wins with clone: similar to IIA (I don't
> have a name for this category)
>
> 4. A wins without clone, but A2 wins with clone: clone "displaces"
> similar candidate
The third category is usually called "crowding". This terminology seems
to be due to Blake Cretney, see
http://lists.electorama.com/pipermail/election-methods-electorama.com//2002-February/105357.html.
The earliest instance I can find of his jargon page is this:
https://web.archive.org/web/19991001204109/http://www.fortunecity.com/meltingpot/harrow/124/defn.html
As for the fourth, I don't think that's a failure, because for any
election where A is cloned into A and A2, there's an equivalent election
where A is cloned into A2 and A. Since clones only obey the property
everybody ranks them next to each other, it's not possible to determine
who's the original and who's the clone; to distinguish A and A2 would be
a failure of the neutrality criterion.
Or to put it differently, suppose you have an election like this, call
it election eX:
45: A>B>C
33: B>C>A
30: C>A>B
Without loss of generality, suppose A wins. Now make two clone
elections, eY:
45: A>A2>B>C
33: B>C>A2>A
30: C>A>A2>B
and eZ:
45: A2>A>B>C
33: B>C>A>A2
30: C>A2>A>B
Now in eY, either a member of the clone set wins with positive
probability, or someone outside the clone set does. If it's the latter,
you have a straightforward clone failure. So suppose the winner/s in eY
is/are part of the clone set.
If A and A2 tie, then A has gone from winning with certainty to winning
with 50% probability, which is a failure of the fourth criterion. If A2
wins, then it's also a failure of the fourth criterion. This only leaves
the possibility that A wins in eY.
But if A wins, then by neutrality A2 must win in election Z, which would
be a failure of the fourth criterion. So no method can be cloneproof: it
will either fail when going from eX to eY, or when going from eX to eZ.
>> James Green-Armytage's paper on IRV shows that even though IRV is
>> theoretically cloneproof, it's unusually vulnerable to candidate exit
>> (where similar candidates leave the race to get a candidate elected).
>> Does your plot try to find such "near clone independence" failures?
>
> No it does not try to isolate this kind of failure. Instead, the IIA
> (independence of irrelevant alternatives) test does this kind of testing
> where removing any candidate is a failure. In the IIA tests there are
> no clones, so no my tests don't measure this specific kind of failure.
> Such failures would just contribute toward the IIA failures.
>
>> If it doesn't, then something's still off: IRV is strictly speaking
>> clone independent, so its clone independence rate should be 100%.
>
> This bothers me too, yet I've looked for bugs that might affect this and
> I haven't found any -- although of course that doesn't mean they aren't
> there.
>
> If I were only testing IRV failures without comparing the results to
> other methods using the same ballots, then I could simply ignore cases
> where there is a tie for the fewest transferred votes (during any of the
> intermediate, but not final, elimination rounds). And then it would
> have 100% clone independence.
>
> How does the academic paper resolve such ties? Or does the math assume
> such ties do not occur?
Suppose that you break ties with a tiebreaker that itself is cloneproof.
Then the cloning doesn't get someone who would've been eliminated later,
eliminated earlier (since there's no teaming or crowding in either the
tiebreak or in Plurality). So the elimination order is the same up until
either A or A2 is eliminated and the other one remains. After that
happens, the remaining candidate gets all of the clone set's first
preference votes and the method proceeds as it would without the clone.
Finding an appropriate tiebreaker is the difficult part. I don't know
how JGA did it, but here's a suggestion that should be cloneproof.
Let's say the tiebreaker consists of a ranking, where in a tie between
some candidates, you eliminate the tied candidate that's ranked last on
that ranking. You have one ranking before the cloning and another one after.
Then the proof says that as long as you eliminate candidates one at a
time, and the rankings before and after are the same, except that the
candidate cloned is replaced with the clone set in some order, IRV will
be cloneproof.
The usual way to get such a ranking would be to pick a random ballot and
use the ranking on that ballot (completing it with random voter
hierarchy if there's equal-rank or truncation:
https://electowiki.org/wiki/Maximize_Affirmed_Majorities#Random_Voter_Hierarchy_tiebreak_procedure).
So you could implement this using random ballot to create the ranking
before the cloning, and use the exact same ballot to create the ranking
after the cloning.
One could argue that this leaves too much to chance: it could be that
IRV is cloneproof only for some random ballot rankings, but not for
every such ranking. But the proof shows that it's either cloneproof for
none of them or for all of them. So in the particular case of IRV, this
will suffice to show that IRV is cloneproof - the randomness has no
effect as far as clone resistance goes.
> I do ignore cases where IRV yields a tie for winner. And also I ignore
> cases where the Condorcet-Kemeny method or plurality yield a tie for who
> wins. That makes sense because those cases are actual ties.
I think you can handle clone failure in the presence of winning ties.
If the winner set doesn't contain A, you clone A, and now it contains A,
then that's teaming.
If the winner set contains A, you clone A, and A is kicked off the set,
that's vote-splitting.
If you clone A and someone who isn't A is either kicked off or added to
the winner set, then that's crowding.
This doesn't properly classify some clone failures, but some of them
defy classification into just one category when you're dealing with
winner ties. For instance, suppose the winner set before cloning is A
and B; and after, it is A, B, and C. This has aspects both of
vote-splitting (because the chance of a tie-breaker choosing A is
reduced) and crowding (because C got admitted).
More generally, suppose you have a cloneproof tiebreaker like Random
Ballot (choose a random ballot, pick the winner who's listed first on
it). Then something like:
- if the probability that the winner comes from the clone set after
cloning is reduced, that's vote-splitting;
- if the probability that the winner comes from the clone set after
cloning is increased, that's teaming;
- and if the conditional probability of electing some candidate X not in
the clone set, given that you elect a candidate outside the clone set,
changes, that's crowding.
> But I can't justify ignoring cases that are problematic for just one
> method. That could cause higher failure rates for the other methods,
> especially the ones that include tie-breaking rules. That would not be
> a fair comparison across the different methods.
>
> I regard this as one of the reasons why such measurements have not
> already been done. It's challenging!
There's another problem as well that I've been mentioning numerous times
:-) When you count "how often" or "how likely", you have to assume some
probability distribution - i.e. how often a particular election is going
to appear. This probability distribution may well change as voters come
to learn the method.
FairVote makes a big deal (as I understand it) about IRV tending to
elect Condorcet winners. However, this is under the probability
distribution inherited from Plurality, where you have two large parties
and a bunch of fringe ones whose only danger is splitting the vote of
major-party voters.
Given some time, the voters may think that now they can vote for third
parties without any harm; but when a third party gets large enough and
is everybody's second choice, cue Burlington.
How often does IRV fail to elect the Condorcet winner? That depends on
whether there are any third parties around.
So any "how often" calculation should be qualified by noting just what
kind of distribution/voter behavior the calculation assumes. Whether
it's uniform utilities, impartial culture, something spatial, or based
on polling data like Armytage's analysis.
> Yet being able to yield numeric comparisons is essential to move beyond
> the simplistic zero versus non-zero failure-rate arguments.
>
> Kristofer, as always I greatly appreciate your wise feedback!!
Thank you. :-)
-km
V
VoteFair
Wed, Jul 7, 2021 10:30 PM
On 6/27/2021 10:32 AM, Kristofer Munsterhjelm wrote:
There's another problem as well that I've been mentioning numerous times
:-) When you count "how often" or "how likely", you have to assume some
probability distribution - i.e. how often a particular election is going
to appear. This probability distribution may well change as voters come
to learn the method.
...
So any "how often" calculation should be qualified by noting just what
kind of distribution/voter behavior the calculation assumes. Whether
it's uniform utilities, impartial culture, something spatial, or based
on polling data like Armytage's analysis.
My simulations have a fully random distribution, without any tactical
voting. Specifically each ranked ballot is generated randomly without
any interaction with any other ballot, and without any knowledge about
how the ballots will be counted. (And without any knowledge of what the
candidates represent.)
Of course in real elections voters will use tactical voting if they
believe that tactical voting can make a difference in the results.
To repeat, my simulations do not attempt to measure cases that involve
tactical voting.
(In contrast, I noticed that your software does perform measurements
regarding tactical voting.)
Perhaps a useful analogy is the tossing of a coin to determine a pattern
in the results. Of course the pattern of the results can have a
distribution (such as a "normal" distribution). Yet there is no pattern,
specifically no distribution pattern, in generating the random ballots.
To repeat what I've written before, these simulations are like stress
tests. They are not intended to represent real elections. Instead they
are intended to push election-counting methods into a zone where the
methods are forced to reveal how they differ from one another.
Switching to the other topic in your reply, I agree with your
categorization of clone failure types.
Richard Fobes
On 6/27/2021 10:32 AM, Kristofer Munsterhjelm wrote:
On 22.06.2021 20:36, VoteFair wrote:
On 6/20/2021 6:53 AM, Kristofer Munsterhjelm wrote:
...
I'd say the three clone failure types are:
Suppose A is cloned into A1 and A2. Then, for any two other candidates B
and C from the original election:
- If A won before cloning, but B wins after, that's vote-splitting.
- If B won before cloning, but A1 or A2 wins after, that's teaming.
- If B won before cloning, but C wins after, that's crowding.
Everything else (A->A1, A->A2, B->B, C->C) is a pass.
I see four categories:
-
A wins without clone, but B wins with clone: clone "hurts" similar
candidate (yes usually because of vote splitting but I'm not sure that's
always the case)
-
B wins without clone, but A or A1 or A2 wins with clone: clone
"helps" similar candidate (A/A1) (yes usually intentionally if teaming
used, but can be accidental)
-
B wins without clone, but C wins with clone: similar to IIA (I don't
have a name for this category)
-
A wins without clone, but A2 wins with clone: clone "displaces"
similar candidate
The third category is usually called "crowding". This terminology seems
to be due to Blake Cretney, see
http://lists.electorama.com/pipermail/election-methods-electorama.com//2002-February/105357.html.
The earliest instance I can find of his jargon page is this:
https://web.archive.org/web/19991001204109/http://www.fortunecity.com/meltingpot/harrow/124/defn.html
As for the fourth, I don't think that's a failure, because for any
election where A is cloned into A and A2, there's an equivalent election
where A is cloned into A2 and A. Since clones only obey the property
everybody ranks them next to each other, it's not possible to determine
who's the original and who's the clone; to distinguish A and A2 would be
a failure of the neutrality criterion.
Or to put it differently, suppose you have an election like this, call
it election eX:
45: A>B>C
33: B>C>A
30: C>A>B
Without loss of generality, suppose A wins. Now make two clone
elections, eY:
45: A>A2>B>C
33: B>C>A2>A
30: C>A>A2>B
and eZ:
45: A2>A>B>C
33: B>C>A>A2
30: C>A2>A>B
Now in eY, either a member of the clone set wins with positive
probability, or someone outside the clone set does. If it's the latter,
you have a straightforward clone failure. So suppose the winner/s in eY
is/are part of the clone set.
If A and A2 tie, then A has gone from winning with certainty to winning
with 50% probability, which is a failure of the fourth criterion. If A2
wins, then it's also a failure of the fourth criterion. This only leaves
the possibility that A wins in eY.
But if A wins, then by neutrality A2 must win in election Z, which would
be a failure of the fourth criterion. So no method can be cloneproof: it
will either fail when going from eX to eY, or when going from eX to eZ.
James Green-Armytage's paper on IRV shows that even though IRV is
theoretically cloneproof, it's unusually vulnerable to candidate exit
(where similar candidates leave the race to get a candidate elected).
Does your plot try to find such "near clone independence" failures?
No it does not try to isolate this kind of failure. Instead, the IIA
(independence of irrelevant alternatives) test does this kind of testing
where removing any candidate is a failure. In the IIA tests there are
no clones, so no my tests don't measure this specific kind of failure.
Such failures would just contribute toward the IIA failures.
If it doesn't, then something's still off: IRV is strictly speaking
clone independent, so its clone independence rate should be 100%.
This bothers me too, yet I've looked for bugs that might affect this and
I haven't found any -- although of course that doesn't mean they aren't
there.
If I were only testing IRV failures without comparing the results to
other methods using the same ballots, then I could simply ignore cases
where there is a tie for the fewest transferred votes (during any of the
intermediate, but not final, elimination rounds). And then it would
have 100% clone independence.
How does the academic paper resolve such ties? Or does the math assume
such ties do not occur?
Suppose that you break ties with a tiebreaker that itself is cloneproof.
Then the cloning doesn't get someone who would've been eliminated later,
eliminated earlier (since there's no teaming or crowding in either the
tiebreak or in Plurality). So the elimination order is the same up until
either A or A2 is eliminated and the other one remains. After that
happens, the remaining candidate gets all of the clone set's first
preference votes and the method proceeds as it would without the clone.
Finding an appropriate tiebreaker is the difficult part. I don't know
how JGA did it, but here's a suggestion that should be cloneproof.
Let's say the tiebreaker consists of a ranking, where in a tie between
some candidates, you eliminate the tied candidate that's ranked last on
that ranking. You have one ranking before the cloning and another one after.
Then the proof says that as long as you eliminate candidates one at a
time, and the rankings before and after are the same, except that the
candidate cloned is replaced with the clone set in some order, IRV will
be cloneproof.
The usual way to get such a ranking would be to pick a random ballot and
use the ranking on that ballot (completing it with random voter
hierarchy if there's equal-rank or truncation:
https://electowiki.org/wiki/Maximize_Affirmed_Majorities#Random_Voter_Hierarchy_tiebreak_procedure).
So you could implement this using random ballot to create the ranking
before the cloning, and use the exact same ballot to create the ranking
after the cloning.
One could argue that this leaves too much to chance: it could be that
IRV is cloneproof only for some random ballot rankings, but not for
every such ranking. But the proof shows that it's either cloneproof for
none of them or for all of them. So in the particular case of IRV, this
will suffice to show that IRV is cloneproof - the randomness has no
effect as far as clone resistance goes.
I do ignore cases where IRV yields a tie for winner. And also I ignore
cases where the Condorcet-Kemeny method or plurality yield a tie for who
wins. That makes sense because those cases are actual ties.
I think you can handle clone failure in the presence of winning ties.
If the winner set doesn't contain A, you clone A, and now it contains A,
then that's teaming.
If the winner set contains A, you clone A, and A is kicked off the set,
that's vote-splitting.
If you clone A and someone who isn't A is either kicked off or added to
the winner set, then that's crowding.
This doesn't properly classify some clone failures, but some of them
defy classification into just one category when you're dealing with
winner ties. For instance, suppose the winner set before cloning is A
and B; and after, it is A, B, and C. This has aspects both of
vote-splitting (because the chance of a tie-breaker choosing A is
reduced) and crowding (because C got admitted).
More generally, suppose you have a cloneproof tiebreaker like Random
Ballot (choose a random ballot, pick the winner who's listed first on
it). Then something like:
-
if the probability that the winner comes from the clone set after
cloning is reduced, that's vote-splitting;
-
if the probability that the winner comes from the clone set after
cloning is increased, that's teaming;
-
and if the conditional probability of electing some candidate X not in
the clone set, given that you elect a candidate outside the clone set,
changes, that's crowding.
But I can't justify ignoring cases that are problematic for just one
method. That could cause higher failure rates for the other methods,
especially the ones that include tie-breaking rules. That would not be
a fair comparison across the different methods.
I regard this as one of the reasons why such measurements have not
already been done. It's challenging!
There's another problem as well that I've been mentioning numerous times
:-) When you count "how often" or "how likely", you have to assume some
probability distribution - i.e. how often a particular election is going
to appear. This probability distribution may well change as voters come
to learn the method.
FairVote makes a big deal (as I understand it) about IRV tending to
elect Condorcet winners. However, this is under the probability
distribution inherited from Plurality, where you have two large parties
and a bunch of fringe ones whose only danger is splitting the vote of
major-party voters.
Given some time, the voters may think that now they can vote for third
parties without any harm; but when a third party gets large enough and
is everybody's second choice, cue Burlington.
How often does IRV fail to elect the Condorcet winner? That depends on
whether there are any third parties around.
So any "how often" calculation should be qualified by noting just what
kind of distribution/voter behavior the calculation assumes. Whether
it's uniform utilities, impartial culture, something spatial, or based
on polling data like Armytage's analysis.
Yet being able to yield numeric comparisons is essential to move beyond
the simplistic zero versus non-zero failure-rate arguments.
Kristofer, as always I greatly appreciate your wise feedback!!
On 6/27/2021 10:32 AM, Kristofer Munsterhjelm wrote:
> There's another problem as well that I've been mentioning numerous times
> :-) When you count "how often" or "how likely", you have to assume some
> probability distribution - i.e. how often a particular election is going
> to appear. This probability distribution may well change as voters come
> to learn the method.
>
> ...
>
> So any "how often" calculation should be qualified by noting just what
> kind of distribution/voter behavior the calculation assumes. Whether
> it's uniform utilities, impartial culture, something spatial, or based
> on polling data like Armytage's analysis.
My simulations have a fully random distribution, without any tactical
voting. Specifically each ranked ballot is generated randomly without
any interaction with any other ballot, and without any knowledge about
how the ballots will be counted. (And without any knowledge of what the
candidates represent.)
Of course in real elections voters will use tactical voting if they
believe that tactical voting can make a difference in the results.
To repeat, my simulations do not attempt to measure cases that involve
tactical voting.
(In contrast, I noticed that your software does perform measurements
regarding tactical voting.)
Perhaps a useful analogy is the tossing of a coin to determine a pattern
in the results. Of course the pattern of the results can have a
distribution (such as a "normal" distribution). Yet there is no pattern,
specifically no distribution pattern, in generating the random ballots.
To repeat what I've written before, these simulations are like stress
tests. They are not intended to represent real elections. Instead they
are intended to push election-counting methods into a zone where the
methods are forced to reveal how they differ from one another.
Switching to the other topic in your reply, I agree with your
categorization of clone failure types.
Richard Fobes
On 6/27/2021 10:32 AM, Kristofer Munsterhjelm wrote:
> On 22.06.2021 20:36, VoteFair wrote:
>> On 6/20/2021 6:53 AM, Kristofer Munsterhjelm wrote:
>>> ...
>>> I'd say the three clone failure types are:
>>>
>>> Suppose A is cloned into A1 and A2. Then, for any two other candidates B
>>> and C from the original election:
>>>
>>> 1. If A won before cloning, but B wins after, that's vote-splitting.
>>> 2. If B won before cloning, but A1 or A2 wins after, that's teaming.
>>> 3. If B won before cloning, but C wins after, that's crowding.
>>>
>>> Everything else (A->A1, A->A2, B->B, C->C) is a pass.
>>
>>
>> I see four categories:
>>
>> 1. A wins without clone, but B wins with clone: clone "hurts" similar
>> candidate (yes usually because of vote splitting but I'm not sure that's
>> always the case)
>>
>> 2. B wins without clone, but A or A1 or A2 wins with clone: clone
>> "helps" similar candidate (A/A1) (yes usually intentionally if teaming
>> used, but can be accidental)
>>
>> 3. B wins without clone, but C wins with clone: similar to IIA (I don't
>> have a name for this category)
>>
>> 4. A wins without clone, but A2 wins with clone: clone "displaces"
>> similar candidate
>
> The third category is usually called "crowding". This terminology seems
> to be due to Blake Cretney, see
> http://lists.electorama.com/pipermail/election-methods-electorama.com//2002-February/105357.html.
> The earliest instance I can find of his jargon page is this:
> https://web.archive.org/web/19991001204109/http://www.fortunecity.com/meltingpot/harrow/124/defn.html
>
> As for the fourth, I don't think that's a failure, because for any
> election where A is cloned into A and A2, there's an equivalent election
> where A is cloned into A2 and A. Since clones only obey the property
> everybody ranks them next to each other, it's not possible to determine
> who's the original and who's the clone; to distinguish A and A2 would be
> a failure of the neutrality criterion.
>
> Or to put it differently, suppose you have an election like this, call
> it election eX:
>
> 45: A>B>C
> 33: B>C>A
> 30: C>A>B
>
> Without loss of generality, suppose A wins. Now make two clone
> elections, eY:
>
> 45: A>A2>B>C
> 33: B>C>A2>A
> 30: C>A>A2>B
>
> and eZ:
>
> 45: A2>A>B>C
> 33: B>C>A>A2
> 30: C>A2>A>B
>
> Now in eY, either a member of the clone set wins with positive
> probability, or someone outside the clone set does. If it's the latter,
> you have a straightforward clone failure. So suppose the winner/s in eY
> is/are part of the clone set.
>
> If A and A2 tie, then A has gone from winning with certainty to winning
> with 50% probability, which is a failure of the fourth criterion. If A2
> wins, then it's also a failure of the fourth criterion. This only leaves
> the possibility that A wins in eY.
>
> But if A wins, then by neutrality A2 must win in election Z, which would
> be a failure of the fourth criterion. So no method can be cloneproof: it
> will either fail when going from eX to eY, or when going from eX to eZ.
>
>>> James Green-Armytage's paper on IRV shows that even though IRV is
>>> theoretically cloneproof, it's unusually vulnerable to candidate exit
>>> (where similar candidates leave the race to get a candidate elected).
>>> Does your plot try to find such "near clone independence" failures?
>>
>> No it does not try to isolate this kind of failure. Instead, the IIA
>> (independence of irrelevant alternatives) test does this kind of testing
>> where removing any candidate is a failure. In the IIA tests there are
>> no clones, so no my tests don't measure this specific kind of failure.
>> Such failures would just contribute toward the IIA failures.
>>
>>> If it doesn't, then something's still off: IRV is strictly speaking
>>> clone independent, so its clone independence rate should be 100%.
>>
>> This bothers me too, yet I've looked for bugs that might affect this and
>> I haven't found any -- although of course that doesn't mean they aren't
>> there.
>>
>> If I were only testing IRV failures without comparing the results to
>> other methods using the same ballots, then I could simply ignore cases
>> where there is a tie for the fewest transferred votes (during any of the
>> intermediate, but not final, elimination rounds). And then it would
>> have 100% clone independence.
>>
>> How does the academic paper resolve such ties? Or does the math assume
>> such ties do not occur?
>
> Suppose that you break ties with a tiebreaker that itself is cloneproof.
> Then the cloning doesn't get someone who would've been eliminated later,
> eliminated earlier (since there's no teaming or crowding in either the
> tiebreak or in Plurality). So the elimination order is the same up until
> either A or A2 is eliminated and the other one remains. After that
> happens, the remaining candidate gets all of the clone set's first
> preference votes and the method proceeds as it would without the clone.
>
> Finding an appropriate tiebreaker is the difficult part. I don't know
> how JGA did it, but here's a suggestion that should be cloneproof.
>
> Let's say the tiebreaker consists of a ranking, where in a tie between
> some candidates, you eliminate the tied candidate that's ranked last on
> that ranking. You have one ranking before the cloning and another one after.
>
> Then the proof says that as long as you eliminate candidates one at a
> time, and the rankings before and after are the same, except that the
> candidate cloned is replaced with the clone set in some order, IRV will
> be cloneproof.
>
> The usual way to get such a ranking would be to pick a random ballot and
> use the ranking on that ballot (completing it with random voter
> hierarchy if there's equal-rank or truncation:
> https://electowiki.org/wiki/Maximize_Affirmed_Majorities#Random_Voter_Hierarchy_tiebreak_procedure).
>
>
> So you could implement this using random ballot to create the ranking
> before the cloning, and use the exact same ballot to create the ranking
> after the cloning.
>
> One could argue that this leaves too much to chance: it could be that
> IRV is cloneproof only for some random ballot rankings, but not for
> every such ranking. But the proof shows that it's either cloneproof for
> none of them or for all of them. So in the particular case of IRV, this
> will suffice to show that IRV is cloneproof - the randomness has no
> effect as far as clone resistance goes.
>
>> I do ignore cases where IRV yields a tie for winner. And also I ignore
>> cases where the Condorcet-Kemeny method or plurality yield a tie for who
>> wins. That makes sense because those cases are actual ties.
>
> I think you can handle clone failure in the presence of winning ties.
>
> If the winner set doesn't contain A, you clone A, and now it contains A,
> then that's teaming.
>
> If the winner set contains A, you clone A, and A is kicked off the set,
> that's vote-splitting.
>
> If you clone A and someone who isn't A is either kicked off or added to
> the winner set, then that's crowding.
>
> This doesn't properly classify some clone failures, but some of them
> defy classification into just one category when you're dealing with
> winner ties. For instance, suppose the winner set before cloning is A
> and B; and after, it is A, B, and C. This has aspects both of
> vote-splitting (because the chance of a tie-breaker choosing A is
> reduced) and crowding (because C got admitted).
>
> More generally, suppose you have a cloneproof tiebreaker like Random
> Ballot (choose a random ballot, pick the winner who's listed first on
> it). Then something like:
>
> - if the probability that the winner comes from the clone set after
> cloning is reduced, that's vote-splitting;
>
> - if the probability that the winner comes from the clone set after
> cloning is increased, that's teaming;
>
> - and if the conditional probability of electing some candidate X not in
> the clone set, given that you elect a candidate outside the clone set,
> changes, that's crowding.
>
>> But I can't justify ignoring cases that are problematic for just one
>> method. That could cause higher failure rates for the other methods,
>> especially the ones that include tie-breaking rules. That would not be
>> a fair comparison across the different methods.
>>
>> I regard this as one of the reasons why such measurements have not
>> already been done. It's challenging!
>
> There's another problem as well that I've been mentioning numerous times
> :-) When you count "how often" or "how likely", you have to assume some
> probability distribution - i.e. how often a particular election is going
> to appear. This probability distribution may well change as voters come
> to learn the method.
>
> FairVote makes a big deal (as I understand it) about IRV tending to
> elect Condorcet winners. However, this is under the probability
> distribution inherited from Plurality, where you have two large parties
> and a bunch of fringe ones whose only danger is splitting the vote of
> major-party voters.
>
> Given some time, the voters may think that now they can vote for third
> parties without any harm; but when a third party gets large enough and
> is everybody's second choice, cue Burlington.
>
> How often does IRV fail to elect the Condorcet winner? That depends on
> whether there are any third parties around.
>
> So any "how often" calculation should be qualified by noting just what
> kind of distribution/voter behavior the calculation assumes. Whether
> it's uniform utilities, impartial culture, something spatial, or based
> on polling data like Armytage's analysis.
>
>> Yet being able to yield numeric comparisons is essential to move beyond
>> the simplistic zero versus non-zero failure-rate arguments.
>>
>> Kristofer, as always I greatly appreciate your wise feedback!!
>
> Thank you. :-)
>
> -km
>