Warren D Smith | 20 Jun 2013 00:52
Picon

impossibility theorem for monetizing voting systems

http://rangevoting.org/MoneyImposs.html

now provides one (non-vague) formulation, with proof, of a
monetization impossibility theorem for voting.

 (The wording could use some polishing, but basically seems solid to me.
This probably will/should be merged into the previous
    http://rangevoting.org/MonetizedRV.html
and largely replace its section 13.)

Whereas previously I'd attacked certain monetization schemes, this theorem
now shows that NO monetization scheme even is possible that meets certain
optimality and reasonability criteria.

There are undoubtably other impossibility results lurking too, for
example the next target
would seem to be some theorem saying that, in some precise sense, even
approximate
optimality is unattainable (?).

[Note, the reason I am not sending this to E.Glen Weyl, is because of
the following message from him dated 18 june 2013:
"Warren,
I am unwilling to continue my communication with you. I hope you will
stop contacting me."]

--

-- 
Warren D. Smith
http://RangeVoting.org  <-- add your endorsement (by clicking
"endorse" as 1st step)
(Continue reading)

Abd ul-Rahman Lomax | 19 Jun 2013 22:23

Re: [CES #8848] Re: MAV on electowiki

At 12:33 PM 6/19/2013, Jameson Quinn wrote:
>My general response to Abd: a number of good points, and a number 
>where I'd disagree. Tough to respond to a kitchen-sink list, so I'll 
>try to prioritize. Unfortunately that means that things I don't 
>respond to could be either "you're right" or "I disagree but don't 
>think it's a productive argument".

Aw, we are building something. Some pieces may be incomplete, that's 
to be expected.

To keep this all in context, this is a discussion of an article:
http://wiki.electorama.com/w/index.php?title=Majority_Approval_Voting&oldid=10169

Current link (has been changed): 
http://wiki.electorama.com/wiki/Majority_Approval_Voting

I see and acknowledge that Jameson has already responded to certain 
comments of mine by editing the article accordingly. Now, to what he wrote:

>2013/6/19 Abd ul-Rahman Lomax 
><<mailto:abd <at> lomaxdesign.com>abd <at> lomaxdesign.com>
>...
>
>If one or more candidate has a majority, then the highest majority wins.
>
>
>Arrghh. That is ordinary Bucklin.
>
>
>Just for the first rank, because at that point there's no higher 
(Continue reading)

Jameson Quinn | 19 Jun 2013 19:33
Picon
Gravatar

Re: [CES #8845] Re: MAV on electowiki

My general response to Abd: a number of good points, and a number where I'd disagree. Tough to respond to a kitchen-sink list, so I'll try to prioritize. Unfortunately that means that things I don't respond to could be either "you're right" or "I disagree but don't think it's a productive argument".

2013/6/19 Abd ul-Rahman Lomax <abd <at> lomaxdesign.com>
...

If one or more candidate has a majority, then the highest majority wins.

Arrghh. That is ordinary Bucklin.

Just for the first rank, because at that point there's no higher rank to fall back to. 

At some point it must be specified how "rank overvotes" are handled. There are possible ways:

1. Ballot is voided. We don't like that!
2. Vote for candidate is voided. Also that is not great.
3. Highest rating marked counts. (This may have been traditional Bucklin. The instructions said "don't do it.")
4. Lowest rating marked counts.
5. Top and bottom ratings are averaged. (So a rating of A and B would give a rating that could be called A- or B+. GPA contribution 3.5.)

6. Vote counts for forming a majority at top rating, but doesn't count as "higher than" until you pass bottom rating. This is actually strategically attractive (if you were in a chicken dilemma, you could give the other side an honest B, but also a chicken-conservative D or even F, and that would basically be saying "I think playing chicken is silly but if it turns out I'm in the minority then game on"), in keeping with the spirit of the method, and in effect very similar to 5.

But I think that pre-specifying this is premature. These are implementation details, not part of the method.

I like the fifth option because it actually would allow voters to give an intermediate rating, thus providing some additional range resolution with no additional ballot complexity, but some cost in canvassing. That additional cost would be small, because most voters would not use it, most voters not needing it.

In amalgamation, then, as to rank, 3.5 would be added in after A but before B.

This would convert a Range 4 ballot to Range 8, with the penultimate bottom rating being missing, unless the bottom rating is explicit.


If not, votes at next grade down ("B") are added to each candidate's approval scores. If there are one or more candidates with a majority, the winner is whichever of those had more votes at higher grades (the previous stage). If there were no majorities, then the next grade down ("C") is added and the process repeats; and so on.

Note that if this process continues without a majority until the last grade ("F") is added, no new rules are needed.

This is technically correct, because the lowest grade amalgamation *must* show 100%. This assumes an F default, so marking of F is *irrelevant* except as a confirmation. 
If Fs are amalgamated with blanks not being treated as F, then F becomes a vote for the bottom-rating candidate. We don't want to create that confusion for a moment, even.

I agree that I should be more explicit about F default. 

For simplicity, dump the F rating entirely. It is assumed, an unexpressed default rank.
 
I strongly disagree that there should be no explicit F. As redundant as it seems to you, there are definitely voters who get satisfaction from explicitly voting against someone, and I would never design a survey where an explicit answer was always considered to connote more support than an implicit "no". 

MAV as a method should not specifically depend on the number of ratings.

Absolutely agree. I'll make that even more explicit.
 
MAV outside of a runoff system is a plurality method (as are all voting systems that can complete without an *explicit* approval of a majority of voters. In treating a midrange vote ("C", 2/4) as an approval, we have already stretched *slightly* beyond that. Taking this down more deeply into D/F waters is pretending a majority that doesn't exist.

OK, but in a non-runoff method, sometimes you'll elect without majority support, and it's still fair to say that D is better than F. 

I can see more complex amalgamation rules that could use the D ratings. The simplest rule, attempted here, doesn't cut it.

Any of those more complex rules is also trying to infer a majority from a plurality. They might sometimes do a slightly better job of that, but my feeling is that it's a false hope to think they'll always succeed, and so KISS.
 
 

 Since by that point all grades will have been counted, all candidate tallies will reach 100%.

In other words, amalgamating the F ratings is *useless*. This treats F as if it were a majority, it's a multiple majority, so *unconditionally* the previous ratings will be used and the F amalgamation will be ignored. So why do we even count it?

Just to make the system seem uniform all the way down?

As I've mentioned, the system should exist in two forms: plurality result, or runoff feeder (which, then, is also in two forms: conditional runoff and unconditional runoff. Unconditional runoff may be better handled with a different system, an explicitly multiwinner one, which has not yet been examined in detail.)


 The process above then naturally elects the candidate with the most approvals at the higher grades (D or above); that is, whichever has the fewest F's.

And I would say, fewest disapprovals, and disapproval includes D and F. It also includes blanks.

Great. Make your own, slightly more-complex system, and give it a different name.
 


 This is the best way to resolve such an election using only the information on the given ballots.

"Best" is a red flag word when it has not been clearly defined. You'd never be allowed to say "best" on Wikipedia, without that, and maybe even with it. That's called a "peacock word."

OK. A way. 

Why would MAV be any "better" than Bucklin?

Wait a minute. In this particular case, MAV and "Bucklin" (you mean, Grand Junction) do exactly the same thing: use second-to-bottom rank if there are no majorities. 

From the information on the ballots, the plurality winner in the majority-finding stage is arguably the "best winner." No, we support MAV because of the effect on strategic voting. If we have a Bucklin system with greater ballot resolution, MAV backup may be unnecessary. If voters are more informed, it may be unnecessary.

You seem to be under the impression that there's a difference between MAV and "Bucklin" in this case.
 

I am not satisfied that we have adequately examined the issues, to, yet, proclaim MAV as the "best" system up from pure Approval.

Nope. I am not sure it's "best", and don't really care. I know that the differences between Bucklin methods are tiny, yet we'll make no progress until we settle on one, simple method.
 

This point should be clearly made, though: MAV is Bucklin, with an exception only appearing in the handling of multiple majorities. Those will tend to be rare, because, more common, we can expect in some kinds of elections, will be majority failure.

How majority failure is handled is a classic problem. Robert's Rules' recommendation to organizations: Don't Do It! *Never* elect with a mere plurality. The version of IRV that they described *requires* a true majority (and even then, they point out the center squeeze problem.)

The backup concept, treating multiple majorities as possibly indicating over-rapid addition of approvals, is interesting, but looking at this is causing me to warm to a graduated median method.... plus pushing toward finer resolution, which will reduce the number of multiple majorities. *None of this is going to be fully satisfactory, because making a decision with a mere plurality is intrinsically problematic.*

Right. And the differences are slim. So let's keep debating these technical points among ourselves, but use common language in our activism. That's what this is about, principally.
 

What I *don't* like with MAV is that a large majority can be ignored vs a bare majority, based on the votes at the higher rating. Graduated median amalgamation can balance this.

Right. For honest votes, GMJ is clearly superior. See above for why I don't care.
 
But I have not seen a detailed examination of this issue, and it's important.

No, it isn't.
 
The MAV backup may be just a bit *too* simple. There is an alternative, as well, that would pick the candidate with the highest GPA. That would consider *all* the ratings. It's theoretically superior, because it would be Range. The D ratings would count.

Another approach would use pairwise comparison. We *do* have explicit approvals of a majority, if the median vote is C or higher. So, then the ballots would be recanvassed to see how the majority-approved candidates fare against each other. The collapsed approvals are separate again. This would make the method Condorcet-compliant, if I'm correct. And that would be a plus. I'm on board the concept that the Condorcet criterion is not absolute, because of social utility, but without explicit majority confirmation, I dislike finding *against* the preference of a majority.


 However, in this and other cases of multiple majorities, a runoff, if feasible, would be a better way to ensure a clean majority win.

It's a *way*. Not simply a "better" one. The alternative presented here is *not* a way to "ensure a clean majority win."

In my book, not putting your hand in a band saw is a "better" way not to cut it off. That is, "a way" is better than "not a way". 



This system was promoted and named due to the confusing array of Bucklin and Median proposals.

Premature. It has not been promoted. It has been *tentatively* named. This, by the way, would be in a History section of an article, and it only begins to tell the history.

 It is intended to be a relatively generic, simple Bucklin option with good resistance to the <http://wiki.electorama.com/wiki/Chicken_dilemma>chicken dilemma. It was named by a <http://lists.electorama.com/pipermail/election-methods-electorama.com/2013-June/031938.html>poll on the electorama mailing list in June 2013.

Geez, *recentism* to the 9s.

You know what I think about the "chicken dilemma." (Voting is not a game of chicken, and "dilemma" is merely an ordinary problem in strategy, which only afflicts a small segment of the population, the rest will simply *vote.*) What MAV will do is to, I expect, *slightly increase* the number of additional approvals, because they become *safer*, i.e., less likely to cause the loss of the favorite to the lower ranked candidate.

I prefer, Jameson, that the issue of the exact definition of MAV be *left open* for the time being. Let "Majority Approval Voting" actually be Supermajority Approval Voting," i.e, ultimately approved by a supermajority of voting systems activists.

Not as the "ideal voting system," which it is not, but as the "ideal next step beyond ordinary Approval, in a plurality context." It introduces a ranked/rated ballot. It's simple to amalgamate and understand. In most elections, the "tiebreaker" procedure is not activated. Indeed, in most elections under some fairly common conditions, there will be majority *failure*, not the multiple majorities that the backup procedure handles.

The grades or ranks for this system could be numbers instead of letter grades. Terms such as "graded MAV" or "rated MAV" can be used to distinguish these possibilities if necessary. In either case, descriptive labels for the ratings or grades are recommended. For instance, for the letter grades:
   * A: Unconditional support
   * B: Support if there are no other majorities above "C"
   * C: Support if there are no other majorities above "D"
   * D: Oppose unless there are no other majorities at all.
   * F: Unconditional opposition.
This treats D as an approval, so it divides the approved categories into four rather than the three from Bucklin. We will need, ultimately, a single, coherent, simple system to propose and try. Notice that the definitions treat not-oppose as support. In my analysis of the traditional Bucklin ballot, it's clear that the 3rd rank was *minimum approval.* The ordinary meaning of a grade of "D" is a kind of failure.

In most schools, you can pass with a "D".
 

This is a *really complicated* explanation of the rating levels.

It's also accurate. 

As the above labels indicate, support at the middle grades or ratings is not partial, as in <http://wiki.electorama.com/wiki/Score_voting>Score voting, but conditional.

That is correct. If the method terminates above the rating, it is not used. That, by the way, is a flaw, from a social utility point of view. I don't like that voters may be casting votes that are not counted. I'm starting to think toward lines of using range amalgamation in the "tiebreaker." And of suggesting that all votes be counted, even if only for reporting. Incubator effect.

Count and report all grades: of course.
Votes counting fully is a flaw: It gives less social utility for honest votes, but by doing less to encourage exaggerated votes, it could result in better information and thus better social utility overall. That is the basic premise of median versus average. Like it or not, that is what MAV gives you. And MAV can do a lot better at giving that than "maybe we should do this, or maybe that, no wait I just thought of another thing..."
 


 That is, the typical ballot will still count fully for or against a given candidate.

Yeah. But I want to see a much more detailed analysis of this.


The different grade levels are a way to help the voting system figure out how far to extend that support so that some candidate gets a majority.

Uh, really? It's more like "so that majority support is found if possible from the votes."

OK, sure.
 
And a D vote is *not* "support." It might be a weak stand-aside. "Okay, if the rest of you insist, this one is better than that one." A strong stand-aside would be a C vote. In consider C as neutral, as to preference strength. So-so. Not good, not bad. "Passing," but barely. No honors. But ... might be serviceable.


For a strategic voter, the most important ratings are the top ("A"), second-to-bottom ("D"), and bottom ("F").

"Most important" is, again, Peacock. Here, Jameson, you are giving your own analysis, not the community's analysis.

OK. Section name: "Preliminary and tentative strategic analysis".
 
This is not a signed article, even if your name is in the History. If you want to present your own analysis, *attribute it.* Or attribute analysis to others. I suggest not presenting your own opinions as if they were fact. Sometimes in writing Wikipedia articles, I'd use "weasel words." This is weak language, like, "Some say that ...." or "It could be claimed that ...." or "According to some sources, ...." I really only did that to find quick consensus, not to propose weasel language as stable or desirable. It was typically replacing *strong language* that did not actually reflect consensus.


A typical zero-knowledge strategy would be to give the best 30% of candidates an "A", the next 25% a "D", and the bottom 45% an "F".

"Typical" according to what standard? What population? I would *not* think this way *at all.*

"Strategic" means at a minimum "game-theoretic equilibrium". Your suggestion is certainly not that, so it is not "strategic", it is "honest".
 
I would cast a Range ballot, period, using the same strategy, i.e., considering what I know of the preferences of others. With Bucklin, I can vote sincerely for my favorite under almost all conditions, and the loss of voting power is miniscule. If it's a zero-knowledge situation, I'd vote simple, normalized Range. I'm really not worried about the multiple majority problem. My votes will represent *true preference strength*. That only shifts with knowledge of the electorate, where I will then vote Von Neumann - Morgenstern utilities. I.e., to put it simply, which will powerfully choose between realistic possibilities, reserving *some voting power* for the expression of true preference, which is an independent value. (And where partisan elections are involved, that has a long-term effect. I am not just concerned about the *present election.*)

Great analysis of why an honest vote is a good idea in this system. 

Some voting systems activists seem to think that voters are obsessed with "winning," but that all that "winning" means to them is getting their favorite elected. No, many voters consider it a "win" if the winner has broad support, *even if they were personally opposed.*


If the typical "honest" voter roughly calibrates their grades to an academic curve, with a median vote at "B" or "C", then strategic and honest votes will mesh well.

Perhaps. All this is vague, ungrounded argument. We don't have the simulations yet.


For instance, if candidates can differ on two dimensions, ideology and quality, and voters are normally distributed along the one dimension of ideology (with all voters preferring highest quality), then this system will tend to elect the candidate preferred by the median voter, that is, the one with the smallest sum of quality deficit plus ideological skew; and this tendency will hold for any unbiased combination of "honest" and "strategic" voters as defined above.

Jameson, you are presenting as if it were fact, your "back of the envelope" conclusions. Please don't do that!


The assertions in the strategic paragraph are based on some back-of-the-envelope diagrams; that is, I consider them likely to be true, but I have not run simulations to prove them. I think it would be interesting to do so. Would others be as interested as I would in such results; that is,

"In the opinion of Jameson Quinn ...."

Or, "As shown in a poll conduced by the Center for Election Science....."


1. Finding an equilibrium zero-knowledge strategy (percentile-grade correspondence) in impartial culture. (I think this would be an exciting new direction for simulation research.)

I want to see Bucklin applied again, because the ballots will be collecting Range data, not only for its value as a voting system.

The true revolutionary system is Asset, of course. It sweeps all these concerns aside, makes them moot.


2. Finding how broad the strategic conditions are (testing different "honest" grade distributions, unbiased strat/hon mixes, and strategic biases) in which MAV elects the median voter's favorite in the 2D/1D model sketched above? If my intuition is right, this model (unlike sparse or impartial models as criticized by Regenwetter) will allow good systems to show near-optimal BR; so MAV and Score will be have nearly the same (and nearly 0) honest BR, and the differences will be in that BR's robustness to different strategic profiles.

I'm suspecting that a different tiebreaker rule can do better. A Range rule would *explicitly* maximize BR, as to what was expressed. Runoff systems, of course, are known to take us beyond single-ballot Range as to BR optimization with realistic votes.


Jameson

2013/6/18 Jameson Quinn <<mailto:jameson.quinn <at> gmail.com>jameson.quinn <at> gmail.com>

I've reworked the description. See what you think.


2013/6/18 Abd ul-Rahman Lomax <<mailto:abd <at> lomaxdesign.com>abd <at> lomaxdesign.com>

At 04:25 PM 6/18/2013, Juho Laatu wrote:
I quickly read the article. Here are some observations.

- Term "Bucklin system" has not been defined. I can guess that it probably refers to Bucklin style stepwise addition of new approvals, but that may not be as obvious to all readers. If there is no definition of "Bucklin system", maybe one could say "As in Bucklin" instead of "As with any Bucklin system".


There is a link to Bucklin voting in the article.


- Sentence "if there are more than one with a majority, the "B" votes are removed and the highest sub-majority wins" is ambigious in the sense that it is not clear if "highest sub-majority" refers to all candidates or to candidates that had majority after adding the "B" votes.


It's poorly worded, all right. Minor point: "There are more than one" grates. (I find the use of the singular or plural with "more" to be ambiguous. I'd avoid it.)

An example is given when the principle has not been stated.

The method does not make sense as stated. The "back-up" is a tie-breaker, considering multiple majorities as if they were ties. They *are* ties in median vote. The tie-breaker only selects a member of the tied set.

Something went south. What was proposed was a Bucklin system. Bucklin does use, I've suggested, a range ballot, but the way that it does this is with a ranked structure. I ran into this when trying to design a set of votes to show a problem that I have not seen examined.

The description on the wiki page makes the system seem more complex than it is.

It's been designed to be five-rank, with explicit F. That's a fish bicycle. "No support" means merely "no support." No vote. Introducing the D vote is a later possible reform, it is an unapproved category. It makes the ballot considerably more complex, and the explanation is more complex.

*D: Oppose unless there are no other majorities at all.


Is that clear? I don't think so. Bucklin as Approval Voting doesn't have a "disapproved rank." All blanks are disapproved.


- It is not quite clear what happens and if it is possible that there is no majority after the "F" votes have been counted.


The F votes are never counted, first of all. Listing them is a mistake. (If the F votes continued the amalgamation, then someone would be voting *for* a candidate rated F. That was the intention for the D rating.

It is far better, however, to introduce a D rating in combination with a runoff system, where the D rating could improve runoff candidate selection.

When a voter rates a candidate as "D", they are opposing the election of that candidate.

The Bucklin system required amalgamating three ranks. It's looking like MAV requires five, but that could be reduced to four, but the whole idea here was to have a *simple* next step beyond basic Approval Voting, and, as well, a clear similar method for use in a runoff system.

(We basically need a step up from approval as a plurality method, and from approval as a primary method in a runoff system.)


- The grades could be letters or numbers, but they could also be e.g. columns without any letter or number. This part of text discusses what the ballots might look like. I'm not sure if ballot different ballot formats should be seen as an essential part of the method definition, or if the method should be defined abstractly without referring to what the actual ballots might look like. I tend to define the methods abstractly without assuming anything on the ballots, and then discuss possible ballot formats as a separate topic, but I'm not saying that's the only and best approach. The current text is thus ok. I just first read the grades of the definition as abstract grades, not as definitions on what would be written in the ballots.


*Something* should be on the ballot that expresses the *function* of a vote. Jameson took this concept from me. A voter should be able to see the ballot and have a reasonably clear idea, just from it, what the vote *means* ... and the meaning is the *effect* that the vote causes.

The original Bucklin ballot, however, simply instructed voters to mark "1st choice," "2nd choice," or '3rd choice." The googlebooks copy is unclear, <http://books.google.com/books?id=QcIqAAAAYAAJ&pg=RA1-PA757&dq=The+Grand+Junction+plan+of+city+government+and+its+results&hl=en&ei=uOTdS7aFKMKclgfq9739Cg&sa=X&oi=book_result&ct=result&resnum=3&ved=0CDsQ6AEwAg#v=onepage&q=The%20Grand%20Junction%20plan%20of%20city%20government%20and%20its%20results&f=false>http://books.google.com/books?id=QcIqAAAAYAAJ&pg=RA1-PA757&dq=The+Grand+Junction+plan+of+city+government+and+its+results&hl=en&ei=uOTdS7aFKMKclgfq9739Cg&sa=X&oi=book_result&ct=result&resnum=3&ved=0CDsQ6AEwAg#v=onepage&q=The%20Grand%20Junction%20plan%20of%20city%20government%20and%20its%20results&f=false


Page 95. It looks like they actually instructed people to vote for all but one. But that part is quite unclear. In the first set of instructions, at the top of the ballot, they did suggest not voting for one candidate. There may be another copy of this ballot somewhere. Bucklin was widely covered.

MAV *assumes that voters err if they approve two candidates by a majority.* That's why it backs up. But what, indeed, if it backs up and the multiple majority candidates are not the plurality winner in the previous round? What if there are *no* votes for those candidates in that round, or the vote is small.


It said: "


- The linked definition of "evaluatve" says that ranked systems can not give same ratings to two candidates. I think that's confusing and wrong.

Juho


Well, that's a common assumption of "ranked systems." It's essentially a definition, which is why we have said that Bucklin is *not* a ranked system. But, really, it's a ranked system that allows equal ranking. (Original Bucklin allowed equal ranking in the third rank only. We have simple expanded the approval principle to all ranks. *That is a convenience to voters.*)


----
Election-Methods mailing list - see <http://electorama.com/em>http://electorama.com/em for list info



--
You received this message because you are subscribed to the Google Groups "The Center for Election Science" group.
To unsubscribe from this group and stop receiving emails from it, send an email to electionscience+unsubscribe <at> googlegroups.com.
For more options, visit <https://groups.google.com/groups/opt_out>https://groups.google.com/groups/opt_out.



--
You received this message because you are subscribed to the Google Groups "The Center for Election Science" group.
To unsubscribe from this group and stop receiving emails from it, send an email to electionscience+unsubscribe <at> googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



----
Election-Methods mailing list - see http://electorama.com/em for list info
Abd ul-Rahman Lomax | 19 Jun 2013 19:51

Re: [CES #8844] Vague impossibility conjecture for monetizing voting systems

At 11:27 AM 6/19/2013, Warren D Smith wrote:
>  CONJECTURE that no good monetization scheme can exist for
>any reasonable voting system in large elections...
>
>I have stated such a conjecture and sketched a proof (which is not a
>real proof) of this impossibility conjecture here:
>     http://rangevoting.org/MonetizedRV.html#monetfails

Vague is an understatement. Start with "good" being undefined. On the 
page, it becomes "reasonable," which merely papers over the lack of 
precision, and precision is essential to proofs. (However, Warren 
does, above, notice that it is not a "real proof." It's really just a 
collection of anti-monetization arguments.)

The core argument is that, allegedly, the cost of voting will be so 
high that most people won't vote. That is *not* an argument against 
the system. People who don't vote don't participate, have no cost, 
and have no benefit. However, the assumption that "poor people" would 
not vote is just that, an assumption. Poll taxes, as Warren has 
pointed out, are unconstitutional in the U.S., in general.

However, it is possible to have monetized voting without poll taxes. 
I proposed an approach, which would involve allowing every voter a 
default, base sum that they can spend as they choose, on their votes. 
This sum might be small, say $1, but it would allow these people to 
vote. Adding weight to the vote by adding more money is really no 
different, in substance, from spending money on campaigns, simply more direct.

Now, such a system might not be accepted, and may not even be worth 
proposing, for that reason, but that is *not* an impossibility 
argument, it's a logistical, practical argument.

The default amount allowed citizens would be adjustable. It might be 
more than $1. The vote might include a designation of a *specific 
charity* to which a refund would be donated, if refunds were below 
some value. Otherwise the "poor voter," might get a check. Notice: if 
they vote in such a way as to get a check, they are voting *against 
their own interest*. Rather, they get a check, sensibly, if they vote 
according to their own personal value in the election, and they get 
the compensation if the result is different. It works.

In *some contexts*, this kind of voting might make sense. In some 
contexts, there is no restriction on poll taxes. A charity might run 
a poll as to how to distribute donations, among legitimate charitable 
purposes, consistent with the purpose and management of the charity, 
and the poll might be weighted by donation. The basic "donation" 
could be the membership dues for the organization. That gives the 
voter the right to vote. And then the voter can offer conditional 
donations for specific causes. If the voter "loses," the voter might 
get an additional amount to be used for voting in future elections; 
essentially, they would not have "spent" their donated funds. So 
this, then, shades into the time-cumulative methods, being more 
specific with easy bookkeeping. It's possible to design the system to 
be workable and practical. 

----
Election-Methods mailing list - see http://electorama.com/em for list info

Abd ul-Rahman Lomax | 19 Jun 2013 19:32

Re: [CES #8843] Re: MAV on electowiki

I don't want to continue carping about the article because I'm not 
ready to write one myself. So this is just how it occurs to me, quickly.

Link to the article itself:

At 07:48 AM 6/19/2013, Jameson Quinn wrote:
>Here's the current version of the article. Note the new paragraph on 
>strategy at the bottom.
>
>Majority Approval Voting (MAV) is a modern, 
><http://wiki.electorama.com/wiki/Evaluative>evaluative version of 
><http://wiki.electorama.com/wiki/Bucklin_voting>Bucklin voting.

Note that Bucklin was *partially evaluative.* That is, in original 
Bucklin, the first and second ranks were *exclusive*. Drop the third 
rank from the ballot, it was purely a ranked system. The third rank 
allowed multiple approvals. So the full ballot can be seen as an 
approval ballot, and approval is an evaluative system. The approved 
candidates are then categorized.

The system described as MAV currently defines *four* approved 
categories. "F" is described as an explicit category, when that, 
itself, creates problems.

>  Voters rate each candidate into one of a predefined set of ratings 
> or grades, such as the letter grades "A", "B", "C", "D", and "F". 
> As with any Bucklin system, first the top-grade ("A") votes for 
> each candidate are counted as approvals.

It should be completely explicit that multiple candidates may be 
categories in all categories, i.e., this is Bucklin-ER, basically.

>If one or more candidate has a majority, then the highest majority wins.

Arrghh. That is ordinary Bucklin.

Rather, "If, at a stage of counting, one and only one candidate has 
obtained a majority (having approval from more than half of the 
voters), that candidate wins."

Majority must be specified or someone might think it is "majority of 
the votes," and there will normally be more votes than voters in 
systems like this.

At some point it must be specified how "rank overvotes" are handled. 
There are possible ways:

1. Ballot is voided. We don't like that!
2. Vote for candidate is voided. Also that is not great.
3. Highest rating marked counts. (This may have been traditional 
Bucklin. The instructions said "don't do it.")
4. Lowest rating marked counts.
5. Top and bottom ratings are averaged. (So a rating of A and B would 
give a rating that could be called A- or B+. GPA contribution 3.5.)

I like the fifth option because it actually would allow voters to 
give an intermediate rating, thus providing some additional range 
resolution with no additional ballot complexity, but some cost in 
canvassing. That additional cost would be small, because most voters 
would not use it, most voters not needing it.

In amalgamation, then, as to rank, 3.5 would be added in after A but before B.

This would convert a Range 4 ballot to Range 8, with the penultimate 
bottom rating being missing, unless the bottom rating is explicit.

>If not, votes at next grade down ("B") are added to each candidate's 
>approval scores. If there are one or more candidates with a 
>majority, the winner is whichever of those had more votes at higher 
>grades (the previous stage). If there were no majorities, then the 
>next grade down ("C") is added and the process repeats; and so on.
>
>Note that if this process continues without a majority until the 
>last grade ("F") is added, no new rules are needed.

This is technically correct, because the lowest grade amalgamation 
*must* show 100%. This assumes an F default, so marking of F is 
*irrelevant* except as a confirmation. If Fs are amalgamated with 
blanks not being treated as F, then F becomes a vote for the 
bottom-rating candidate. We don't want to create that confusion for a 
moment, even.

For simplicity, dump the F rating entirely. It is assumed, an 
unexpressed default rank.

MAV as a method should not specifically depend on the number of 
ratings. MAV outside of a runoff system is a plurality method (as are 
all voting systems that can complete without an *explicit* approval 
of a majority of voters. In treating a midrange vote ("C", 2/4) as an 
approval, we have already stretched *slightly* beyond that. Taking 
this down more deeply into D/F waters is pretending a majority that 
doesn't exist.

I can see more complex amalgamation rules that could use the D 
ratings. The simplest rule, attempted here, doesn't cut it.

>  Since by that point all grades will have been counted, all 
> candidate tallies will reach 100%.

In other words, amalgamating the F ratings is *useless*. This treats 
F as if it were a majority, it's a multiple majority, so 
*unconditionally* the previous ratings will be used and the F 
amalgamation will be ignored. So why do we even count it?

Just to make the system seem uniform all the way down?

As I've mentioned, the system should exist in two forms: plurality 
result, or runoff feeder (which, then, is also in two forms: 
conditional runoff and unconditional runoff. Unconditional runoff may 
be better handled with a different system, an explicitly multiwinner 
one, which has not yet been examined in detail.)

>  The process above then naturally elects the candidate with the 
> most approvals at the higher grades (D or above); that is, 
> whichever has the fewest F's.

And I would say, fewest disapprovals, and disapproval includes D and 
F. It also includes blanks.

>  This is the best way to resolve such an election using only the 
> information on the given ballots.

"Best" is a red flag word when it has not been clearly defined. You'd 
never be allowed to say "best" on Wikipedia, without that, and maybe 
even with it. That's called a "peacock word."

Why would MAV be any "better" than Bucklin? From the information on 
the ballots, the plurality winner in the majority-finding stage is 
arguably the "best winner." No, we support MAV because of the effect 
on strategic voting. If we have a Bucklin system with greater ballot 
resolution, MAV backup may be unnecessary. If voters are more 
informed, it may be unnecessary.

I am not satisfied that we have adequately examined the issues, to, 
yet, proclaim MAV as the "best" system up from pure Approval.

This point should be clearly made, though: MAV is Bucklin, with an 
exception only appearing in the handling of multiple majorities. 
Those will tend to be rare, because, more common, we can expect in 
some kinds of elections, will be majority failure.

How majority failure is handled is a classic problem. Robert's Rules' 
recommendation to organizations: Don't Do It! *Never* elect with a 
mere plurality. The version of IRV that they described *requires* a 
true majority (and even then, they point out the center squeeze problem.)

The backup concept, treating multiple majorities as possibly 
indicating over-rapid addition of approvals, is interesting, but 
looking at this is causing me to warm to a graduated median 
method.... plus pushing toward finer resolution, which will reduce 
the number of multiple majorities. *None of this is going to be fully 
satisfactory, because making a decision with a mere plurality is 
intrinsically problematic.*

What I *don't* like with MAV is that a large majority can be ignored 
vs a bare majority, based on the votes at the higher rating. 
Graduated median amalgamation can balance this. But I have not seen a 
detailed examination of this issue, and it's important. The MAV 
backup may be just a bit *too* simple. There is an alternative, as 
well, that would pick the candidate with the highest GPA. That would 
consider *all* the ratings. It's theoretically superior, because it 
would be Range. The D ratings would count.

Another approach would use pairwise comparison. We *do* have explicit 
approvals of a majority, if the median vote is C or higher. So, then 
the ballots would be recanvassed to see how the majority-approved 
candidates fare against each other. The collapsed approvals are 
separate again. This would make the method Condorcet-compliant, if 
I'm correct. And that would be a plus. I'm on board the concept that 
the Condorcet criterion is not absolute, because of social utility, 
but without explicit majority confirmation, I dislike finding 
*against* the preference of a majority.

>  However, in this and other cases of multiple majorities, a runoff, 
> if feasible, would be a better way to ensure a clean majority win.

It's a *way*. Not simply a "better" one. The alternative presented 
here is *not* a way to "ensure a clean majority win."

>This system was promoted and named due to the confusing array of 
>Bucklin and Median proposals.

Premature. It has not been promoted. It has been *tentatively* named. 
This, by the way, would be in a History section of an article, and it 
only begins to tell the history.

>  It is intended to be a relatively generic, simple Bucklin option 
> with good resistance to the 
> <http://wiki.electorama.com/wiki/Chicken_dilemma>chicken dilemma. 
> It was named by a 
>
<http://lists.electorama.com/pipermail/election-methods-electorama.com/2013-June/031938.html>poll 
> on the electorama mailing list in June 2013.

Geez, *recentism* to the 9s.

You know what I think about the "chicken dilemma." (Voting is not a 
game of chicken, and "dilemma" is merely an ordinary problem in 
strategy, which only afflicts a small segment of the population, the 
rest will simply *vote.*) What MAV will do is to, I expect, *slightly 
increase* the number of additional approvals, because they become 
*safer*, i.e., less likely to cause the loss of the favorite to the 
lower ranked candidate.

I prefer, Jameson, that the issue of the exact definition of MAV be 
*left open* for the time being. Let "Majority Approval Voting" 
actually be Supermajority Approval Voting," i.e, ultimately approved 
by a supermajority of voting systems activists.

Not as the "ideal voting system," which it is not, but as the "ideal 
next step beyond ordinary Approval, in a plurality context." It 
introduces a ranked/rated ballot. It's simple to amalgamate and 
understand. In most elections, the "tiebreaker" procedure is not 
activated. Indeed, in most elections under some fairly common 
conditions, there will be majority *failure*, not the multiple 
majorities that the backup procedure handles.

>The grades or ranks for this system could be numbers instead of 
>letter grades. Terms such as "graded MAV" or "rated MAV" can be used 
>to distinguish these possibilities if necessary. In either case, 
>descriptive labels for the ratings or grades are recommended. For 
>instance, for the letter grades:
>    * A: Unconditional support
>    * B: Support if there are no other majorities above "C"
>    * C: Support if there are no other majorities above "D"
>    * D: Oppose unless there are no other majorities at all.
>    * F: Unconditional opposition.
This treats D as an approval, so it divides the approved categories 
into four rather than the three from Bucklin. We will need, 
ultimately, a single, coherent, simple system to propose and try. 
Notice that the definitions treat not-oppose as support. In my 
analysis of the traditional Bucklin ballot, it's clear that the 3rd 
rank was *minimum approval.* The ordinary meaning of a grade of "D" 
is a kind of failure.

This is a *really complicated* explanation of the rating levels.

>As the above labels indicate, support at the middle grades or 
>ratings is not partial, as in 
><http://wiki.electorama.com/wiki/Score_voting>Score voting, but conditional.

That is correct. If the method terminates above the rating, it is not 
used. That, by the way, is a flaw, from a social utility point of 
view. I don't like that voters may be casting votes that are not 
counted. I'm starting to think toward lines of using range 
amalgamation in the "tiebreaker." And of suggesting that all votes be 
counted, even if only for reporting. Incubator effect.

>  That is, the typical ballot will still count fully for or against 
> a given candidate.

Yeah. But I want to see a much more detailed analysis of this.

>The different grade levels are a way to help the voting system 
>figure out how far to extend that support so that some candidate 
>gets a majority.

Uh, really? It's more like "so that majority support is found if 
possible from the votes." And a D vote is *not* "support." It might 
be a weak stand-aside. "Okay, if the rest of you insist, this one is 
better than that one." A strong stand-aside would be a C vote. In 
consider C as neutral, as to preference strength. So-so. Not good, 
not bad. "Passing," but barely. No honors. But ... might be serviceable.

>For a strategic voter, the most important ratings are the top ("A"), 
>second-to-bottom ("D"), and bottom ("F").

"Most important" is, again, Peacock. Here, Jameson, you are giving 
your own analysis, not the community's analysis. This is not a signed 
article, even if your name is in the History. If you want to present 
your own analysis, *attribute it.* Or attribute analysis to others. I 
suggest not presenting your own opinions as if they were fact. 
Sometimes in writing Wikipedia articles, I'd use "weasel words." This 
is weak language, like, "Some say that ...." or "It could be claimed 
that ...." or "According to some sources, ...." I really only did 
that to find quick consensus, not to propose weasel language as 
stable or desirable. It was typically replacing *strong language* 
that did not actually reflect consensus.

>A typical zero-knowledge strategy would be to give the best 30% of 
>candidates an "A", the next 25% a "D", and the bottom 45% an "F".

"Typical" according to what standard? What population? I would *not* 
think this way *at all.* I would cast a Range ballot, period, using 
the same strategy, i.e., considering what I know of the preferences 
of others. With Bucklin, I can vote sincerely for my favorite under 
almost all conditions, and the loss of voting power is miniscule. If 
it's a zero-knowledge situation, I'd vote simple, normalized Range. 
I'm really not worried about the multiple majority problem. My votes 
will represent *true preference strength*. That only shifts with 
knowledge of the electorate, where I will then vote Von Neumann - 
Morgenstern utilities. I.e., to put it simply, which will powerfully 
choose between realistic possibilities, reserving *some voting power* 
for the expression of true preference, which is an independent value. 
(And where partisan elections are involved, that has a long-term 
effect. I am not just concerned about the *present election.*)

Some voting systems activists seem to think that voters are obsessed 
with "winning," but that all that "winning" means to them is getting 
their favorite elected. No, many voters consider it a "win" if the 
winner has broad support, *even if they were personally opposed.*

>If the typical "honest" voter roughly calibrates their grades to an 
>academic curve, with a median vote at "B" or "C", then strategic and 
>honest votes will mesh well.

Perhaps. All this is vague, ungrounded argument. We don't have the 
simulations yet.

>For instance, if candidates can differ on two dimensions, ideology 
>and quality, and voters are normally distributed along the one 
>dimension of ideology (with all voters preferring highest quality), 
>then this system will tend to elect the candidate preferred by the 
>median voter, that is, the one with the smallest sum of quality 
>deficit plus ideological skew; and this tendency will hold for any 
>unbiased combination of "honest" and "strategic" voters as defined above.

Jameson, you are presenting as if it were fact, your "back of the 
envelope" conclusions. Please don't do that!

>The assertions in the strategic paragraph are based on some 
>back-of-the-envelope diagrams; that is, I consider them likely to be 
>true, but I have not run simulations to prove them. I think it would 
>be interesting to do so. Would others be as interested as I would in 
>such results; that is,

"In the opinion of Jameson Quinn ...."

Or, "As shown in a poll conduced by the Center for Election Science....."

>1. Finding an equilibrium zero-knowledge strategy (percentile-grade 
>correspondence) in impartial culture. (I think this would be an 
>exciting new direction for simulation research.)

I want to see Bucklin applied again, because the ballots will be 
collecting Range data, not only for its value as a voting system.

The true revolutionary system is Asset, of course. It sweeps all 
these concerns aside, makes them moot.

>2. Finding how broad the strategic conditions are (testing different 
>"honest" grade distributions, unbiased strat/hon mixes, and 
>strategic biases) in which MAV elects the median voter's favorite in 
>the 2D/1D model sketched above? If my intuition is right, this model 
>(unlike sparse or impartial models as criticized by Regenwetter) 
>will allow good systems to show near-optimal BR; so MAV and Score 
>will be have nearly the same (and nearly 0) honest BR, and the 
>differences will be in that BR's robustness to different strategic profiles.

I'm suspecting that a different tiebreaker rule can do better. A 
Range rule would *explicitly* maximize BR, as to what was expressed. 
Runoff systems, of course, are known to take us beyond single-ballot 
Range as to BR optimization with realistic votes.

>Jameson
>
>2013/6/18 Jameson Quinn 
><<mailto:jameson.quinn <at> gmail.com>jameson.quinn <at> gmail.com>
>I've reworked the description. See what you think.
>
>
>2013/6/18 Abd ul-Rahman Lomax 
><<mailto:abd <at> lomaxdesign.com>abd <at> lomaxdesign.com>
>At 04:25 PM 6/18/2013, Juho Laatu wrote:
>I quickly read the article. Here are some observations.
>
>- Term "Bucklin system" has not been defined. I can guess that it 
>probably refers to Bucklin style stepwise addition of new approvals, 
>but that may not be as obvious to all readers. If there is no 
>definition of "Bucklin system", maybe one could say "As in Bucklin" 
>instead of "As with any Bucklin system".
>
>
>There is a link to Bucklin voting in the article.
>
>
>- Sentence "if there are more than one with a majority, the "B" 
>votes are removed and the highest sub-majority wins" is ambigious in 
>the sense that it is not clear if "highest sub-majority" refers to 
>all candidates or to candidates that had majority after adding the "B" votes.
>
>
>It's poorly worded, all right. Minor point: "There are more than 
>one" grates. (I find the use of the singular or plural with "more" 
>to be ambiguous. I'd avoid it.)
>
>An example is given when the principle has not been stated.
>
>The method does not make sense as stated. The "back-up" is a 
>tie-breaker, considering multiple majorities as if they were ties. 
>They *are* ties in median vote. The tie-breaker only selects a 
>member of the tied set.
>
>Something went south. What was proposed was a Bucklin system. 
>Bucklin does use, I've suggested, a range ballot, but the way that 
>it does this is with a ranked structure. I ran into this when trying 
>to design a set of votes to show a problem that I have not seen examined.
>
>The description on the wiki page makes the system seem more complex 
>than it is.
>
>It's been designed to be five-rank, with explicit F. That's a fish 
>bicycle. "No support" means merely "no support." No vote. 
>Introducing the D vote is a later possible reform, it is an 
>unapproved category. It makes the ballot considerably more complex, 
>and the explanation is more complex.
>
>*D: Oppose unless there are no other majorities at all.
>
>
>Is that clear? I don't think so. Bucklin as Approval Voting doesn't 
>have a "disapproved rank." All blanks are disapproved.
>
>
>- It is not quite clear what happens and if it is possible that 
>there is no majority after the "F" votes have been counted.
>
>
>The F votes are never counted, first of all. Listing them is a 
>mistake. (If the F votes continued the amalgamation, then someone 
>would be voting *for* a candidate rated F. That was the intention 
>for the D rating.
>
>It is far better, however, to introduce a D rating in combination 
>with a runoff system, where the D rating could improve runoff 
>candidate selection.
>
>When a voter rates a candidate as "D", they are opposing the 
>election of that candidate.
>
>The Bucklin system required amalgamating three ranks. It's looking 
>like MAV requires five, but that could be reduced to four, but the 
>whole idea here was to have a *simple* next step beyond basic 
>Approval Voting, and, as well, a clear similar method for use in a 
>runoff system.
>
>(We basically need a step up from approval as a plurality method, 
>and from approval as a primary method in a runoff system.)
>
>
>- The grades could be letters or numbers, but they could also be 
>e.g. columns without any letter or number. This part of text 
>discusses what the ballots might look like. I'm not sure if ballot 
>different ballot formats should be seen as an essential part of the 
>method definition, or if the method should be defined abstractly 
>without referring to what the actual ballots might look like. I tend 
>to define the methods abstractly without assuming anything on the 
>ballots, and then discuss possible ballot formats as a separate 
>topic, but I'm not saying that's the only and best approach. The 
>current text is thus ok. I just first read the grades of the 
>definition as abstract grades, not as definitions on what would be 
>written in the ballots.
>
>
>*Something* should be on the ballot that expresses the *function* of 
>a vote. Jameson took this concept from me. A voter should be able to 
>see the ballot and have a reasonably clear idea, just from it, what 
>the vote *means* ... and the meaning is the *effect* that the vote causes.
>
>The original Bucklin ballot, however, simply instructed voters to 
>mark "1st choice," "2nd choice," or '3rd choice." The googlebooks 
>copy is unclear, 
><http://books.google.com/books?id=QcIqAAAAYAAJ&pg=RA1-PA757&dq=The+Grand+Junction+plan+of+city+government+and+its+results&hl=en&ei=uOTdS7aFKMKclgfq9739Cg&sa=X&oi=book_result&ct=result&resnum=3&ved=0CDsQ6AEwAg#v=onepage&q=The%20Grand%20Junction%20plan%20of%20city%20government%20and%20its%20results&f=false>http://books.google.com/books?id=QcIqAAAAYAAJ&pg=RA1-PA757&dq=The+Grand+Junction+plan+of+city+government+and+its+results&hl=en&ei=uOTdS7aFKMKclgfq9739Cg&sa=X&oi=book_result&ct=result&resnum=3&ved=0CDsQ6AEwAg#v=onepage&q=The%20Grand%20Junction%20plan%20of%20city%20government%20and%20its%20results&f=false
>
>Page 95. It looks like they actually instructed people to vote for 
>all but one. But that part is quite unclear. In the first set of 
>instructions, at the top of the ballot, they did suggest not voting 
>for one candidate. There may be another copy of this ballot 
>somewhere. Bucklin was widely covered.
>
>MAV *assumes that voters err if they approve two candidates by a 
>majority.* That's why it backs up. But what, indeed, if it backs up 
>and the multiple majority candidates are not the plurality winner in 
>the previous round? What if there are *no* votes for those 
>candidates in that round, or the vote is small.
>
>
>It said: "
>
>
>- The linked definition of "evaluatve" says that ranked systems can 
>not give same ratings to two candidates. I think that's confusing and wrong.
>
>Juho
>
>
>Well, that's a common assumption of "ranked systems." It's 
>essentially a definition, which is why we have said that Bucklin is 
>*not* a ranked system. But, really, it's a ranked system that allows 
>equal ranking. (Original Bucklin allowed equal ranking in the third 
>rank only. We have simple expanded the approval principle to all 
>ranks. *That is a convenience to voters.*)
>
>
>----
>Election-Methods mailing list - see 
><http://electorama.com/em>http://electorama.com/em for list info
>
>
>
>--
>You received this message because you are subscribed to the Google 
>Groups "The Center for Election Science" group.
>To unsubscribe from this group and stop receiving emails from it, 
>send an email to electionscience+unsubscribe <at> googlegroups.com.
>For more options, visit 
><https://groups.google.com/groups/opt_out>https://groups.google.com/groups/opt_out.
>
>

----
Election-Methods mailing list - see http://electorama.com/em for list info

Warren D Smith | 19 Jun 2013 18:27
Picon

Vague impossibility conjecture for monetizing voting systems

 CONJECTURE that no good monetization scheme can exist for
any reasonable voting system in large elections...

I have stated such a conjecture and sketched a proof (which is not a
real proof) of this impossibility conjecture here:
    http://rangevoting.org/MonetizedRV.html#monetfails

Probably a proof in full generality is not possible, but I'm pretty
sure it is possible to do better than I've done so far.  You might
want to think about this, it would be a pretty interesting
impossibility theorem.
----
Election-Methods mailing list - see http://electorama.com/em for list info

Abd ul-Rahman Lomax | 19 Jun 2013 04:50

Re: [CES #8834] Upper-Bucklin naming (was: Median systems, branding....)

At 02:42 PM 6/18/2013, Jameson Quinn wrote:
>New running tally, including Andy Jennings's 
>latest votes (which went out on only one of the 
>lists). Current voting tallies in parentheses, 
>ordered JQ/AL/RB/AJ/DSH/BG/BRG. Options have 
>been placed in descending order, which I expect to be stable from here on.
>
>Abd: please vote on MAV, MSV, CAV, AAV, and CSV.

My votes are the second in each list.

Majority Approval Voting: (A/B/C/A/A/D/B) Median: 
B, votes above: 3. PROBABLE WINNER.

Additive Approval Voting: (B/C/B/C/B/E/B) Median: B, votes above: 0

Descending Approval Threshold Voting: 
(A/B-/B/C/C/F/A) Median B-; votes above B, 2.

Cumulative Approval Voting: (A/C/B/C/D/A/F) Median C; votes above: 3
Majority Support Voting: (B/D/C/A/C/D/B) Median C; votes above: 3

Instant Runoff Approval Voting: (B/A/F/C/F/F/C) Median C; votes above: 2
Cumulative Support Voting: (A/C/B/C/F/C/F) Median C; votes above: 2

>I am happy with how this went. There are still 
>details we haven't come to consensus on — such 
>as the numbers of and labels for rating 
>categories — but I am comfortable with leaving 
>those unspecified, and allowing each advocate to specify them if they want to.
>
>Abd: I understand that you favor the "runoff" 
>terminology. However, the IRAV proposal lost 
>convincingly. If you have any further issues to 
>discuss, please pose them (along with your votes as requested above).

Well, I could have shifted the DAT vote to tie 
with MAV.... However, the particular system is 
DAT with a backup as needed to avoid a multiple 
majority. MAV represents that. I'm still 
uncomfortable with the *method*, i.e., with 
dumping the principle of preponderance of the 
votes in the case of a multiple majority, and we 
have seen inadequate discussion of that./

>I would happily have submitted to the majority 
>here on even a name I didn't personally like.

>  I hope that, at least on these lists, we can 
> begin to come together to use MAV as the 
> representative Bucklin proposal, and stop 
> pushing our own individual variants like "GMJ" or "ER-Bucklin".

I can appreciate the intention, but not the push. 
The Approval Voting consensus arose rather 
naturally, this seems to have been rushed. What's the hurry?

I see a place for using different names in 
different contexts, and do not see that "one size fits all."

MAV -- I'm happy to use that name for a defined 
method, and will leave the "grade" issue for 
later -- sacrifices utility maximization for some 
increased level of LnH protection. I *do* think 
it's an interesting idea, but would greatly 
prefer to resolve the problem with real runoffs, 
*whenever* the votes show the lack of a clear majority *choice.*

----
Election-Methods mailing list - see http://electorama.com/em for list info

Jameson Quinn | 18 Jun 2013 22:44
Picon
Gravatar

MAV on electowiki

http://wiki.electorama.com/wiki/Majority_Approval_Voting

Please help build up the article and work on the clearest consensus wording. This article is all my own voice so far; my goal is for it not to be.

Jameson
----
Election-Methods mailing list - see http://electorama.com/em for list info
Abd ul-Rahman Lomax | 18 Jun 2013 20:52

Re: Participation Criteria and Bucklin - perhaps they *can* work together after all?

At 03:58 PM 6/17/2013, Chris Benham wrote:
>Benjamin,
>The criterion ("criteria" is the plural) you suggest is not new. It 
>is called Mono-add-Top, and comes from Douglas Woodall.
>
>It is met by IRV and MinMax(Margins) but is failed by Bucklin. In my 
>opinion IRV is the best of the methods that meet it.
>
>26: A>Y>X
>25: B>Y>X
>17: C>D>X
>17: E>F>X
>17: G>H>X
>
>The majority threshold is 51 and X wins in the third round. But if 
>we add anywhere between 3 and 100
>X>Y ballots then Y wins in the second round.

Some error there. Total votes are 102. Majority is 52 votes. I just 
want it to be noticed how *crazy* this scenario is. Voting systems 
criteria can be like that. A totally insane situation, won't happen 
in a real election in a billion years, can be asserted to cause 
criterion failure. There is no *evaluation*, no consideration of harm 
or effect on social utility, just a raw definition of a criterion and 
an example showing failure. Or, sometimes, a proof that failure is 
not possible (with *any* scenario).

The deeper analysis is much more difficult. What are the conditions 
that allow mono-add-top failure? In the example above, X wins without 
the additional votes because X is the *unanimous* third choice of all 
the voters, while being the first or second choice of none. That's, 
for starters, preposterously unlikely. However, a somewhat more 
realistic version could be constructed.

The ballots that then shift the win to Y cross a minimal majority 
threshold for Y in the second round (With the 3 votes additional, 53 
votes is majority, so this would need to be two votes, not three).

I have generally suggested that in studying criteria performance that 
overall social utility be considered. Because Bucklin, especially 
Bucklin-ER -- which this election could be -- uses a Range ballot, 
that's what makes strategic voting sense -- it is possible to 
estimate social utility performance. In a hybrid system, which is 
what I've been coming to highly recommend as a more sophisticated 
reform, social utility and the Condorcet criterion can be tested, and 
problems, conflicts, can easily be handled with a runoff, and if the 
runoff *is the general election*, then the primary method is merely a 
nomination device. If the primary method never *eliminates* a 
Condorcet winner, then the overall method can fairly be considered 
Condorcet-compliant, with the final application of the criterion 
being *in the general election*. I.e., the Condorcet winner will win, 
*unless* the voters vary and that preference is not maintained. That 
pairwise majority will know the situation from the primary. How will they vote?

Now, X is the *social utility winner* if this is Bucklin. The voting 
pattern does not reflect -- at all -- real voting behavior with 
Bucklin, which we know. Many or even most voters will bullet vote. 
The frontrunners are A and B. A and B voters are unlikely to add 
lower preferences in second rank, in fact, they many not add them at 
all. And all of this reveals problems with the majority criterion and 
the multiple majority criterion.

I have pointed out that Bucklin uses a Range ballot to control voting 
in a series of approval elections. That is, the optimal Bucklin 
ballot will show utilities for candidates, as to those within the 
approved set, those where the voter is at all willing to support the 
candidate, to approve the candidate, and thus cause the election. 
Here, a deeper preference is revealed in the third rank. What does 
this do to a social utility estimate:

     4 3 2
26: A>Y>X
25: B>Y>X
17: C>D>X
17: E>F>X
17: G>H>X
---
102 voters, max score 408

Totals, as percentage of maximum possible (i.e, 4 points per voter 
per candidate)

A: 25.4%
B: 24.5%
C,E,G: 16.7%
Y: 37.5%
D,F,H: 12.5%
X: 50%

X is *obviously* the social utility winner. However, that's a wimpy 
decision, 50% of maximum range. Voting third rank in Bucklin is *bare 
minimum approval,* which is why I interpret it as 50% range.

Now, we add

2: X>Y

The two votes, when the second rank is amalgamated, lead to 53 votes 
for Y, a bare majority, Y wins, in the second round, with only 2 
votes for X at that level. That's because Bucklin collapses to 
approval voting as higher ranks fail to find a majority. A and B are 
still two votes short of a majority. However, the full ballots show a 
different story.

In this case, the two additional votes caused a bare majority to 
appear in the second round, thus concealing the *full approval* for X 
that only comes up in the third round.

Notice that the A,B voters also approve Y, all of them. None of them 
approve each other. These votes, as far as I can tell, make no sense, 
they are preposterously unreal. While I can easily create preference 
profiles that match the votes -- they would be these preferences 
translated into Bucklin votes, which are then Range 4 utilities -- 
the voters are *uncorrelated* with each other, and are behaving as if 
purely and completely isolated. It's as if they don't follow the same 
media, and are, as it were, from different planets. Yet they are 
organized into clear factions, and that high level of organization is 
what allows this criterion failure to appear.

Bucklin amalgamation is not perfect for social utility. Rather, it's 
following a somewhat different principle, the seeking of majority 
approval. I agree that the process here is interesting, and the 
hybrid methods I suggest would detect the SU maximizer. They would 
*not* award the win based on that; rather, the presence of such a 
beats-all winner (X is pairwise approved over all other candidates, 
plus X is the SU winner from the Bucklin ballots interpreted as Range 
ballots), or even simply one that beats the otherwise-winner, would 
trigger a runoff.

Who would the runoff candidates be? First of all, this ballot is the 
truncated Range 4 ballot of Bucklin. I'd suggest a complete Range 
ballot, not truncated. However, dealing with just the example before 
us, I'd suggest:

X, the SU maximizer and Condorcet winner.
Y, the Bucklin winner otherwise.

A and B voters have all settled on Y as second choice, and the SU 
figures show that. That is a weak preference expression, so we can 
assume that the A and B voters will be satisfied with the runoff as a 
choice. Nodoby is likely to be seriously dissatisfied if they voted sincerely.

----
Election-Methods mailing list - see http://electorama.com/em for list info

Abd ul-Rahman Lomax | 18 Jun 2013 18:56

Re: Participation Criteria and Bucklin - perhaps they *can* work together after all?

At 03:41 PM 6/17/2013, Jameson Quinn wrote:
>2013/6/17 Abd ul-Rahman Lomax 
><<mailto:abd <at> lomaxdesign.com>abd <at> lomaxdesign.com>
>At 01:23 PM 6/17/2013, Jameson Quinn wrote:
>
>2013/6/17 Benjamin Grant <<mailto:benn <at> 4efix.com>benn <at> 4efix.com>
>
>Is *this* an example of Bucklin failing Participation?
>
>5: A>B>C
>
>4: B>C>A
>
>A wins
>
>Right
>
>But add these in:
>
>2: C>A>B
>
>  B wins.
>
>
>Yes, with your "tiebreaker".
>
>
>This is not participation failure. Adding ballots ranking C highest 
>did not cause C to lose.
>
>
>Abd, you're wrong. Adding B>A ballots caused A to lose; that is a 
>participation failure.

I did err in my analysis. However, I would urge anyone tempted to 
write "you are wrong" to be very careful. It's a big red flag that 
one is, oneself, making some mistake. Would we not expect the 
addition of B>A ballots to have the possibility of causing A to lose?

No, the added ballots were A>B ballots, at a lower ranking. The 
failure comes from causing majority failure, thus pulling in deeper votes.

I had somehow failed to notice the B votes from the 5 voters. A wins 
in the first round without the added votes, with a simple majority. 
This is the  sequence, which Jameson did not explore specifically, 
merely stating his result.

>>5: A>B>C
>>
>>4: B>C>A
>>
>>A wins
>>
>>Right
>>
>>But add these in:
>>
>>2: C>A>B
>>
>>  B wins.

A wins in the 9-voter case, by a simple majority. However, the 
11-voter case has a new majority requirement, 6 votes instead of 5.

We have the situation here that a majority favoring A votes second 
rank for B. In Range equivalents, often proposed as examples of "bad 
Range behavior," we see the same kind of phenomenon asserted.

Under straight Bucklin, if there are two frontrunners, A and B, we 
would expect *very few* additional votes for B, because the election 
is very likely to reduce, then, to A vs B. So this is like examples 
of alleged majority criterion failure based on the majority 
suppressing its preference by voting for another candidate, who gets 
a greater majority once they do that.

First round: (majority is 6)
A:5, B:4, C:2

Second round:
A: 7, B:9, C:6

*All three candidates have a majority?* Who is the ideal winner of 
this election? The A voters elected to vote A>B rather than A>.>B or 
just A. The only reason B can win is because they set it up. By 
second-ranking B, which indicates weak preference, they gave the 
election to B. The C voters merely opened that box.

The back-up Bucklin system under discussion would still award the 
victory to A, because there was more than one majority, so the result 
would back up to the first rank and A would still win. Is that a 
desired result, or otherwise?

What do we see here WRT utilities? First of all, I don't know what is 
really meant by the .>.>X preferences? Are there more than three 
candidates in this election? Are those actually approvals? If so, 
every voter ultimately approved every candidate. Jameson and another 
seemed to assume Bucklin votes from a preference order, which is naive.

That's why I suggested that these might have been written the way 
below, if they were *not* approvals, i.e, if the third rank shown was 
the *worst* rating. Yeah, in analyzing ranked voting systems, this is 
common practice, to give the complete rankings. But Bucklin is *not* 
a simple ranked system, it uses an Range ballot, in the traditional 
form, with the range only covering the approved categories. You 
cannot translate sincere preferences to Bucklin votes, especially 
Bucklin-ER. There are *families* of sincere votes.

So Bucklin votes, perhaps:

5: A>B
4: B>C

If this is 3-rank Bucklin (standard), then the voters also had X>.>Y 
possibilities, or bullet votes. If they second-rank a candidate, that 
indicates *weak preference*. Bucklin analysis here only looks at the 
first rank, because a majority is found there.

Range analysis gives me this:

9-voter election
5: A,4; B,3
4: B,4; C,3

So full range analysis: A,20; B,31; C,12.

So the A win is actually weak, mere majority criterion compliant, an 
example of the failure of the majority criterion! This election is 
then *vulnerable* to more voter participation, and that is what happens.

5: A>B
4: B>C
2: C>A

This vote expresses, by default, A>B. However, the *primary 
expression* is a vote for C. The A vote is a subsidiary preference. 
Are these weak or strong preferences (Bucklin allows four levels of 
preference strength, i.e., a Range increment of 4, 3, 2, or 1. The 
voters here all elected to express weak preference with the top two 
and strong preference with the third candidate.)

5: A,4; B,3
4: B,4; C,3
2: C,4; A,3

A,26; B, 31; C, 20

B is *still the utility optimizer.*

Yes, there is technical participation failure. 2 votes that did 
express, as a lower preference, A>B, did cause A to lose to B.

Will the C voters be upset? On the face, yes. They got C, the worst 
candidate, because they voted. However, what they really did was to 
trigger a deeper consideration, that revealed that B was the more 
widely preferred candidate. This would have been a case where voting 
A=C would have made much more sense.

*Multiple majorities* were not common with Bucklin. It's a problem 
where there is an abrupt introduction of many additional approvals. 
In the system above, we get a *triple majority.* That is a sign of 
weak preferences, as expressed. It could be naive voters, note that 
the *majority of voters in the 9-candidate election* first or 
second-rank the true utility winner. Bucklin simply doesn't consider 
that, because of the prior majority. I've argued that, in a two-round 
Bucklin system, it should.

I have pointed out that multiple majorities indicate that the 
majority *may not have made a choice,* and I've suggested that these 
go to a runoff. The backup method, where a multiple majority backs up 
to the previous rank and goes for the plurality winner there (among 
the majority-approved set), seems to solve the problem. The C winners 
will be happy with that, A will win.

*However,* social utility took a whack! Thus, I would suggest, a 
runoff election between A and B would resolve the issue, clearly. 
Contrary to what may voting systems analysts have expected, A will 
not necessarily win. The C voters, in particular, may have less 
motivation to vote. The A voters may decide that they prefer to find 
closer to unanimity, they have weak preference, and that's what real 
people do in small-group social dynamics. The majority has a 
*choice,*  now narrowed and uncomplicated by the presence of C.

The C voters may be unhappy, but the B voters are pleased, and there 
are more of them. As to maximimum displeasure with the result, if A 
wins, we have 4 seriously unhappy, and if B wins, we have 2. This 
assumes sincere votes, under the Bucklin system, which *only allows approvals.*

In that system, if the A voters had voted A>.>B, say, or A only, A 
could win both ways. Those voters elected to vote as they did. (Of 
course, this was a made-up scenario, but in making it up, were the 
options open to the A voters considered? As well, what about the C 
voters? If the system allows them to vote A=C, why didn't they vote 
that way? They'd have gotten A, no problem.)

Once we realize the possibility of two-round elections, with the 
primary being exactly that, a primary election to choose general 
election candidates, these issues resolve. The general election will 
have wider participation. It can and should use an advanced voting 
system. Certainly it should *allow* multiple approvals. But Bucklin 
still allows favorite expression.

I *do* want to allow voters to vote sincere preferences, like the C 
voters. The problem only arises because of multiple majorities, and 
the presence of a true utility optimizer, apparently, with the C 
voters causing majority failure in the first rank and thus a deeper look.

----
Election-Methods mailing list - see http://electorama.com/em for list info

Benjamin Grant | 18 Jun 2013 15:04
Gravatar

HELP: Re: inline replies and Outlook 201x

OK, I have been dealing with a huge issue, and that is using Outlook to perform inline replies.

 

When, for example, Jameson Quinn sends a long and nuance post to the list, and I want to reply to it, the only method of reply I want to use in the inline method.  That means that I post a chunk of his message, then my reply, then another chunk, then my reply to that, and so on, like this:

 

(example)

 

Jameson Chunk 1

Benn reply 1

 

Jameson Chunk 2

Benn Reply 2

 

Jameson Chunk 3

Benn Reply 3

 

…and so on.

 

The ONLY way this works without becoming unintelligible is if it is easily visually apparent as one scans down my reply which sections are the original chunk (to which I am replying) and which sections are my new additions to the conversation, my replies.

 

Outlook 2013 is frustrating me to no END in this regard.

 

However, let me be 100% clear – switching from Outlook to another product is not an option.  I depend on Outlook in a myriad of ways I do not want to get into here, but for better or worse, I *will* be using Outlook.

 

My question is this: Is there any *good* way to configure or use Outlook so that I can do my inline replies on this list, and all of you can easily visually determine which parts of the reply I am quoting (the “chunks”) and which I am newly creating (my replies), without it being a huge pain in my rear, such as hand editing line by line?  Do any of you have ANY advice?  My greatest fear is that if I don’t fix this issue, the inline replies I send to the list will go largely unanswered because they will be largely unintelligible.

 

Thanks.

 

PS. I guess I *could* insert some kind of macroed out lines like “****BEGIN QUOTED TEXT*****” and “****END QUOTED TEXT****” but honestly, even that won’t work at all, because while that might work the first time, what happens when a thread goes back and forth a couple five times – it will already be populated with those markers, rendering new markers lost in a sea of noise.  This is a HARD problem to solve, but unless I do, I may as well be typing gibberish!  Argh!  Help? 

 

PPS.  I *have* done a few hours of googling on this problem, but haven’t yet found a silver bullet.  I am hoping that you guys have some fresh, good ideas?

 

-Benn Grant

eFix Computer Consulting

benn <at> 4efix.com

603.283.6601

 

----
Election-Methods mailing list - see http://electorama.com/em for list info

Gmane