04.10.2015 Views

ECONOMY

Weingast - Wittman (eds) - Handbook of Political Ecnomy

Weingast - Wittman (eds) - Handbook of Political Ecnomy

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

donald g. saari 395<br />

desired A ∼ C ≻ B plurality ranking. (So, A and C each receive 3 of the vote, B<br />

8<br />

receives 2 .) These normalized plurality tallies require the normalized antiplurality<br />

tallies to satisfy 3 16 ≤ X ≤ 1 2 , 1 8 ≤ Y ≤ 1 2 , 3 16 ≤ Z ≤ 1 2 .TohavetheB ≻ C ≻ A<br />

8<br />

antiplurality outcome, let X = 3 16 , Z = 5 16 , Y = 8 . By plotting the (x, y, z) and<br />

16<br />

(X, Y, Z) point to create the procedure line, it follows that any supporting profile<br />

allows the six election rankings A ∼ C ≻ B, C ≻ A ≻ B, C ≻ A ∼ B, C ≻ B ≻ A,<br />

C ∼ B ≻ A, B ≻ C ≻ A.<br />

To construct a supporting profile, convert (x, y, z)and(X, Y, Z)tointegervalues<br />

where the integer antiplurality outcomes sum to twice the plurality outcomes. (This<br />

is because with the plurality and antiplurality votes, each voter casts, respectively, one<br />

and two points.) With our example, multiply the plurality outcome by its common<br />

denominator of eight to get (3, 2, 3), and the ( 3 16 , 8<br />

16 , 5 ) outcome by its common<br />

16<br />

denominator of 16 to obtain the desired (3, 8, 5). (This approach always works if<br />

the common denominator for the normalized antiplurality tally is twice that of the<br />

normalized plurality tally.)<br />

Now notice from Figure 22.1b that the s -coefficient for each candidate is the difference<br />

between her plurality and antiplurality tallies. So a profile satisfying our<br />

example defines the A, B, andC positional outcomes of 3 + s (3 − 3), 2+s (8 − 2),<br />

and 3 + s (5 − 3). These values are listed next to the appropriate Figure 22.2b vertex.<br />

Compute the a through f integervaluesinFigure22.2b as above; e.g. Ann’s tally<br />

of 3 + 0s =[a + b]+s [ f + c]. Ann has no “second-place votes,” so c = f =0. As<br />

Barb’s plurality vote is 2 = (e + f )and f =0,wehavethate = 2. Similarly, d =3.<br />

It remains to divide Ann’s a + b = 3 first-place votes to satisfy the s -coefficients for<br />

Barb and Connie: the only choice is a = 3. Thus, the eight-voter supporting profile<br />

for the example has three voters preferring A ≻ B ≻ C, two preferring B ≻ C ≻ A,<br />

and three preferring C ≻ B ≻ A.<br />

The missing technical condition is that a candidate’s s -coefficient cannot exceed<br />

the sum of the other two candidates’ plurality votes; e.g. as the s -coefficient comes<br />

from the other candidates’ first-place votes, there must be enough of them.<br />

This approach makes it easy to construct profiles to exhibit all sorts of interesting<br />

behavior. In practical terms, just draw a line in the triangle. Almost any line suffices:<br />

if the endpoints are close to the center, the above conditions will be satisfied. Often<br />

just the positioning of the procedure line suffices to discover conclusions; e.g. in this<br />

manner we now know the following. I leave the proofs to the reader; they just involve<br />

drawinganappropriatelineinanequilateraltriangle:<br />

For any ranking, there is a profile where all normalized positional outcomes agree<br />

and yield the selected ranking. (Select the normalized plurality and antiplurality<br />

points to be the same; the procedure line becomes a point where all normalized<br />

tallies agree.)<br />

Select any ranking for the plurality and for the antiplurality outcomes. There<br />

exists a profile with these outcomes. In fact, select any two different positional<br />

methods and any two ranking: there exists a profile so that the first rule’s<br />

outcome is the first ranking while the second rule’s outcome is the second<br />

ranking.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!