@Jack-Waugh, I think that would be welcome.
tec
@tec
I've been interested in voting theory since I proved Arrow's impossibility theorem in a discrete math class in college as an exercise. I did not like it then, and now, decades later, I know why.
Best posts made by tec
-
RE: Multiwinner vs. Single-winner
-
RE: Collaborative Coding for Simulation
@jack-waugh on the original question regarding languages, I don't really know FORTH (or its variations) and I have a strong attraction to LISP. But for the simple and practical reasons that simulations have to be run on some system, having JavaScript client code is really the only way to go if you want more than a handful of users running simultaneous simulations.
-
RE: Simulating Voting Strategies
Warren D. Smith's Range Voting paper (2000) and his C code simulation goes over a number of different voting systems and simulates both honest and "rational" ballots for many of the voting systems he covers. The 30 voting system and strategy permutations in the paper are: (In the paper, WDS starts his list with zero and the "as 25" strategy reference is "as 26")
- Honest range voting (scaled utility vote)
- Honest Borda
- Honest Condorcet Least-Reversal (CLR)
- Honest Coombs STV (most least-liked candid eliminated each round)
- Honest Hare Single Transferable Vote STV (least most-liked canddt eliminated)
- Honest Copeland (win most pairwise elections)
- Honest Dabagh point-and-a-half
- Honest Black (if no Condorcet winner use Borda)
- Honest Bucklin
- Honest plurality+runoff for 2 top finishers
- Honest plurality (1 vote for max-util canddt)
- Honest bullet (1 vote against min-util cand)
- Majority vote on random candidate pair
- Random "dictator" voter dictates winner
- Random winner
- Worst-summed-utility winner
- Honest approval (threshhold=avg canddt utility)
- Strategic range/approval (average of 2 frontrunner utils as thresh)
- Rational range/approval (threshhold=moving avg)
- Rational plurality (vote for 1 of 2 frontrnnrs)
- Strategic Borda I (1 frontrunner top, 1 bottom, rest recursively)
- Rational bullet (vote against 1 of 2 frontrnnrs)
- Strategic CLR (strat same as 25)
- Strategic Hare STV (strat same as 25)
- Rational Borda (1 frontrunner max, 1 min, rest using moving avg to decide if max or min vote)
- Strategic Coombs STV (strat same as 25)
- Strategic Borda II (1 frontrunner max, 1 min vote, rest honest)
- Rational Dabagh point-and-a-half (moving avg)
- Strategic Copeland (strat same as 25)
- Strategic Black (same strat as 25)
(A Google search for rangevote.pdf will get you to the paper. His c code is at: https://www.rangevoting.org/WarrenSmithPages/homepage/votetest2.c)
I hope this provides some good options for your strategy simulations.
--tec
-
What Arrow's Impossibility Theorem Really Means
Arrow's impossibility theorem is frequently cited in the discussion between ordinal and cardinal voting systems, with the idea that AIT only applies to ordinal voting systems. It is true that Arrow was only looking at ordinal systems, with the goal of a social welfare function (SWF) that took as input a collection of individual preference orders and returned a collective order. But what Arrow actually proved was his conditions were inconsistent. Specifically, his condition allowing voters to have unrestricted preference orders (citizen sovereignty or CS) is inconsistent with the idea that a majority preference of B over A would somehow be reversed by the introduction of some alternative C.
The Independence of Irrelevant Alternatives (IIA) condition seems reasonable at first glance. Yet there is a real question about what is meant by irrelevant. Ignoring ties, there are four possible states for an electorate preferring B over A created by the introduction of C, and at least two of them are highly relevant to the collective choice.
- When both B and A are preferred over C, there is no problem, and B remains the collective choice.
- When B is preferred over C and C is preferred over A, there is still no problem because B remains the collective choice.
- When C is preferred over both A and B, it can be argued that C is anything but irrelevant, and the collective choice should now be C.
- When A is preferred over C and C is preferred over B, the introduction of C creates a majority cycle. This is also extremely relevant because the cycle creates something like an equivalence class. This is a problem because the selection of any one of the three alternatives requires the SWF to reverse a known majority preference.
It is easy to come up with preference profiles that result in majority cycles, such as this one:
|-----------------+-------+-------+---------------+-------+-------| | voter region | order | count | voter region | order | count | |-----------------+-------+-------+---------------+-------+-------| | left top | A>B>C | 15 | right top (B) | B>A>C | 19 | | left middle (A) | A>C>B | 18 | right middle | B>C>A | 15 | | left bottom (C) | C>A>B | 15 | right bottom | C>B>A | 18 | |-----------------+-------+-------+---------------+-------+-------|
In this preference profile A is preferred over C by 52 to 48, C is preferred over B by 51 to 49, and B is preferred over A by 52 to 48. But just coming up with a preference profile doesn't really help us understand why the voters would have these preferences, or how common they might be in a real election.
To get a better sense of this type of cycle, it helps to put the election in some type of context. In this case, consider a group of 100 voters in a small community trying to determine a location for a common resource such as a cell tower. Each voter has an ideal location (gray dot) and their utility of the resource is inversely proportional to the distance the single tower will be from their ideal. The locations are indicated by labeled locations (black dots) A, B, and C. In the two images, the voters are positioned identically, and the indifference lines (perpendicular bisectors between each pair of alternatives) are also identical. The only difference is the alternatives in the right image have been moved closer to the center.
The first point I want to drive home here is that majority cycles are real and are the result of real voter utilities for the specific alternatives in the cycle. The voting method is irrelevant to the existence of cycles. When there is a cycle, the use of a cardinal voting method does not magically make that cycle go away.
The second point I'd like to make is that no voting system that tries to do everything in one or two rounds can pick a good collective alternative when all the alternatives are collectively bad. The differences between the alternatives in the left image and those in the right image are what drove me to work on iterative voting systems.
-
RE: If there are only two candidates, could FPTP be improved upon?
@rob Your question was answered by Ken Arrow (of Arrow's impossibility theorem fame). AIT is more formally called Arrow's general possibility theorem, and is the second theorem in his Social Choice and Individual Values. His theorem 1 (Possibility Theorem for Two Alternatives) covers exactly this situation, and unlike his General Possibility theorem, the answer is affirmative. It is possible for a society to choose between two alternatives without violating any of his desirable conditions. The method to use is simple majority rule.
After Arrow published his book, Kenneth May published an article in Econometrica (1952) titled, A Set of Independent Necessary and Sufficient Conditions for Simple Majority Decision. That paper augmented Arrow's result and states that not only does simple majority rules satisfies Arrow's conditions, but every voting system that satisfies those conditions is equivalent to simple majority rule.
In essence, choosing between two alternatives is easy. The problem comes when you try to expand beyond two alternatives. That's what AIT shows and what Gibbard and Satterthwaite expanded upon.
So when limited to two alternatives simple majority decision works, and any other reasonable voting system devolves into simple majority decision when restricted to two alternatives.
-
RE: What Arrow's Impossibility Theorem Really Means
@BlainCellars the code I use is what I cobbled together since I started looking at voting systems and trying to figure out what worked best. Much of my work was done without consulting the (somewhat vast) literature on voting theory, and the tools and processes I used to help me think about things are all either free/open source or my own coding. This specific graphic was originally developed using Gnu Emacs with the svg package. Since the discussion code on this forum does not accept svg files, I used inkscape to convert the svg image into a png file.
More generally, when I started looking into the problem of voting I started with NetLogo because it provides an easy graphic display for agent-based models. Using NL, I could create and display 100 voter-agents randomly distributed in a 2D field, then create some alternatives for them to vote for under whatever system I was looking at. It worked great for a while, but as my questions got more involved, and my code-base became more extensive I realized I needed something a little more robust. I switched to Python because it allowed me to write tests for my code and make it more reliable.
At the moment my code is not well documented and is in need of refactoring. So while I can get it do to a number of interesting things I'm not sure how useful it would be to anyone else. On the other hand, I think it might be very useful for voting theorists to have easy access to spatial models. There is a data hierarchy to the various electorate models I've seen in recent voting theory papers. Tournaments have the least amount of data and have essentially eliminated the electorate altogether. Preference profiles have an electorate but lump voters together based on preference orders without any indication of the relative strength of individual voter preferences. Lists of individual voters with randomized utilities for each alternative allow some comparisons, but are still limited in that they really can't handle the addition of alternatives. Spatial models allow just about everything and are known to cover all possible tournaments, preference profiles, and utility models.
I'm assuming you have something in mind with your inquiry about programs. What are you looking for? Are you looking for images of electorates? Or do you want an election simulation environment for running tests and evaluations? I am thinking of putting my code on GitHub, but it will take a lot of work before it is ready for someone else to use. Are you looking for an answer to a specific need? Or are you willing to be an alpha-tester for a generic voting system evaluation framework? And more generally, would people such as the folks on this forum be interested in such an evaluation framework?
(This was a bigger answer than I suspect you wanted, but perhaps it will get us further in our collective quest for better collective decisions.)
-
RE: RCV IRV Hare
@jack-waugh, the main argument against instant runoff voting (IRV) in my mind is that it seems very easy to eliminate a Condorcet winner. The story line starts with an existing plurality system with two major parties (Duverger's law). Over time, the two parties will tend to converge to the center along any issue that is in play in an election. This leads to party members not being very happy with the results even when they win. This leads to challenges to both party establishments from their extreme wings. Under plurality, this can lead to parties losing due to the spoiler effect. Some of the arguments in favor of IRV claim it solves this problem because voters can vote for their extreme wing as their first choice and the party establishment alternative as their second choice, and the implicit assumption is the extreme alternative is eliminated in the first round and support flows to the "more electable" of the parties' offerings.
The problem with this argument is that IRV is being proposed in order to allow multiple alternatives, and the more choices their are, the fewer first place votes there will be on average for any individual alternative, and the greater the likelihood that alternatives in a crowded middle will be eliminated. Once that happens, we start seeing IRV electing fringe alternatives instead of moderates, which is almost exactly what we have now with plurality.
Note that this argument is against the standard IRV in which if there is no winner, the alternative with the fewest first-place votes is eliminated. The dynamic is much better in a variation of IRV called the Coombs method, which successively eliminates the alternative with the most last-place votes. (The fact that a single alternative can have both the most first-place votes and the most last-place votes seems to have made it a hard sell, but that's a different issue.)
A different argument against IRV [that was actually presented as an argument in favor of IRV, (Bartholdi, 1991)] is that strategic voting under IRV is so complicated that it is nearly impossible to determine the best strategic vote. The author's argument is that faced with the computational difficulties of determining the best strategic vote, voters will instead choose to vote honestly. To me, this line of thinking seems unsound, and I thus take it as just one more reason to avoid IRV.
I hope this helps you in your discussions.
Latest posts made by tec
-
RE: Collaborative Coding for Simulation
If you are looking for voting strategies and you aren't already familiar with it, you might want to look at Warren D. Smith's 2000 Range Voting paper. In it he proposes Range Voting (now more commonly referred to as Score) and compares it to about 30 other voting methods (really 14 other methods with naïve and strategic variations), The last I checked the paper can be found at Range Voting. The (c) code is also available at votetest2.c.
According to the (many) voting papers I've read over the past several years, there is a major decision that needs to be made when representing the electorate. In my opinion, the worst option is to use tournaments, which essentially ignore voters and even elections, and are about choosing a winner among a fixed set of alternatives based on a graph in which an arrow points from node A to node B if A would defeat B in a one-on-one simple majority election. The graph is just a given, and the challenge is to figure out a way to pick the winner. These papers have tended to focus on the computational difficulty of making this choice when the graph is large. The second way of representing the electorate is preference profiles, which is just a ranking of the fixed set of alternatives combined with a mulitplicity for each raking indicating how many voters would order the alternative that way. My problem with this method is that it doesn't provide any data for approval voting or score voting, or indeed any cardinal voting method.
My preferred method (which generally requires computer simulation for any realistically sized electorate) is to represent voters as points in an issue space (usually 2D or higher), and use a distance function between the voters and the alternatives (also points in the issue space) to generate ordinal or cardinal ballots.
One of the projects I'm considering is to start with something like Nicky Case's To Build A Better Ballot, and use interactive JavaScript to illustrate many of the problems with various voting systems. This is also similar to what @rob did in the underlying electorate model in his voting strategy simulation. (I do have an ulterior motive here. If the simulations start with the voters and distance functions to the alternatives, it becomes a lot easier to show exactly how an iterative voting system like SAVE would work, and how it would be significantly better than any non-iterative system. That argument is a lot easier with pictures.)
-
RE: Collaborative Coding for Simulation
@jack-waugh on the original question regarding languages, I don't really know FORTH (or its variations) and I have a strong attraction to LISP. But for the simple and practical reasons that simulations have to be run on some system, having JavaScript client code is really the only way to go if you want more than a handful of users running simultaneous simulations.
-
RE: If there are only two candidates, could FPTP be improved upon?
@rob Your question was answered by Ken Arrow (of Arrow's impossibility theorem fame). AIT is more formally called Arrow's general possibility theorem, and is the second theorem in his Social Choice and Individual Values. His theorem 1 (Possibility Theorem for Two Alternatives) covers exactly this situation, and unlike his General Possibility theorem, the answer is affirmative. It is possible for a society to choose between two alternatives without violating any of his desirable conditions. The method to use is simple majority rule.
After Arrow published his book, Kenneth May published an article in Econometrica (1952) titled, A Set of Independent Necessary and Sufficient Conditions for Simple Majority Decision. That paper augmented Arrow's result and states that not only does simple majority rules satisfies Arrow's conditions, but every voting system that satisfies those conditions is equivalent to simple majority rule.
In essence, choosing between two alternatives is easy. The problem comes when you try to expand beyond two alternatives. That's what AIT shows and what Gibbard and Satterthwaite expanded upon.
So when limited to two alternatives simple majority decision works, and any other reasonable voting system devolves into simple majority decision when restricted to two alternatives.
-
RE: RCV IRV Hare
@jack-waugh, the main argument against instant runoff voting (IRV) in my mind is that it seems very easy to eliminate a Condorcet winner. The story line starts with an existing plurality system with two major parties (Duverger's law). Over time, the two parties will tend to converge to the center along any issue that is in play in an election. This leads to party members not being very happy with the results even when they win. This leads to challenges to both party establishments from their extreme wings. Under plurality, this can lead to parties losing due to the spoiler effect. Some of the arguments in favor of IRV claim it solves this problem because voters can vote for their extreme wing as their first choice and the party establishment alternative as their second choice, and the implicit assumption is the extreme alternative is eliminated in the first round and support flows to the "more electable" of the parties' offerings.
The problem with this argument is that IRV is being proposed in order to allow multiple alternatives, and the more choices their are, the fewer first place votes there will be on average for any individual alternative, and the greater the likelihood that alternatives in a crowded middle will be eliminated. Once that happens, we start seeing IRV electing fringe alternatives instead of moderates, which is almost exactly what we have now with plurality.
Note that this argument is against the standard IRV in which if there is no winner, the alternative with the fewest first-place votes is eliminated. The dynamic is much better in a variation of IRV called the Coombs method, which successively eliminates the alternative with the most last-place votes. (The fact that a single alternative can have both the most first-place votes and the most last-place votes seems to have made it a hard sell, but that's a different issue.)
A different argument against IRV [that was actually presented as an argument in favor of IRV, (Bartholdi, 1991)] is that strategic voting under IRV is so complicated that it is nearly impossible to determine the best strategic vote. The author's argument is that faced with the computational difficulties of determining the best strategic vote, voters will instead choose to vote honestly. To me, this line of thinking seems unsound, and I thus take it as just one more reason to avoid IRV.
I hope this helps you in your discussions.
-
RE: Simulating Voting Strategies
@Jack-Waugh My apologies. I did not notice that your question about a voter favoring both front runners was directed to @Rob. I mistakenly thought it was directed to me based on a strategy WDS proposed in his paper for IRV simulations.
The WDS strategy assumes the two front runners are significantly distinct and any voter tempted to vote strategically would have strong preferences. If I recall correctly, the WDS strategy for IRV (Strategic Hare STV) was to give the maximal rank to the better of the two front runners and the worst rank to the lesser front runner, then use a moving average to fill out the ballot by giving the highest remaining rank to the next most likely alternative that was better than average and the lowest remaining rank to the next most likely alternative that was worse than average.
That strategy is certainly codable for a simulation, but it also seemed like a direct lead-in to your question about a why voter that liked both front-runners would vote strategically, and framed the question in the real world. Hence my response. Hopefully, it is at least an interesting scenario.
-
RE: Simulating Voting Strategies
@Jack-Waugh Just a clarification. My post about Warren D. Smith's Range voting paper was in response to this request for strategic algorithms to simulate. Next time I'll be sure to "reply" to the post I'm replying to. Sorry for any confusion.
-
RE: Simulating Voting Strategies
That question gets right to the heart of the problems in IRV. A paper by Bartholdi and Orlin (1991), Single Transferable Vote Resists Strategic Voting, suggests IRV should be used because it is so difficult to figure out how to vote strategically. The question a rational voter faces when filling out their IRV ballot involves both the accuracy of the polling data, and what the polling data shows. If polling shows both front runners are significantly ahead of an unacceptable third choice and the sum of the top three poll numbers is significantly larger than the sum of the poll data for the remaining choices, then an honest IRV ballot is probably a strategic ballot. But the devil is in the details, or more specifically the eliminations. Here's a scenario that might answer your question.
Suppose there are five alternatives, global moderates A, B, and C, and more extreme alternatives D and E. The party affiliations are A and B in one party, and C,D,E in the other. Alternative D is solidly in the middle of its party, and alternative E is at the extreme.
The actual profiles are as follows. However, these are not known.
A>B>C>D>E 24%
B>A>C>D>E 24%
C>D>A>B>E 11%
C>D>B>A>E 11%
E>D>C>A>B 7.6%
E>D>C>B>A 7.6%
D>E>C>A>B 3.7%
D>E>C>B>A 3.7%
D>C>E>A>B 3.7%
D>C>E>B>A 3.7%If you look at these profiles carefully, you'll see C is a Condorcet winner. However, this is an IRV election so polls will be about round results and what would happen after eliminations, and C's Condorcet status is not reported as such.
The polls state: A and B are the frontrunners for the first round, with C, C3 and C2 following. C2 voters are likely to have C or C3 as their second choices. Almost all C3 voters have C2 as their second choice, with C as a distant third. A and B voters are likely to stay within their party, but could tolerate C. If forced to choose, C voters strongly prefer C2 over C3, but might possibly break with their party if their only in-party choice is C3.
Our voter Joey is pretty undecided about A and B, liking both, but very much anti C,D,and E. So Joey takes the poll data and considers the likely outcome:
First count, A:24%, B:24% (too close to call), C:22%, C2:14.8%, C3:15.2%.
Status: no winner, C2 eliminatedPoll say C2 votes will split evenly between C and C3.
Second count: A:24%, B:24% (too close to call), C:29.4%, C3:22.6%.
Status: no winner, C3 eliminated.Polls say the initial C3 preferences were C3>C2>C, and the initial C2 preferences were split between C2>C3>C and C2>C>C3. With C2 already eliminated, all of C3 votes go to C.
Third count: A:24%, B:24% (too close to call), C:52%.
Status: C is the winner.Given these predictions, Joey might decide to change his honest vote from A>B>C>C2 to C2>A>B>C, and encourage some of his like-minded voters to do the same. If enough of them collude, they might prevent C2 from being eliminated in the first round, causing C3 to be eliminated so that in the second round, with C2 picking up all the votes from C3, there will still be no winner and C will have the lowest vote count and be eliminated.
If 0.5% of the A or B voters implement this strategy, the IRV election would run:
First count, A:23.75%, B:23.75% (too close to call), C:22%, C2:15.3%, C3:15.2%
Status: no winner, C3 eliminated, C3 votes all go to C2.Second count, A:23.75%, B:23.75% (too close to call), C:22%, C2:30.5%
Status: no winner, C eliminated, C votes split among A,B,C2Polls are unclear here but all three remaining alternatives are expected to
pick up between 5-10%.At this stage, with C and C3 eliminated, it is unlikely that there will be a third count winner. But the key point is that both A and B are expected to be able to defeat C2. This means if either A or B is eliminated in the third stage, the remaining alternative will win in the fourth stage. And if by some chance C2 is eliminated, the final round will be between A and B, both of which Joey and friends prefer over all others.
The big problem with this scenario is the poll claim that A and B are frontrunners because they get the most votes in the first round. However, IRV is hard to predict and it is quite possible polling agencies might be wary of predicting beyond the first round when the elimination choice between C2 and C3 is so close.
In any event, I hope this is a reasonable illustration of the manipulability of IRV. (Of which I am not a fan.)
-
RE: Simulating Voting Strategies
Warren D. Smith's Range Voting paper (2000) and his C code simulation goes over a number of different voting systems and simulates both honest and "rational" ballots for many of the voting systems he covers. The 30 voting system and strategy permutations in the paper are: (In the paper, WDS starts his list with zero and the "as 25" strategy reference is "as 26")
- Honest range voting (scaled utility vote)
- Honest Borda
- Honest Condorcet Least-Reversal (CLR)
- Honest Coombs STV (most least-liked candid eliminated each round)
- Honest Hare Single Transferable Vote STV (least most-liked canddt eliminated)
- Honest Copeland (win most pairwise elections)
- Honest Dabagh point-and-a-half
- Honest Black (if no Condorcet winner use Borda)
- Honest Bucklin
- Honest plurality+runoff for 2 top finishers
- Honest plurality (1 vote for max-util canddt)
- Honest bullet (1 vote against min-util cand)
- Majority vote on random candidate pair
- Random "dictator" voter dictates winner
- Random winner
- Worst-summed-utility winner
- Honest approval (threshhold=avg canddt utility)
- Strategic range/approval (average of 2 frontrunner utils as thresh)
- Rational range/approval (threshhold=moving avg)
- Rational plurality (vote for 1 of 2 frontrnnrs)
- Strategic Borda I (1 frontrunner top, 1 bottom, rest recursively)
- Rational bullet (vote against 1 of 2 frontrnnrs)
- Strategic CLR (strat same as 25)
- Strategic Hare STV (strat same as 25)
- Rational Borda (1 frontrunner max, 1 min, rest using moving avg to decide if max or min vote)
- Strategic Coombs STV (strat same as 25)
- Strategic Borda II (1 frontrunner max, 1 min vote, rest honest)
- Rational Dabagh point-and-a-half (moving avg)
- Strategic Copeland (strat same as 25)
- Strategic Black (same strat as 25)
(A Google search for rangevote.pdf will get you to the paper. His c code is at: https://www.rangevoting.org/WarrenSmithPages/homepage/votetest2.c)
I hope this provides some good options for your strategy simulations.
--tec
-
RE: What Arrow's Impossibility Theorem Really Means
@BlainCellars the code I use is what I cobbled together since I started looking at voting systems and trying to figure out what worked best. Much of my work was done without consulting the (somewhat vast) literature on voting theory, and the tools and processes I used to help me think about things are all either free/open source or my own coding. This specific graphic was originally developed using Gnu Emacs with the svg package. Since the discussion code on this forum does not accept svg files, I used inkscape to convert the svg image into a png file.
More generally, when I started looking into the problem of voting I started with NetLogo because it provides an easy graphic display for agent-based models. Using NL, I could create and display 100 voter-agents randomly distributed in a 2D field, then create some alternatives for them to vote for under whatever system I was looking at. It worked great for a while, but as my questions got more involved, and my code-base became more extensive I realized I needed something a little more robust. I switched to Python because it allowed me to write tests for my code and make it more reliable.
At the moment my code is not well documented and is in need of refactoring. So while I can get it do to a number of interesting things I'm not sure how useful it would be to anyone else. On the other hand, I think it might be very useful for voting theorists to have easy access to spatial models. There is a data hierarchy to the various electorate models I've seen in recent voting theory papers. Tournaments have the least amount of data and have essentially eliminated the electorate altogether. Preference profiles have an electorate but lump voters together based on preference orders without any indication of the relative strength of individual voter preferences. Lists of individual voters with randomized utilities for each alternative allow some comparisons, but are still limited in that they really can't handle the addition of alternatives. Spatial models allow just about everything and are known to cover all possible tournaments, preference profiles, and utility models.
I'm assuming you have something in mind with your inquiry about programs. What are you looking for? Are you looking for images of electorates? Or do you want an election simulation environment for running tests and evaluations? I am thinking of putting my code on GitHub, but it will take a lot of work before it is ready for someone else to use. Are you looking for an answer to a specific need? Or are you willing to be an alpha-tester for a generic voting system evaluation framework? And more generally, would people such as the folks on this forum be interested in such an evaluation framework?
(This was a bigger answer than I suspect you wanted, but perhaps it will get us further in our collective quest for better collective decisions.)
-
What Arrow's Impossibility Theorem Really Means
Arrow's impossibility theorem is frequently cited in the discussion between ordinal and cardinal voting systems, with the idea that AIT only applies to ordinal voting systems. It is true that Arrow was only looking at ordinal systems, with the goal of a social welfare function (SWF) that took as input a collection of individual preference orders and returned a collective order. But what Arrow actually proved was his conditions were inconsistent. Specifically, his condition allowing voters to have unrestricted preference orders (citizen sovereignty or CS) is inconsistent with the idea that a majority preference of B over A would somehow be reversed by the introduction of some alternative C.
The Independence of Irrelevant Alternatives (IIA) condition seems reasonable at first glance. Yet there is a real question about what is meant by irrelevant. Ignoring ties, there are four possible states for an electorate preferring B over A created by the introduction of C, and at least two of them are highly relevant to the collective choice.
- When both B and A are preferred over C, there is no problem, and B remains the collective choice.
- When B is preferred over C and C is preferred over A, there is still no problem because B remains the collective choice.
- When C is preferred over both A and B, it can be argued that C is anything but irrelevant, and the collective choice should now be C.
- When A is preferred over C and C is preferred over B, the introduction of C creates a majority cycle. This is also extremely relevant because the cycle creates something like an equivalence class. This is a problem because the selection of any one of the three alternatives requires the SWF to reverse a known majority preference.
It is easy to come up with preference profiles that result in majority cycles, such as this one:
|-----------------+-------+-------+---------------+-------+-------| | voter region | order | count | voter region | order | count | |-----------------+-------+-------+---------------+-------+-------| | left top | A>B>C | 15 | right top (B) | B>A>C | 19 | | left middle (A) | A>C>B | 18 | right middle | B>C>A | 15 | | left bottom (C) | C>A>B | 15 | right bottom | C>B>A | 18 | |-----------------+-------+-------+---------------+-------+-------|
In this preference profile A is preferred over C by 52 to 48, C is preferred over B by 51 to 49, and B is preferred over A by 52 to 48. But just coming up with a preference profile doesn't really help us understand why the voters would have these preferences, or how common they might be in a real election.
To get a better sense of this type of cycle, it helps to put the election in some type of context. In this case, consider a group of 100 voters in a small community trying to determine a location for a common resource such as a cell tower. Each voter has an ideal location (gray dot) and their utility of the resource is inversely proportional to the distance the single tower will be from their ideal. The locations are indicated by labeled locations (black dots) A, B, and C. In the two images, the voters are positioned identically, and the indifference lines (perpendicular bisectors between each pair of alternatives) are also identical. The only difference is the alternatives in the right image have been moved closer to the center.
The first point I want to drive home here is that majority cycles are real and are the result of real voter utilities for the specific alternatives in the cycle. The voting method is irrelevant to the existence of cycles. When there is a cycle, the use of a cardinal voting method does not magically make that cycle go away.
The second point I'd like to make is that no voting system that tries to do everything in one or two rounds can pick a good collective alternative when all the alternatives are collectively bad. The differences between the alternatives in the left image and those in the right image are what drove me to work on iterative voting systems.