election-methods@mailman.electorama.com

Technical discussion of election methods

View all threads

Trying to have CD, protect strong top-set, and protect middle candidates too

FS
Forest Simmons
Sun, Nov 20, 2016 12:31 AM

I'm sure it was intentionally subtle, but not too subtle, by Brams or
Fishburn, either one or both.

On Sat, Nov 19, 2016 at 4:08 PM, Michael Ossipoff email9648742@gmail.com
wrote:

On Sat, Nov 19, 2016 at 6:37 PM, Forest Simmons fsimmons@pcc.edu wrote:

No hurry.  Let's give it some time, and if it survives scrutiny

Sure, and it seems to be surviving scrutiny better than anything else so
far.

, we can call it by a descriptive title or the VOBS (Venzke Ossipoff
Benham Simmons) method, like they do in physics.

It's true that progress is ultimately collaborative, but of course
eventually one individual notices, finds, puts together the as-yet
un-noticed possibility that is hiding in the discussion, and people
particularly take note of that final arrival at a goal.

We might have to change the order of the initials to avoid tempting
people to call it the "Very Old BS method."

In a debate between Brams (or Fishburn) and the Saari, main Borda
advocate, the Approval advocate called Borda "the Borda System (BS)", and
referred to it as BS throughout the discussion
.
Michael Ossipoff

On Sat, Nov 19, 2016 at 2:08 PM, Michael Ossipoff <email9648742@gmail.com

wrote:

It seems to me that this is the method that you'd rather have named
after you, if it meets FBC, CD, Mono-Add-Plump, and resists truncation &
burial.

Michael Ossipoff

On Sat, Nov 19, 2016 at 4:49 PM, Michael Ossipoff <
email9648742@gmail.com> wrote:

Well, this looks like the sought-after method that meets FBC & CD, and
has wv strategy.  ...and without a major criticism.

My first impression is that MDDA(pt/2) would be easier to explain &
propose.

Thanks for what seems to be the method with the sought-after
properties-combination!

Michael Ossipoff

On Fri, Nov 18, 2016 at 6:56 PM, Forest Simmons fsimmons@pcc.edu
wrote:

Does optional approval cutoff wreck burial protection?

Suppose we have a sincere scenario

40 C>B
35 A>B
25 B>C

and the C faction decides to bury the CWs B.  The B faction
anticipates this and responds by truncating C.  It is in the interest of
the A faction to leave the default implicit approval cutoff in place.  The
C faction doesn't want to give A too much support so they use the explicit
cutoff option:

40 C>>A
35 A>B
25 B

The approval winner is B the CWs.

If they left the implicit cutoff in place it would be worse for them;
their last choice would be elected.

So I think MDDA with optional explicit cutoff is fine with respect to
truncation and burial.

How about the CD?

In this case the sincere profile is

40 C
35 A>B
25 B>A

The B>A faction threatens to defect from the AB coalition.
The A faction responds by using the explicit cutoff:

40 C
35 A>>B
25 B

The approval winner is C, so the threatened defection back-fires.

It seems to me like that is plenty of chicken defection insurance.

The obvious equilibrium position (for the chicken scenario) is

40 C
35 A>>B
25 B>>A

Under MDDA(pt/2) the only uneliminated candidate is A.

But if the B faction defects, all candidates are eliminated, and the
approval winner C is elected.

This is why I like MDDA(pt/2).

An interesting fact is that MDDA(pt/2) is just another formulation of
my version of ICA.  They are precisely equivalent.  Here's why:

In my version of ICA, X beats Y iff

[X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words,

[X>Y] > [Y:>=X] - [X=Y=Bottom],

which in turn equals

100% - [X>Y] - [X=Y=Bottom], since  100%= [X>Y] + [Y>=X].

So X beats Y iff

[X>Y] > 100% - [X>Y] - [X=Y=Bottom].

If you add [X.Y] to both sides and divide by 2, you get

[X>Y] +[X=Y=Bottom]/2 > 50%,

precisely the "majority-with- half-power-truncation" rule.

So (my version of) ICA is precisely equivalent to MDDA(pt/2).

I believe it to be completely adequate for defending against burial,
truncation, and Chicken Defection.

Now suppose that p<q<r, and p+q+r=100%, and we have three factions of
respective sizes p, q, and r:, with r + q > 50%.

p: C
q: A>>B
r: B>>A

Then under the pt/2 rule both C and B are eliminated, but not A, so A
is elected.

Suppose that the B factions defects.

Then A is also eliminated, and the approval winner C is elected.

Etc.

So which of the two equivalent formulations is easier to sell?  ICA or
MDDA(pt/2) ?

Forest

I'm sure it was intentionally subtle, but not too subtle, by Brams or Fishburn, either one or both. On Sat, Nov 19, 2016 at 4:08 PM, Michael Ossipoff <email9648742@gmail.com> wrote: > > > On Sat, Nov 19, 2016 at 6:37 PM, Forest Simmons <fsimmons@pcc.edu> wrote: > >> No hurry. Let's give it some time, and if it survives scrutiny >> > > Sure, and it seems to be surviving scrutiny better than anything else so > far. > > >> , we can call it by a descriptive title or the VOBS (Venzke Ossipoff >> Benham Simmons) method, like they do in physics. >> > > It's true that progress is ultimately collaborative, but of course > eventually one individual notices, finds, puts together the as-yet > un-noticed possibility that is hiding in the discussion, and people > particularly take note of that final arrival at a goal. > > >> >> We might have to change the order of the initials to avoid tempting >> people to call it the "Very Old BS method." >> > > In a debate between Brams (or Fishburn) and the Saari, main Borda > advocate, the Approval advocate called Borda "the Borda System (BS)", and > referred to it as BS throughout the discussion > . > Michael Ossipoff > > > > >> >> On Sat, Nov 19, 2016 at 2:08 PM, Michael Ossipoff <email9648742@gmail.com >> > wrote: >> >>> It seems to me that _this_ is the method that you'd rather have named >>> after you, if it meets FBC, CD, Mono-Add-Plump, and resists truncation & >>> burial. >>> >>> Michael Ossipoff >>> >>> >>> On Sat, Nov 19, 2016 at 4:49 PM, Michael Ossipoff < >>> email9648742@gmail.com> wrote: >>> >>>> Well, this looks like the sought-after method that meets FBC & CD, and >>>> has wv strategy. ...and without a major criticism. >>>> >>>> My first impression is that MDDA(pt/2) would be easier to explain & >>>> propose. >>>> >>>> Thanks for what seems to be the method with the sought-after >>>> properties-combination! >>>> >>>> Michael Ossipoff >>>> >>>> On Fri, Nov 18, 2016 at 6:56 PM, Forest Simmons <fsimmons@pcc.edu> >>>> wrote: >>>> >>>>> Does optional approval cutoff wreck burial protection? >>>>> >>>>> Suppose we have a sincere scenario >>>>> >>>>> 40 C>B >>>>> 35 A>B >>>>> 25 B>C >>>>> >>>>> and the C faction decides to bury the CWs B. The B faction >>>>> anticipates this and responds by truncating C. It is in the interest of >>>>> the A faction to leave the default implicit approval cutoff in place. The >>>>> C faction doesn't want to give A too much support so they use the explicit >>>>> cutoff option: >>>>> >>>>> 40 C>>A >>>>> 35 A>B >>>>> 25 B >>>>> >>>>> The approval winner is B the CWs. >>>>> >>>>> If they left the implicit cutoff in place it would be worse for them; >>>>> their last choice would be elected. >>>>> >>>>> So I think MDDA with optional explicit cutoff is fine with respect to >>>>> truncation and burial. >>>>> >>>>> How about the CD? >>>>> >>>>> In this case the sincere profile is >>>>> >>>>> 40 C >>>>> 35 A>B >>>>> 25 B>A >>>>> >>>>> The B>A faction threatens to defect from the AB coalition. >>>>> The A faction responds by using the explicit cutoff: >>>>> >>>>> 40 C >>>>> 35 A>>B >>>>> 25 B >>>>> >>>>> The approval winner is C, so the threatened defection back-fires. >>>>> >>>>> It seems to me like that is plenty of chicken defection insurance. >>>>> >>>>> The obvious equilibrium position (for the chicken scenario) is >>>>> >>>>> 40 C >>>>> 35 A>>B >>>>> 25 B>>A >>>>> >>>>> Under MDDA(pt/2) the only uneliminated candidate is A. >>>>> >>>>> But if the B faction defects, all candidates are eliminated, and the >>>>> approval winner C is elected. >>>>> >>>>> This is why I like MDDA(pt/2). >>>>> >>>>> An interesting fact is that MDDA(pt/2) is just another formulation of >>>>> my version of ICA. They are precisely equivalent. Here's why: >>>>> >>>>> In my version of ICA, X beats Y iff >>>>> >>>>> [X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words, >>>>> >>>>> [X>Y] > [Y:>=X] - [X=Y=Bottom], >>>>> >>>>> which in turn equals >>>>> >>>>> 100% - [X>Y] - [X=Y=Bottom], since 100%= [X>Y] + [Y>=X]. >>>>> >>>>> So X beats Y iff >>>>> >>>>> [X>Y] > 100% - [X>Y] - [X=Y=Bottom]. >>>>> >>>>> If you add [X.Y] to both sides and divide by 2, you get >>>>> >>>>> [X>Y] +[X=Y=Bottom]/2 > 50%, >>>>> >>>>> precisely the "majority-with- half-power-truncation" rule. >>>>> >>>>> So (my version of) ICA is precisely equivalent to MDDA(pt/2). >>>>> >>>>> I believe it to be completely adequate for defending against burial, >>>>> truncation, and Chicken Defection. >>>>> >>>>> >>>>> Now suppose that p<q<r, and p+q+r=100%, and we have three factions of >>>>> respective sizes p, q, and r:, with r + q > 50%. >>>>> >>>>> p: C >>>>> q: A>>B >>>>> r: B>>A >>>>> >>>>> Then under the pt/2 rule both C and B are eliminated, but not A, so A >>>>> is elected. >>>>> >>>>> Suppose that the B factions defects. >>>>> >>>>> Then A is also eliminated, and the approval winner C is elected. >>>>> >>>>> Etc. >>>>> >>>>> So which of the two equivalent formulations is easier to sell? ICA or >>>>> MDDA(pt/2) ? >>>>> >>>>> Forest >>>>> >>>> >>>> >>> >> >
MO
Michael Ossipoff
Sun, Nov 20, 2016 7:42 AM

Voting, using this method, I might often want to deny approval to a
high-ranked candidate (even top?), without denying to the rest of my
ranking, approval & full protection from burial & truncation.

Maybe I just don't trust to voters of an excellent candidate whom I rank
high, but I have no reason to not want to protect the rest of my ranking
from burial or truncation by my unranked candidates' voters.

So I suggest that, in addition to an approval cutoff, a voter should also
be able to individually deny approval to any individual candidate(s).

It's probably impossible in principle, with any possible method, to both
protect from chicken-defection by a candidate's voters, and also give hir
full truncation & burial protection.

Michael Ossipoff

On Fri, Nov 18, 2016 at 6:56 PM, Forest Simmons fsimmons@pcc.edu wrote:

Does optional approval cutoff wreck burial protection?

Suppose we have a sincere scenario

40 C>B
35 A>B
25 B>C

and the C faction decides to bury the CWs B.  The B faction anticipates
this and responds by truncating C.  It is in the interest of the A faction
to leave the default implicit approval cutoff in place.  The C faction
doesn't want to give A too much support so they use the explicit cutoff
option:

40 C>>A
35 A>B
25 B

The approval winner is B the CWs.

If they left the implicit cutoff in place it would be worse for them;
their last choice would be elected.

So I think MDDA with optional explicit cutoff is fine with respect to
truncation and burial.

How about the CD?

In this case the sincere profile is

40 C
35 A>B
25 B>A

The B>A faction threatens to defect from the AB coalition.
The A faction responds by using the explicit cutoff:

40 C
35 A>>B
25 B

The approval winner is C, so the threatened defection back-fires.

It seems to me like that is plenty of chicken defection insurance.

The obvious equilibrium position (for the chicken scenario) is

40 C
35 A>>B
25 B>>A

Under MDDA(pt/2) the only uneliminated candidate is A.

But if the B faction defects, all candidates are eliminated, and the
approval winner C is elected.

This is why I like MDDA(pt/2).

An interesting fact is that MDDA(pt/2) is just another formulation of my
version of ICA.  They are precisely equivalent.  Here's why:

In my version of ICA, X beats Y iff

[X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words,

[X>Y] > [Y:>=X] - [X=Y=Bottom],

which in turn equals

100% - [X>Y] - [X=Y=Bottom], since  100%= [X>Y] + [Y>=X].

So X beats Y iff

[X>Y] > 100% - [X>Y] - [X=Y=Bottom].

If you add [X.Y] to both sides and divide by 2, you get

[X>Y] +[X=Y=Bottom]/2 > 50%,

precisely the "majority-with- half-power-truncation" rule.

So (my version of) ICA is precisely equivalent to MDDA(pt/2).

I believe it to be completely adequate for defending against burial,
truncation, and Chicken Defection.

Now suppose that p<q<r, and p+q+r=100%, and we have three factions of
respective sizes p, q, and r:, with r + q > 50%.

p: C
q: A>>B
r: B>>A

Then under the pt/2 rule both C and B are eliminated, but not A, so A is
elected.

Suppose that the B factions defects.

Then A is also eliminated, and the approval winner C is elected.

Etc.

So which of the two equivalent formulations is easier to sell?  ICA or
MDDA(pt/2) ?

Forest

Voting, using this method, I might often want to deny approval to a high-ranked candidate (even top?), without denying to the rest of my ranking, approval & full protection from burial & truncation. Maybe I just don't trust to voters of an excellent candidate whom I rank high, but I have no reason to not want to protect the rest of my ranking from burial or truncation by my unranked candidates' voters. So I suggest that, in addition to an approval cutoff, a voter should also be able to individually deny approval to any individual candidate(s). It's probably impossible in principle, with any possible method, to both protect from chicken-defection by a candidate's voters, and also give hir full truncation & burial protection. Michael Ossipoff On Fri, Nov 18, 2016 at 6:56 PM, Forest Simmons <fsimmons@pcc.edu> wrote: > Does optional approval cutoff wreck burial protection? > > Suppose we have a sincere scenario > > 40 C>B > 35 A>B > 25 B>C > > and the C faction decides to bury the CWs B. The B faction anticipates > this and responds by truncating C. It is in the interest of the A faction > to leave the default implicit approval cutoff in place. The C faction > doesn't want to give A too much support so they use the explicit cutoff > option: > > 40 C>>A > 35 A>B > 25 B > > The approval winner is B the CWs. > > If they left the implicit cutoff in place it would be worse for them; > their last choice would be elected. > > So I think MDDA with optional explicit cutoff is fine with respect to > truncation and burial. > > How about the CD? > > In this case the sincere profile is > > 40 C > 35 A>B > 25 B>A > > The B>A faction threatens to defect from the AB coalition. > The A faction responds by using the explicit cutoff: > > 40 C > 35 A>>B > 25 B > > The approval winner is C, so the threatened defection back-fires. > > It seems to me like that is plenty of chicken defection insurance. > > The obvious equilibrium position (for the chicken scenario) is > > 40 C > 35 A>>B > 25 B>>A > > Under MDDA(pt/2) the only uneliminated candidate is A. > > But if the B faction defects, all candidates are eliminated, and the > approval winner C is elected. > > This is why I like MDDA(pt/2). > > An interesting fact is that MDDA(pt/2) is just another formulation of my > version of ICA. They are precisely equivalent. Here's why: > > In my version of ICA, X beats Y iff > > [X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words, > > [X>Y] > [Y:>=X] - [X=Y=Bottom], > > which in turn equals > > 100% - [X>Y] - [X=Y=Bottom], since 100%= [X>Y] + [Y>=X]. > > So X beats Y iff > > [X>Y] > 100% - [X>Y] - [X=Y=Bottom]. > > If you add [X.Y] to both sides and divide by 2, you get > > [X>Y] +[X=Y=Bottom]/2 > 50%, > > precisely the "majority-with- half-power-truncation" rule. > > So (my version of) ICA is precisely equivalent to MDDA(pt/2). > > I believe it to be completely adequate for defending against burial, > truncation, and Chicken Defection. > > > Now suppose that p<q<r, and p+q+r=100%, and we have three factions of > respective sizes p, q, and r:, with r + q > 50%. > > p: C > q: A>>B > r: B>>A > > Then under the pt/2 rule both C and B are eliminated, but not A, so A is > elected. > > Suppose that the B factions defects. > > Then A is also eliminated, and the approval winner C is elected. > > Etc. > > So which of the two equivalent formulations is easier to sell? ICA or > MDDA(pt/2) ? > > Forest >
MO
Michael Ossipoff
Sun, Nov 20, 2016 10:10 PM

I've unsuccessfully looked for an exception to this statement of mine:

"It's probably impossible in principle, with any possible method, to both
protect from chicken-defection by a candidate's voters, and also give hir
full truncation & burial protection."

Here's what I tried:

I know of 3 ways of avoiding chicken-dilemma:

  1. IRV does it by not sharing any votes unless your top-ranked candidate is
    eliminated.

  2. MDDA(p/2) does it by the A voters denying an approval to B, in the
    chicken-dilemma example.

  3. MMPO does it by the fact that, with C voters treating A & B equally, B
    can't do better than A,  because the A faction is larger.

It could appear as if #3 is promising, because there's no need for A voters
to deny support to B.

The trouble is that,  though the A voters don't need to deny support to B,
the support that they give to anyone is iffy. MMPO doesn't really have
burial-resistance for anyone you middle-rank. Truncation of the buriers'
candidate doesn't prevent hir from successfully burying, any more than it
does in MDDTR.

Well, the best that can be said for MMPO, in regards to burial resistance,
is that burial isn't quite as easy & safe as it can be in MDDTR.

In MDDTR, the buriers merely need for everyone to be majority-beaten, & for
their candidate to have a plurality. In MMPO, the buriers need for all the
other candidates to be more beaten than their candidate. So the
requirement is a bit harder, making the burial a little less safe &
dependable.

The pt/2 provision seems to avoid MMPO's "Hitler with 2 votes" bad-example.

So, between MDDA(pt/2) and MMPO(pt/2), it's a choice between fully
protecting middle-ranked candidates whom you don't deny approval to, vs
making burial a little harder & less reliable & less safe than in MDDTR
(but not really resisted), for all of your middle-ranked candidates.

...Complete protection to all of your middle-ranked to whom you don't deny
approval, vs some questionable maybe-protection to all of your
middle-ranked.

MDDA(pt/2) gives the choice to the voter, regarding support vs
chicken-deterrence, instead of being a crapshoot-compromise like MMPO(pt/2).


I also considered IC-Smith//MMPO.

Maybe it fails FBC, but I didn't find where it does. It share's MMPO's (&
MDDTR's) usual lack of real anti-burial support for any of your
middle-ranked candidates.

I guess its advantage over MMPO(pt/2) would be its limitation to the
IC-Smith set, if that's really achieved without losing FBC.


I wanted to mention these possibilities, but I don't regard either of these
gamble-support methods as a rival to MDDA(pt/2).


Michael Ossipoff

On Sun, Nov 20, 2016 at 2:42 AM, Michael Ossipoff email9648742@gmail.com
wrote:

Voting, using this method, I might often want to deny approval to a
high-ranked candidate (even top?), without denying to the rest of my
ranking, approval & full protection from burial & truncation.

Maybe I just don't trust to voters of an excellent candidate whom I rank
high, but I have no reason to not want to protect the rest of my ranking
from burial or truncation by my unranked candidates' voters.

So I suggest that, in addition to an approval cutoff, a voter should also
be able to individually deny approval to any individual candidate(s).

It's probably impossible in principle, with any possible method, to both
protect from chicken-defection by a candidate's voters, and also give hir
full truncation & burial protection.

Michael Ossipoff

On Fri, Nov 18, 2016 at 6:56 PM, Forest Simmons fsimmons@pcc.edu wrote:

Does optional approval cutoff wreck burial protection?

Suppose we have a sincere scenario

40 C>B
35 A>B
25 B>C

and the C faction decides to bury the CWs B.  The B faction anticipates
this and responds by truncating C.  It is in the interest of the A faction
to leave the default implicit approval cutoff in place.  The C faction
doesn't want to give A too much support so they use the explicit cutoff
option:

40 C>>A
35 A>B
25 B

The approval winner is B the CWs.

If they left the implicit cutoff in place it would be worse for them;
their last choice would be elected.

So I think MDDA with optional explicit cutoff is fine with respect to
truncation and burial.

How about the CD?

In this case the sincere profile is

40 C
35 A>B
25 B>A

The B>A faction threatens to defect from the AB coalition.
The A faction responds by using the explicit cutoff:

40 C
35 A>>B
25 B

The approval winner is C, so the threatened defection back-fires.

It seems to me like that is plenty of chicken defection insurance.

The obvious equilibrium position (for the chicken scenario) is

40 C
35 A>>B
25 B>>A

Under MDDA(pt/2) the only uneliminated candidate is A.

But if the B faction defects, all candidates are eliminated, and the
approval winner C is elected.

This is why I like MDDA(pt/2).

An interesting fact is that MDDA(pt/2) is just another formulation of my
version of ICA.  They are precisely equivalent.  Here's why:

In my version of ICA, X beats Y iff

[X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words,

[X>Y] > [Y:>=X] - [X=Y=Bottom],

which in turn equals

100% - [X>Y] - [X=Y=Bottom], since  100%= [X>Y] + [Y>=X].

So X beats Y iff

[X>Y] > 100% - [X>Y] - [X=Y=Bottom].

If you add [X.Y] to both sides and divide by 2, you get

[X>Y] +[X=Y=Bottom]/2 > 50%,

precisely the "majority-with- half-power-truncation" rule.

So (my version of) ICA is precisely equivalent to MDDA(pt/2).

I believe it to be completely adequate for defending against burial,
truncation, and Chicken Defection.

Now suppose that p<q<r, and p+q+r=100%, and we have three factions of
respective sizes p, q, and r:, with r + q > 50%.

p: C
q: A>>B
r: B>>A

Then under the pt/2 rule both C and B are eliminated, but not A, so A is
elected.

Suppose that the B factions defects.

Then A is also eliminated, and the approval winner C is elected.

Etc.

So which of the two equivalent formulations is easier to sell?  ICA or
MDDA(pt/2) ?

Forest

I've unsuccessfully looked for an exception to this statement of mine: "It's probably impossible in principle, with any possible method, to both protect from chicken-defection by a candidate's voters, and also give hir full truncation & burial protection." Here's what I tried: I know of 3 ways of avoiding chicken-dilemma: 1. IRV does it by not sharing any votes unless your top-ranked candidate is eliminated. 2. MDDA(p/2) does it by the A voters denying an approval to B, in the chicken-dilemma example. 3. MMPO does it by the fact that, with C voters treating A & B equally, B can't do better than A, because the A faction is larger. It could appear as if #3 is promising, because there's no need for A voters to deny support to B. The trouble is that, though the A voters don't need to deny support to B, the support that they give to _anyone_ is iffy. MMPO doesn't really have burial-resistance for _anyone_ you middle-rank. Truncation of the buriers' candidate doesn't prevent hir from successfully burying, any more than it does in MDDTR. Well, the best that can be said for MMPO, in regards to burial resistance, is that burial isn't quite as easy & safe as it can be in MDDTR. In MDDTR, the buriers merely need for everyone to be majority-beaten, & for their candidate to have a plurality. In MMPO, the buriers need for all the other candidates to be _more_ beaten than their candidate. So the requirement is a bit harder, making the burial a little less safe & dependable. The pt/2 provision seems to avoid MMPO's "Hitler with 2 votes" bad-example. So, between MDDA(pt/2) and MMPO(pt/2), it's a choice between fully protecting middle-ranked candidates whom you don't deny approval to, vs making burial a little harder & less reliable & less safe than in MDDTR (but not really resisted), for all of your middle-ranked candidates. ...Complete protection to all of your middle-ranked to whom you don't deny approval, vs some questionable maybe-protection to all of your middle-ranked. MDDA(pt/2) gives the choice to the voter, regarding support vs chicken-deterrence, instead of being a crapshoot-compromise like MMPO(pt/2). ------------------------------------------------- I also considered IC-Smith//MMPO. Maybe it fails FBC, but I didn't find where it does. It share's MMPO's (& MDDTR's) usual lack of real anti-burial support for any of your middle-ranked candidates. I guess its advantage over MMPO(pt/2) would be its limitation to the IC-Smith set, if that's really achieved without losing FBC. --------------------------------------------------- I wanted to mention these possibilities, but I don't regard either of these gamble-support methods as a rival to MDDA(pt/2). --------------------------------------------------- Michael Ossipoff On Sun, Nov 20, 2016 at 2:42 AM, Michael Ossipoff <email9648742@gmail.com> wrote: > Voting, using this method, I might often want to deny approval to a > high-ranked candidate (even top?), without denying to the rest of my > ranking, approval & full protection from burial & truncation. > > Maybe I just don't trust to voters of an excellent candidate whom I rank > high, but I have no reason to not want to protect the rest of my ranking > from burial or truncation by my unranked candidates' voters. > > So I suggest that, in addition to an approval cutoff, a voter should also > be able to individually deny approval to any individual candidate(s). > > It's probably impossible in principle, with any possible method, to both > protect from chicken-defection by a candidate's voters, and also give hir > full truncation & burial protection. > > Michael Ossipoff > > On Fri, Nov 18, 2016 at 6:56 PM, Forest Simmons <fsimmons@pcc.edu> wrote: > >> Does optional approval cutoff wreck burial protection? >> >> Suppose we have a sincere scenario >> >> 40 C>B >> 35 A>B >> 25 B>C >> >> and the C faction decides to bury the CWs B. The B faction anticipates >> this and responds by truncating C. It is in the interest of the A faction >> to leave the default implicit approval cutoff in place. The C faction >> doesn't want to give A too much support so they use the explicit cutoff >> option: >> >> 40 C>>A >> 35 A>B >> 25 B >> >> The approval winner is B the CWs. >> >> If they left the implicit cutoff in place it would be worse for them; >> their last choice would be elected. >> >> So I think MDDA with optional explicit cutoff is fine with respect to >> truncation and burial. >> >> How about the CD? >> >> In this case the sincere profile is >> >> 40 C >> 35 A>B >> 25 B>A >> >> The B>A faction threatens to defect from the AB coalition. >> The A faction responds by using the explicit cutoff: >> >> 40 C >> 35 A>>B >> 25 B >> >> The approval winner is C, so the threatened defection back-fires. >> >> It seems to me like that is plenty of chicken defection insurance. >> >> The obvious equilibrium position (for the chicken scenario) is >> >> 40 C >> 35 A>>B >> 25 B>>A >> >> Under MDDA(pt/2) the only uneliminated candidate is A. >> >> But if the B faction defects, all candidates are eliminated, and the >> approval winner C is elected. >> >> This is why I like MDDA(pt/2). >> >> An interesting fact is that MDDA(pt/2) is just another formulation of my >> version of ICA. They are precisely equivalent. Here's why: >> >> In my version of ICA, X beats Y iff >> >> [X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words, >> >> [X>Y] > [Y:>=X] - [X=Y=Bottom], >> >> which in turn equals >> >> 100% - [X>Y] - [X=Y=Bottom], since 100%= [X>Y] + [Y>=X]. >> >> So X beats Y iff >> >> [X>Y] > 100% - [X>Y] - [X=Y=Bottom]. >> >> If you add [X.Y] to both sides and divide by 2, you get >> >> [X>Y] +[X=Y=Bottom]/2 > 50%, >> >> precisely the "majority-with- half-power-truncation" rule. >> >> So (my version of) ICA is precisely equivalent to MDDA(pt/2). >> >> I believe it to be completely adequate for defending against burial, >> truncation, and Chicken Defection. >> >> >> Now suppose that p<q<r, and p+q+r=100%, and we have three factions of >> respective sizes p, q, and r:, with r + q > 50%. >> >> p: C >> q: A>>B >> r: B>>A >> >> Then under the pt/2 rule both C and B are eliminated, but not A, so A is >> elected. >> >> Suppose that the B factions defects. >> >> Then A is also eliminated, and the approval winner C is elected. >> >> Etc. >> >> So which of the two equivalent formulations is easier to sell? ICA or >> MDDA(pt/2) ? >> >> Forest >> > >
KV
Kevin Venzke
Sun, Nov 20, 2016 11:57 PM

Hi Mike,
IC-Smith//MMPO shouldn't work for FBC, but "IC,MMPO" should work (i.e. find the Condorcet winners as under the ICA method, but instead of picking the winner with approval, use the original max defeats, without eliminating anyone).
I'm currently working on a new method DNA scheme, where a code is generated to represent a method, based on who it elects in a specific selection of 3-candidate, 3-faction scenarios. Then certain properties can be defined on the DNA and checked exhaustively. It has limits. But this one supports tying at the top, and an explicit approval cutoff to place on either side of a middle preference.
Related to this, one issue I'd like your thoughts on is how CD is defined on the wiki: Chicken Dilemma Criterion - Electowiki

|
|
|
|  |    |

|

|
|
|  |
Chicken Dilemma Criterion - Electowiki
|  |

|

|

Premise item 4 used to say "B voters refuse to vote A over anyone."
But now it says "The A voters vote B over C. The B voters refuse to vote A over anyone."
So now it appears that CD might apply even when the B faction votes B>C:5 C4 A>B3 B>C
That creates an issue, because MMPO elects B in this scenario. So I'm thinking the wiki needs an edit.
I also wonder about creating a stronger version of CD, whose penalty can be invoked not just by the B faction, but also by the A faction. I think there are probably a few reasonable methods that would satisfy this.
Kevin

  De : Michael Ossipoff <email9648742@gmail.com>

À : Forest Simmons fsimmons@pcc.edu
Cc : EM election-methods@lists.electorama.com
Envoyé le : Dimanche 20 novembre 2016 16h10
Objet : Re: [EM] Trying to have CD, protect strong top-set, and protect middle candidates too

I've unsuccessfully looked for an exception to this statement of mine:

"It's probably impossible in principle, with any possible method, to both protect from chicken-defection by a candidate's voters, and also give hir full truncation & burial protection."

Here's what I tried:

I know of 3 ways of avoiding chicken-dilemma:

  1. IRV does it by not sharing any votes unless your top-ranked candidate is eliminated.

  2. MDDA(p/2) does it by the A voters denying an approval to B, in the chicken-dilemma example.

  3. MMPO does it by the fact that, with C voters treating A & B equally, B can't do better than A,  because the A faction is larger.

It could appear as if #3 is promising, because there's no need for A voters to deny support to B.

The trouble is that,  though the A voters don't need to deny support to B, the support that they give to anyone is iffy. MMPO doesn't really have burial-resistance for anyone you middle-rank. Truncation of the buriers' candidate doesn't prevent hir from successfully burying, any more than it does in MDDTR.

Well, the best that can be said for MMPO, in regards to burial resistance, is that burial isn't quite as easy & safe as it can be in MDDTR.

In MDDTR, the buriers merely need for everyone to be majority-beaten, & for their candidate to have a plurality. In MMPO, the buriers need for all the other candidates to be more beaten than their candidate. So the requirement is a bit harder, making the burial a little less safe & dependable.

The pt/2 provision seems to avoid MMPO's "Hitler with 2 votes" bad-example.

So, between MDDA(pt/2) and MMPO(pt/2), it's a choice between fully protecting middle-ranked candidates whom you don't deny approval to, vs making burial a little harder & less reliable & less safe than in MDDTR (but not really resisted), for all of your middle-ranked candidates.

...Complete protection to all of your middle-ranked to whom you don't deny approval, vs some questionable maybe-protection to all of your middle-ranked.

MDDA(pt/2) gives the choice to the voter, regarding support vs chicken-deterrence, instead of being a crapshoot-compromise like MMPO(pt/2).


I also considered IC-Smith//MMPO.

Maybe it fails FBC, but I didn't find where it does. It share's MMPO's (& MDDTR's) usual lack of real anti-burial support for any of your middle-ranked candidates.

I guess its advantage over MMPO(pt/2) would be its limitation to the IC-Smith set, if that's really achieved without losing FBC.


I wanted to mention these possibilities, but I don't regard either of these gamble-support methods as a rival to MDDA(pt/2).


Michael Ossipoff

On Sun, Nov 20, 2016 at 2:42 AM, Michael Ossipoff email9648742@gmail.com wrote:

Voting, using this method, I might often want to deny approval to a high-ranked candidate (even top?), without denying to the rest of my ranking, approval & full protection from burial & truncation.

Maybe I just don't trust to voters of an excellent candidate whom I rank high, but I have no reason to not want to protect the rest of my ranking from burial or truncation by my unranked candidates' voters.

So I suggest that, in addition to an approval cutoff, a voter should also be able to individually deny approval to any individual candidate(s).

It's probably impossible in principle, with any possible method, to both protect from chicken-defection by a candidate's voters, and also give hir full truncation & burial protection.

Michael Ossipoff

On Fri, Nov 18, 2016 at 6:56 PM, Forest Simmons fsimmons@pcc.edu wrote:

Does optional approval cutoff wreck burial protection?

Suppose we have a sincere scenario

40 C>B
35 A>B
25 B>C

and the C faction decides to bury the CWs B.  The B faction anticipates this and responds by truncating C.  It is in the interest of the A faction to leave the default implicit approval cutoff in place.  The C faction doesn't want to give A too much support so they use the explicit cutoff option:

40 C>>A
35 A>B
25 B

The approval winner is B the CWs.

If they left the implicit cutoff in place it would be worse for them; their last choice would be elected.

So I think MDDA with optional explicit cutoff is fine with respect to truncation and burial.

How about the CD?

In this case the sincere profile is

40 C
35 A>B
25 B>A

The B>A faction threatens to defect from the AB coalition.
The A faction responds by using the explicit cutoff:

40 C
35 A>>B
25 B

The approval winner is C, so the threatened defection back-fires.

It seems to me like that is plenty of chicken defection insurance.

The obvious equilibrium position (for the chicken scenario) is

40 C
35 A>>B
25 B>>A

Under MDDA(pt/2) the only uneliminated candidate is A.

But if the B faction defects, all candidates are eliminated, and the approval winner C is elected.

This is why I like MDDA(pt/2).

An interesting fact is that MDDA(pt/2) is just another formulation of my version of ICA.  They are precisely equivalent.  Here's why:

In my version of ICA, X beats Y iff

[X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words,

[X>Y] > [Y:>=X] - [X=Y=Bottom],

which in turn equals

100% - [X>Y] - [X=Y=Bottom], since  100%= [X>Y] + [Y>=X].

So X beats Y iff

[X>Y] > 100% - [X>Y] - [X=Y=Bottom].

If you add [X.Y] to both sides and divide by 2, you get

[X>Y] +[X=Y=Bottom]/2 > 50%,

precisely the "majority-with- half-power-truncation" rule.

So (my version of) ICA is precisely equivalent to MDDA(pt/2).

I believe it to be completely adequate for defending against burial, truncation, and Chicken Defection.

Now suppose that p<q<r, and p+q+r=100%, and we have three factions of respective sizes p, q, and r:, with r + q > 50%.

p: C
q: A>>B
r: B>>A

Then under the pt/2 rule both C and B are eliminated, but not A, so A is elected.

Suppose that the B factions defects.

Then A is also eliminated, and the approval winner C is elected.

Etc.

So which of the two equivalent formulations is easier to sell?  ICA or MDDA(pt/2) ?

Forest


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

Hi Mike, IC-Smith//MMPO shouldn't work for FBC, but "IC,MMPO" should work (i.e. find the Condorcet winners as under the ICA method, but instead of picking the winner with approval, use the original max defeats, without eliminating anyone). I'm currently working on a new method DNA scheme, where a code is generated to represent a method, based on who it elects in a specific selection of 3-candidate, 3-faction scenarios. Then certain properties can be defined on the DNA and checked exhaustively. It has limits. But this one supports tying at the top, and an explicit approval cutoff to place on either side of a middle preference. Related to this, one issue I'd like your thoughts on is how CD is defined on the wiki: Chicken Dilemma Criterion - Electowiki | | | | | | | | | | | Chicken Dilemma Criterion - Electowiki | | | | Premise item 4 used to say "B voters refuse to vote A over anyone." But now it says "The A voters vote B over C. The B voters refuse to vote A over anyone." So now it appears that CD might apply even when the B faction votes B>C:5 C4 A>B3 B>C That creates an issue, because MMPO elects B in this scenario. So I'm thinking the wiki needs an edit. I also wonder about creating a stronger version of CD, whose penalty can be invoked not just by the B faction, but also by the A faction. I think there are probably a few reasonable methods that would satisfy this. Kevin De : Michael Ossipoff <email9648742@gmail.com> À : Forest Simmons <fsimmons@pcc.edu> Cc : EM <election-methods@lists.electorama.com> Envoyé le : Dimanche 20 novembre 2016 16h10 Objet : Re: [EM] Trying to have CD, protect strong top-set, and protect middle candidates too I've unsuccessfully looked for an exception to this statement of mine: "It's probably impossible in principle, with any possible method, to both protect from chicken-defection by a candidate's voters, and also give hir full truncation & burial protection." Here's what I tried: I know of 3 ways of avoiding chicken-dilemma: 1. IRV does it by not sharing any votes unless your top-ranked candidate is eliminated. 2. MDDA(p/2) does it by the A voters denying an approval to B, in the chicken-dilemma example. 3. MMPO does it by the fact that, with C voters treating A & B equally, B can't do better than A,  because the A faction is larger. It could appear as if #3 is promising, because there's no need for A voters to deny support to B. The trouble is that,  though the A voters don't need to deny support to B, the support that they give to _anyone_ is iffy. MMPO doesn't really have burial-resistance for _anyone_ you middle-rank. Truncation of the buriers' candidate doesn't prevent hir from successfully burying, any more than it does in MDDTR. Well, the best that can be said for MMPO, in regards to burial resistance, is that burial isn't quite as easy & safe as it can be in MDDTR. In MDDTR, the buriers merely need for everyone to be majority-beaten, & for their candidate to have a plurality. In MMPO, the buriers need for all the other candidates to be _more_ beaten than their candidate. So the requirement is a bit harder, making the burial a little less safe & dependable. The pt/2 provision seems to avoid MMPO's "Hitler with 2 votes" bad-example. So, between MDDA(pt/2) and MMPO(pt/2), it's a choice between fully protecting middle-ranked candidates whom you don't deny approval to, vs making burial a little harder & less reliable & less safe than in MDDTR (but not really resisted), for all of your middle-ranked candidates. ...Complete protection to all of your middle-ranked to whom you don't deny approval, vs some questionable maybe-protection to all of your middle-ranked. MDDA(pt/2) gives the choice to the voter, regarding support vs chicken-deterrence, instead of being a crapshoot-compromise like MMPO(pt/2). ------------------------------------------------- I also considered IC-Smith//MMPO. Maybe it fails FBC, but I didn't find where it does. It share's MMPO's (& MDDTR's) usual lack of real anti-burial support for any of your middle-ranked candidates. I guess its advantage over MMPO(pt/2) would be its limitation to the IC-Smith set, if that's really achieved without losing FBC. --------------------------------------------------- I wanted to mention these possibilities, but I don't regard either of these gamble-support methods as a rival to MDDA(pt/2). --------------------------------------------------- Michael Ossipoff On Sun, Nov 20, 2016 at 2:42 AM, Michael Ossipoff <email9648742@gmail.com> wrote: Voting, using this method, I might often want to deny approval to a high-ranked candidate (even top?), without denying to the rest of my ranking, approval & full protection from burial & truncation. Maybe I just don't trust to voters of an excellent candidate whom I rank high, but I have no reason to not want to protect the rest of my ranking from burial or truncation by my unranked candidates' voters. So I suggest that, in addition to an approval cutoff, a voter should also be able to individually deny approval to any individual candidate(s). It's probably impossible in principle, with any possible method, to both protect from chicken-defection by a candidate's voters, and also give hir full truncation & burial protection. Michael Ossipoff On Fri, Nov 18, 2016 at 6:56 PM, Forest Simmons <fsimmons@pcc.edu> wrote: Does optional approval cutoff wreck burial protection? Suppose we have a sincere scenario 40 C>B 35 A>B 25 B>C and the C faction decides to bury the CWs B.  The B faction anticipates this and responds by truncating C.  It is in the interest of the A faction to leave the default implicit approval cutoff in place.  The C faction doesn't want to give A too much support so they use the explicit cutoff option: 40 C>>A 35 A>B 25 B The approval winner is B the CWs. If they left the implicit cutoff in place it would be worse for them; their last choice would be elected. So I think MDDA with optional explicit cutoff is fine with respect to truncation and burial. How about the CD? In this case the sincere profile is 40 C 35 A>B 25 B>A The B>A faction threatens to defect from the AB coalition. The A faction responds by using the explicit cutoff: 40 C 35 A>>B 25 B The approval winner is C, so the threatened defection back-fires. It seems to me like that is plenty of chicken defection insurance. The obvious equilibrium position (for the chicken scenario) is 40 C 35 A>>B 25 B>>A Under MDDA(pt/2) the only uneliminated candidate is A. But if the B faction defects, all candidates are eliminated, and the approval winner C is elected. This is why I like MDDA(pt/2). An interesting fact is that MDDA(pt/2) is just another formulation of my version of ICA.  They are precisely equivalent.  Here's why: In my version of ICA, X beats Y iff [X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words, [X>Y] > [Y:>=X] - [X=Y=Bottom], which in turn equals 100% - [X>Y] - [X=Y=Bottom], since  100%= [X>Y] + [Y>=X]. So X beats Y iff [X>Y] > 100% - [X>Y] - [X=Y=Bottom]. If you add [X.Y] to both sides and divide by 2, you get [X>Y] +[X=Y=Bottom]/2 > 50%, precisely the "majority-with- half-power-truncation" rule. So (my version of) ICA is precisely equivalent to MDDA(pt/2). I believe it to be completely adequate for defending against burial, truncation, and Chicken Defection. Now suppose that p<q<r, and p+q+r=100%, and we have three factions of respective sizes p, q, and r:, with r + q > 50%. p: C q: A>>B r: B>>A Then under the pt/2 rule both C and B are eliminated, but not A, so A is elected. Suppose that the B factions defects. Then A is also eliminated, and the approval winner C is elected. Etc. So which of the two equivalent formulations is easier to sell?  ICA or MDDA(pt/2) ? Forest ---- Election-Methods mailing list - see http://electorama.com/em for list info
C
C.Benham
Sun, Nov 20, 2016 11:59 PM

On 11/19/2016 10:26 AM, Forest Simmons wrote:

An interesting fact is that MDDA(pt/2) is just another formulation of
my version of ICA.

Yes, that had dawned on me.  It's also like symmetrically completing
ballots only at the bottom, saying
that above-bottom equal-rankings contribute nothing to the pairwise
scores of the candidates with the
same above-bottom ranking versus each other, and then saying that unless
all candidates have a majority-
strength defeat any that do are disqualified.

But isn't that a little bit different from the normal version of the
"Tied-at-the-Top Rule", because that treats
equal-top equal ranking differently from all below-top equal-ranking?

I am a bit concerned about this (sincere) scenario:

40: A>B
10: A=B
35: B
15: C

With all the voters' approval cutoffs left in the default position B
wins but A is the CW. Of course if the 40 A>B
preferrers vote  A>>B there is no problem, but might there be a case for
the default placement being just below
the top-voted candidate/s?

For a method with this cute game-theoretic  defence of the 'sincere CW
who is the smallest faction's favourite' and also
a way of addressing the Chicken Dilemma scenario , this looks very good.

It meets FBC, Mono-add-Plump and Irrelevant Ballots Independence,
Plurality and Mono-raise.

Chris Benham

On 11/19/2016 10:26 AM, Forest Simmons wrote:

Does optional approval cutoff wreck burial protection?

Suppose we have a sincere scenario

40 C>B
35 A>B
25 B>C

and the C faction decides to bury the CWs B.  The B faction
anticipates this and responds by truncating C. It is in the interest
of the A faction to leave the default implicit approval cutoff in
place.  The C faction doesn't want to give A too much support so they
use the explicit cutoff option:

40 C>>A
35 A>B
25 B

The approval winner is B the CWs.

If they left the implicit cutoff in place it would be worse for them;
their last choice would be elected.

So I think MDDA with optional explicit cutoff is fine with respect to
truncation and burial.

How about the CD?

In this case the sincere profile is

40 C
35 A>B
25 B>A

The B>A faction threatens to defect from the AB coalition.
The A faction responds by using the explicit cutoff:

40 C
35 A>>B
25 B

The approval winner is C, so the threatened defection back-fires.

It seems to me like that is plenty of chicken defection insurance.

The obvious equilibrium position (for the chicken scenario) is

40 C
35 A>>B
25 B>>A

Under MDDA(pt/2) the only uneliminated candidate is A.

But if the B faction defects, all candidates are eliminated, and the
approval winner C is elected.

This is why I like MDDA(pt/2).

An interesting fact is that MDDA(pt/2) is just another formulation of
my version of ICA.  They are precisely equivalent.  Here's why:

In my version of ICA, X beats Y iff

[X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words,

[X>Y] > [Y:>=X] - [X=Y=Bottom],

which in turn equals

100% - [X>Y] - [X=Y=Bottom], since  100%= [X>Y] + [Y>=X].

So X beats Y iff

[X>Y] > 100% - [X>Y] - [X=Y=Bottom].

If you add [X.Y] to both sides and divide by 2, you get

[X>Y] +[X=Y=Bottom]/2 > 50%,

precisely the "majority-with- half-power-truncation" rule.

So (my version of) ICA is precisely equivalent to MDDA(pt/2).

I believe it to be completely adequate for defending against burial,
truncation, and Chicken Defection.

Now suppose that p<q<r, and p+q+r=100%, and we have three factions of
respective sizes p, q, and r:, with r + q > 50%.

p: C
q: A>>B
r: B>>A

Then under the pt/2 rule both C and B are eliminated, but not A, so A
is elected.

Suppose that the B factions defects.

Then A is also eliminated, and the approval winner C is elected.

Etc.

So which of the two equivalent formulations is easier to sell?  ICA or
MDDA(pt/2) ?

Forest

On 11/19/2016 10:26 AM, Forest Simmons wrote: > An interesting fact is that MDDA(pt/2) is just another formulation of > my version of ICA. Yes, that had dawned on me. It's also like symmetrically completing ballots only at the bottom, saying that above-bottom equal-rankings contribute nothing to the pairwise scores of the candidates with the same above-bottom ranking versus each other, and then saying that unless all candidates have a majority- strength defeat any that do are disqualified. But isn't that a little bit different from the normal version of the "Tied-at-the-Top Rule", because that treats equal-top equal ranking differently from all below-top equal-ranking? I am a bit concerned about this (sincere) scenario: 40: A>B 10: A=B 35: B 15: C With all the voters' approval cutoffs left in the default position B wins but A is the CW. Of course if the 40 A>B preferrers vote A>>B there is no problem, but might there be a case for the default placement being just below the top-voted candidate/s? For a method with this cute game-theoretic defence of the 'sincere CW who is the smallest faction's favourite' and also a way of addressing the Chicken Dilemma scenario , this looks very good. It meets FBC, Mono-add-Plump and Irrelevant Ballots Independence, Plurality and Mono-raise. Chris Benham On 11/19/2016 10:26 AM, Forest Simmons wrote: > Does optional approval cutoff wreck burial protection? > > Suppose we have a sincere scenario > > 40 C>B > 35 A>B > 25 B>C > > and the C faction decides to bury the CWs B. The B faction > anticipates this and responds by truncating C. It is in the interest > of the A faction to leave the default implicit approval cutoff in > place. The C faction doesn't want to give A too much support so they > use the explicit cutoff option: > > 40 C>>A > 35 A>B > 25 B > > The approval winner is B the CWs. > > If they left the implicit cutoff in place it would be worse for them; > their last choice would be elected. > > So I think MDDA with optional explicit cutoff is fine with respect to > truncation and burial. > > How about the CD? > > In this case the sincere profile is > > 40 C > 35 A>B > 25 B>A > > The B>A faction threatens to defect from the AB coalition. > The A faction responds by using the explicit cutoff: > > 40 C > 35 A>>B > 25 B > > The approval winner is C, so the threatened defection back-fires. > > It seems to me like that is plenty of chicken defection insurance. > > The obvious equilibrium position (for the chicken scenario) is > > 40 C > 35 A>>B > 25 B>>A > > Under MDDA(pt/2) the only uneliminated candidate is A. > > But if the B faction defects, all candidates are eliminated, and the > approval winner C is elected. > > This is why I like MDDA(pt/2). > > An interesting fact is that MDDA(pt/2) is just another formulation of > my version of ICA. They are precisely equivalent. Here's why: > > In my version of ICA, X beats Y iff > > [X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words, > > [X>Y] > [Y:>=X] - [X=Y=Bottom], > > which in turn equals > > 100% - [X>Y] - [X=Y=Bottom], since 100%= [X>Y] + [Y>=X]. > > So X beats Y iff > > [X>Y] > 100% - [X>Y] - [X=Y=Bottom]. > > If you add [X.Y] to both sides and divide by 2, you get > > [X>Y] +[X=Y=Bottom]/2 > 50%, > > precisely the "majority-with- half-power-truncation" rule. > > So (my version of) ICA is precisely equivalent to MDDA(pt/2). > > I believe it to be completely adequate for defending against burial, > truncation, and Chicken Defection. > > > Now suppose that p<q<r, and p+q+r=100%, and we have three factions of > respective sizes p, q, and r:, with r + q > 50%. > > p: C > q: A>>B > r: B>>A > > Then under the pt/2 rule both C and B are eliminated, but not A, so A > is elected. > > Suppose that the B factions defects. > > Then A is also eliminated, and the approval winner C is elected. > > Etc. > > So which of the two equivalent formulations is easier to sell? ICA or > MDDA(pt/2) ? > > Forest > >
MO
Michael Ossipoff
Mon, Nov 21, 2016 2:38 AM

Hi Kevin--

On Sun, Nov 20, 2016 at 6:57 PM, Kevin Venzke stepjak@yahoo.fr wrote:

IC-Smith//MMPO shouldn't work for FBC, but "IC,MMPO" should work (i.e.
find the Condorcet winners as under the ICA method, but instead of picking
the winner with approval, use the original max defeats, without eliminating
anyone).

Its advantage over MMPO(pt/2), then, would be that it meets the IC form of
the Condorcet Criterion.

I'm currently working on a new method DNA scheme, where a code is
generated to represent a method, based on who it elects in a specific
selection of 3-candidate, 3-faction scenarios.

But surely a lot of problems require more than 3 candidates. For example,
MMPO & MDDTR have their burial-vulnerability problems only with at least 4
candidates.

Yes, CD needs work. But, in the meantime, we know when a method has or
doesn't have a chicken-dilemma problem. MDDA(pt/2) doesn't have one,and
that's the main thing.

So yes, I can't defend the current form of CD.

But would I be able to revise it? I tried to revise my vote in the ongoing
Electowiki poll on voting systems (by 0-10 Score), but when I tried, I got
a message that said that access isn't available. Is that poll just closed,
or is it a systemwide problem?

I don't think that anyone should be able to revise, modify or delete what
someone else has posted to Electowiki. But the original poster should be
able to revise his or her work there.

And that poll ongoing Electowiki voting-systems poll should remain open.

I can understand why it uses Score, because there's so little agreement on
which rank-count is best. Also, Score is more easily-counted, its count is
more easily programmed. Then shouldn't that poll do a running
count-calculation, displaying the Score totals, & the winner?

[Replying farther down] :

Related to this, one issue I'd like your thoughts on is how CD is defined
on the wiki: Chicken Dilemma Criterion - Electowiki
http://wiki.electorama.com/wiki/Chicken_Dilemma_Criterion

Chicken Dilemma Criterion - Electowiki
http://wiki.electorama.com/wiki/Chicken_Dilemma_Criterion

Premise item 4 used to say "Voting is sincere, except that the B voters
refuse to vote A over anyone."

But now it says "The A voters vote B over C. The B voters refuse to vote
A over anyone."

So now it appears that CD might apply even when the B faction votes B>C

Yes, by the strict wording, it does. I've since defined, on EM, a "Weak CD"
that's more like what I initially intended with CD. Some methods meet both.

The CD definition needs revision.

[Replying farther down] :

:
5 C
4 A>B
3 B>C

That creates an issue, because MMPO elects B in this scenario. So I'm
thinking the wiki needs an edit.

I also wonder about creating a stronger version of CD, whose penalty can
be invoked not just by the B faction, but also by the A faction. I think
there are probably a few reasonable methods that would satisfy this.

I'd be interested in it, though of course my intention has been to protect
the larger faction of the majority pair of factions.

Kevin


De : Michael Ossipoff email9648742@gmail.com
À : Forest Simmons fsimmons@pcc.edu
Cc : EM election-methods@lists.electorama.com
Envoyé le : Dimanche 20 novembre 2016 16h10
Objet : Re: [EM] Trying to have CD, protect strong top-set, and protect
middle candidates too

I've unsuccessfully looked for an exception to this statement of mine:

"It's probably impossible in principle, with any possible method, to both
protect from chicken-defection by a candidate's voters, and also give hir
full truncation & burial protection."

Here's what I tried:

I know of 3 ways of avoiding chicken-dilemma:

  1. IRV does it by not sharing any votes unless your top-ranked candidate
    is eliminated.

  2. MDDA(p/2) does it by the A voters denying an approval to B, in the
    chicken-dilemma example.

  3. MMPO does it by the fact that, with C voters treating A & B equally, B
    can't do better than A,  because the A faction is larger.

It could appear as if #3 is promising, because there's no need for A
voters to deny support to B.

The trouble is that,  though the A voters don't need to deny support to B,
the support that they give to anyone is iffy. MMPO doesn't really have
burial-resistance for anyone you middle-rank. Truncation of the buriers'
candidate doesn't prevent hir from successfully burying, any more than it
does in MDDTR.

Well, the best that can be said for MMPO, in regards to burial resistance,
is that burial isn't quite as easy & safe as it can be in MDDTR.

In MDDTR, the buriers merely need for everyone to be majority-beaten, &
for their candidate to have a plurality. In MMPO, the buriers need for all
the other candidates to be more beaten than their candidate. So the
requirement is a bit harder, making the burial a little less safe &
dependable.

The pt/2 provision seems to avoid MMPO's "Hitler with 2 votes" bad-example.

So, between MDDA(pt/2) and MMPO(pt/2), it's a choice between fully
protecting middle-ranked candidates whom you don't deny approval to, vs
making burial a little harder & less reliable & less safe than in MDDTR
(but not really resisted), for all of your middle-ranked candidates.

...Complete protection to all of your middle-ranked to whom you don't deny
approval, vs some questionable maybe-protection to all of your
middle-ranked.

MDDA(pt/2) gives the choice to the voter, regarding support vs
chicken-deterrence, instead of being a crapshoot-compromise like MMPO(pt/2).


I also considered IC-Smith//MMPO.

Maybe it fails FBC, but I didn't find where it does. It share's MMPO's (&
MDDTR's) usual lack of real anti-burial support for any of your
middle-ranked candidates.

I guess its advantage over MMPO(pt/2) would be its limitation to the
IC-Smith set, if that's really achieved without losing FBC.


I wanted to mention these possibilities, but I don't regard either of
these gamble-support methods as a rival to MDDA(pt/2).


Michael Ossipoff

On Sun, Nov 20, 2016 at 2:42 AM, Michael Ossipoff email9648742@gmail.com
wrote:

Voting, using this method, I might often want to deny approval to a
high-ranked candidate (even top?), without denying to the rest of my
ranking, approval & full protection from burial & truncation.

Maybe I just don't trust to voters of an excellent candidate whom I rank
high, but I have no reason to not want to protect the rest of my ranking
from burial or truncation by my unranked candidates' voters.

So I suggest that, in addition to an approval cutoff, a voter should also
be able to individually deny approval to any individual candidate(s).

It's probably impossible in principle, with any possible method, to both
protect from chicken-defection by a candidate's voters, and also give hir
full truncation & burial protection.

Michael Ossipoff

On Fri, Nov 18, 2016 at 6:56 PM, Forest Simmons fsimmons@pcc.edu wrote:

Does optional approval cutoff wreck burial protection?

Suppose we have a sincere scenario

40 C>B
35 A>B
25 B>C

and the C faction decides to bury the CWs B.  The B faction anticipates
this and responds by truncating C.  It is in the interest of the A faction
to leave the default implicit approval cutoff in place.  The C faction
doesn't want to give A too much support so they use the explicit cutoff
option:

40 C>>A
35 A>B
25 B

The approval winner is B the CWs.

If they left the implicit cutoff in place it would be worse for them;
their last choice would be elected.

So I think MDDA with optional explicit cutoff is fine with respect to
truncation and burial.

How about the CD?

In this case the sincere profile is

40 C
35 A>B
25 B>A

The B>A faction threatens to defect from the AB coalition.
The A faction responds by using the explicit cutoff:

40 C
35 A>>B
25 B

The approval winner is C, so the threatened defection back-fires.

It seems to me like that is plenty of chicken defection insurance.

The obvious equilibrium position (for the chicken scenario) is

40 C
35 A>>B
25 B>>A

Under MDDA(pt/2) the only uneliminated candidate is A.

But if the B faction defects, all candidates are eliminated, and the
approval winner C is elected.

This is why I like MDDA(pt/2).

An interesting fact is that MDDA(pt/2) is just another formulation of my
version of ICA.  They are precisely equivalent.  Here's why:

In my version of ICA, X beats Y iff

[X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words,

[X>Y] > [Y:>=X] - [X=Y=Bottom],

which in turn equals

100% - [X>Y] - [X=Y=Bottom], since  100%= [X>Y] + [Y>=X].

So X beats Y iff

[X>Y] > 100% - [X>Y] - [X=Y=Bottom].

If you add [X.Y] to both sides and divide by 2, you get

[X>Y] +[X=Y=Bottom]/2 > 50%,

precisely the "majority-with- half-power-truncation" rule.

So (my version of) ICA is precisely equivalent to MDDA(pt/2).

I believe it to be completely adequate for defending against burial,
truncation, and Chicken Defection.

Now suppose that p<q<r, and p+q+r=100%, and we have three factions of
respective sizes p, q, and r:, with r + q > 50%.

p: C
q: A>>B
r: B>>A

Then under the pt/2 rule both C and B are eliminated, but not A, so A is
elected.

Suppose that the B factions defects.

Then A is also eliminated, and the approval winner C is elected.

Etc.

So which of the two equivalent formulations is easier to sell?  ICA or
MDDA(pt/2) ?

Forest


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

Hi Kevin-- On Sun, Nov 20, 2016 at 6:57 PM, Kevin Venzke <stepjak@yahoo.fr> wrote: > > > IC-Smith//MMPO shouldn't work for FBC, but "IC,MMPO" should work (i.e. > find the Condorcet winners as under the ICA method, but instead of picking > the winner with approval, use the original max defeats, without eliminating > anyone). > Its advantage over MMPO(pt/2), then, would be that it meets the IC form of the Condorcet Criterion. > > I'm currently working on a new method DNA scheme, where a code is > generated to represent a method, based on who it elects in a specific > selection of 3-candidate, 3-faction scenarios. > But surely a lot of problems require more than 3 candidates. For example, MMPO & MDDTR have their burial-vulnerability problems only with at least 4 candidates. Yes, CD needs work. But, in the meantime, we know when a method has or doesn't have a chicken-dilemma problem. MDDA(pt/2) doesn't have one,and that's the main thing. So yes, I can't defend the current form of CD. But would I be able to revise it? I tried to revise my vote in the ongoing Electowiki poll on voting systems (by 0-10 Score), but when I tried, I got a message that said that access isn't available. Is that poll just closed, or is it a systemwide problem? I don't think that anyone should be able to revise, modify or delete what someone else has posted to Electowiki. But the original poster should be able to revise his or her work there. And that poll ongoing Electowiki voting-systems poll should remain open. I can understand why it uses Score, because there's so little agreement on which rank-count is best. Also, Score is more easily-counted, its count is more easily programmed. Then shouldn't that poll do a running count-calculation, displaying the Score totals, & the winner? [Replying farther down] : > > Related to this, one issue I'd like your thoughts on is how CD is defined > on the wiki: Chicken Dilemma Criterion - Electowiki > <http://wiki.electorama.com/wiki/Chicken_Dilemma_Criterion> > > Chicken Dilemma Criterion - Electowiki > <http://wiki.electorama.com/wiki/Chicken_Dilemma_Criterion> > > > Premise item 4 used to say "Voting is sincere, except that the B voters > refuse to vote A over anyone." > > But now it says "The A voters vote B over C. The B voters refuse to vote > A over anyone." > > So now it appears that CD might apply even when the B faction votes B>C > Yes, by the strict wording, it does. I've since defined, on EM, a "Weak CD" that's more like what I initially intended with CD. Some methods meet both. The CD definition needs revision. [Replying farther down] : > : > 5 C > 4 A>B > 3 B>C > > That creates an issue, because MMPO elects B in this scenario. So I'm > thinking the wiki needs an edit. > > I also wonder about creating a stronger version of CD, whose penalty can > be invoked not just by the B faction, but also by the A faction. I think > there are probably a few reasonable methods that would satisfy this. > I'd be interested in it, though of course my intention has been to protect the larger faction of the majority pair of factions. > > Kevin > > > ------------------------------ > *De :* Michael Ossipoff <email9648742@gmail.com> > *À :* Forest Simmons <fsimmons@pcc.edu> > *Cc :* EM <election-methods@lists.electorama.com> > *Envoyé le :* Dimanche 20 novembre 2016 16h10 > *Objet :* Re: [EM] Trying to have CD, protect strong top-set, and protect > middle candidates too > > I've unsuccessfully looked for an exception to this statement of mine: > > "It's probably impossible in principle, with any possible method, to both > protect from chicken-defection by a candidate's voters, and also give hir > full truncation & burial protection." > > Here's what I tried: > > I know of 3 ways of avoiding chicken-dilemma: > > 1. IRV does it by not sharing any votes unless your top-ranked candidate > is eliminated. > > 2. MDDA(p/2) does it by the A voters denying an approval to B, in the > chicken-dilemma example. > > 3. MMPO does it by the fact that, with C voters treating A & B equally, B > can't do better than A, because the A faction is larger. > > It could appear as if #3 is promising, because there's no need for A > voters to deny support to B. > > The trouble is that, though the A voters don't need to deny support to B, > the support that they give to _anyone_ is iffy. MMPO doesn't really have > burial-resistance for _anyone_ you middle-rank. Truncation of the buriers' > candidate doesn't prevent hir from successfully burying, any more than it > does in MDDTR. > > Well, the best that can be said for MMPO, in regards to burial resistance, > is that burial isn't quite as easy & safe as it can be in MDDTR. > > In MDDTR, the buriers merely need for everyone to be majority-beaten, & > for their candidate to have a plurality. In MMPO, the buriers need for all > the other candidates to be _more_ beaten than their candidate. So the > requirement is a bit harder, making the burial a little less safe & > dependable. > > The pt/2 provision seems to avoid MMPO's "Hitler with 2 votes" bad-example. > > So, between MDDA(pt/2) and MMPO(pt/2), it's a choice between fully > protecting middle-ranked candidates whom you don't deny approval to, vs > making burial a little harder & less reliable & less safe than in MDDTR > (but not really resisted), for all of your middle-ranked candidates. > > ...Complete protection to all of your middle-ranked to whom you don't deny > approval, vs some questionable maybe-protection to all of your > middle-ranked. > > MDDA(pt/2) gives the choice to the voter, regarding support vs > chicken-deterrence, instead of being a crapshoot-compromise like MMPO(pt/2). > > ------------------------------------------------- > > I also considered IC-Smith//MMPO. > > Maybe it fails FBC, but I didn't find where it does. It share's MMPO's (& > MDDTR's) usual lack of real anti-burial support for any of your > middle-ranked candidates. > > I guess its advantage over MMPO(pt/2) would be its limitation to the > IC-Smith set, if that's really achieved without losing FBC. > > --------------------------------------------------- > > I wanted to mention these possibilities, but I don't regard either of > these gamble-support methods as a rival to MDDA(pt/2). > > --------------------------------------------------- > > Michael Ossipoff > > > > > > > On Sun, Nov 20, 2016 at 2:42 AM, Michael Ossipoff <email9648742@gmail.com> > wrote: > > Voting, using this method, I might often want to deny approval to a > high-ranked candidate (even top?), without denying to the rest of my > ranking, approval & full protection from burial & truncation. > > Maybe I just don't trust to voters of an excellent candidate whom I rank > high, but I have no reason to not want to protect the rest of my ranking > from burial or truncation by my unranked candidates' voters. > > So I suggest that, in addition to an approval cutoff, a voter should also > be able to individually deny approval to any individual candidate(s). > > It's probably impossible in principle, with any possible method, to both > protect from chicken-defection by a candidate's voters, and also give hir > full truncation & burial protection. > > Michael Ossipoff > > On Fri, Nov 18, 2016 at 6:56 PM, Forest Simmons <fsimmons@pcc.edu> wrote: > > Does optional approval cutoff wreck burial protection? > > Suppose we have a sincere scenario > > 40 C>B > 35 A>B > 25 B>C > > and the C faction decides to bury the CWs B. The B faction anticipates > this and responds by truncating C. It is in the interest of the A faction > to leave the default implicit approval cutoff in place. The C faction > doesn't want to give A too much support so they use the explicit cutoff > option: > > 40 C>>A > 35 A>B > 25 B > > The approval winner is B the CWs. > > If they left the implicit cutoff in place it would be worse for them; > their last choice would be elected. > > So I think MDDA with optional explicit cutoff is fine with respect to > truncation and burial. > > How about the CD? > > In this case the sincere profile is > > 40 C > 35 A>B > 25 B>A > > The B>A faction threatens to defect from the AB coalition. > The A faction responds by using the explicit cutoff: > > 40 C > 35 A>>B > 25 B > > The approval winner is C, so the threatened defection back-fires. > > It seems to me like that is plenty of chicken defection insurance. > > The obvious equilibrium position (for the chicken scenario) is > > 40 C > 35 A>>B > 25 B>>A > > Under MDDA(pt/2) the only uneliminated candidate is A. > > But if the B faction defects, all candidates are eliminated, and the > approval winner C is elected. > > This is why I like MDDA(pt/2). > > An interesting fact is that MDDA(pt/2) is just another formulation of my > version of ICA. They are precisely equivalent. Here's why: > > In my version of ICA, X beats Y iff > > [X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words, > > [X>Y] > [Y:>=X] - [X=Y=Bottom], > > which in turn equals > > 100% - [X>Y] - [X=Y=Bottom], since 100%= [X>Y] + [Y>=X]. > > So X beats Y iff > > [X>Y] > 100% - [X>Y] - [X=Y=Bottom]. > > If you add [X.Y] to both sides and divide by 2, you get > > [X>Y] +[X=Y=Bottom]/2 > 50%, > > precisely the "majority-with- half-power-truncation" rule. > > So (my version of) ICA is precisely equivalent to MDDA(pt/2). > > I believe it to be completely adequate for defending against burial, > truncation, and Chicken Defection. > > > Now suppose that p<q<r, and p+q+r=100%, and we have three factions of > respective sizes p, q, and r:, with r + q > 50%. > > p: C > q: A>>B > r: B>>A > > Then under the pt/2 rule both C and B are eliminated, but not A, so A is > elected. > > Suppose that the B factions defects. > > Then A is also eliminated, and the approval winner C is elected. > > Etc. > > So which of the two equivalent formulations is easier to sell? ICA or > MDDA(pt/2) ? > > Forest > > > > > ---- > Election-Methods mailing list - see http://electorama.com/em for list info > > >
FS
Forest Simmons
Mon, Nov 21, 2016 8:55 PM

Chris,

I'm convinced; the default approval should be top set only.  How much
control the voters have over adjusting that cutoff on their ballots is
still up for grabs.  I like keeping it simple, but Michael nade some good
points about allowing voters to specify individual disapprovals.

Good point about presenting half-power-truncation as symmetric completion
for truncated candidates.  It's easier to motivate it from that perspective.

The more I think about it the more I like symmetric completion for all
equal rankings below the approval cutoff, not just for truncation.

Then not only do we have mono-add-plump, but also this more detailed
property:

If a new ballot is added that doesn't rank any (previously) disqualified
candidate above all of her disqualifiers or equal to any approved
disqualifier, then the new winner will be from the candidates that are
approved on the new ballot.

What more could we ask for by way of participation incentive?

Forest

On Sun, Nov 20, 2016 at 3:59 PM, C.Benham cbenham@adam.com.au wrote:

On 11/19/2016 10:26 AM, Forest Simmons wrote:

An interesting fact is that MDDA(pt/2) is just another formulation of my
version of ICA.

Yes, that had dawned on me.  It's also like symmetrically completing
ballots only at the bottom, saying
that above-bottom equal-rankings contribute nothing to the pairwise scores
of the candidates with the
same above-bottom ranking versus each other, and then saying that unless
all candidates have a majority-
strength defeat any that do are disqualified.

But isn't that a little bit different from the normal version of the
"Tied-at-the-Top Rule", because that treats
equal-top equal ranking differently from all below-top equal-ranking?

I am a bit concerned about this (sincere) scenario:

40: A>B
10: A=B
35: B
15: C

With all the voters' approval cutoffs left in the default position B wins
but A is the CW. Of course if the 40 A>B
preferrers vote  A>>B there is no problem, but might there be a case for
the default placement being just below
the top-voted candidate/s?

For a method with this cute game-theoretic  defence of the 'sincere CW who
is the smallest faction's favourite' and also
a way of addressing the Chicken Dilemma scenario , this looks very good.

It meets FBC, Mono-add-Plump and Irrelevant Ballots Independence,
Plurality and Mono-raise.

Chris Benham

On 11/19/2016 10:26 AM, Forest Simmons wrote:

Does optional approval cutoff wreck burial protection?

Suppose we have a sincere scenario

40 C>B
35 A>B
25 B>C

and the C faction decides to bury the CWs B.  The B faction anticipates
this and responds by truncating C.  It is in the interest of the A faction
to leave the default implicit approval cutoff in place.  The C faction
doesn't want to give A too much support so they use the explicit cutoff
option:

40 C>>A
35 A>B
25 B

The approval winner is B the CWs.

If they left the implicit cutoff in place it would be worse for them;
their last choice would be elected.

So I think MDDA with optional explicit cutoff is fine with respect to
truncation and burial.

How about the CD?

In this case the sincere profile is

40 C
35 A>B
25 B>A

The B>A faction threatens to defect from the AB coalition.
The A faction responds by using the explicit cutoff:

40 C
35 A>>B
25 B

The approval winner is C, so the threatened defection back-fires.

It seems to me like that is plenty of chicken defection insurance.

The obvious equilibrium position (for the chicken scenario) is

40 C
35 A>>B
25 B>>A

Under MDDA(pt/2) the only uneliminated candidate is A.

But if the B faction defects, all candidates are eliminated, and the
approval winner C is elected.

This is why I like MDDA(pt/2).

An interesting fact is that MDDA(pt/2) is just another formulation of my
version of ICA.  They are precisely equivalent.  Here's why:

In my version of ICA, X beats Y iff

[X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words,

[X>Y] > [Y:>=X] - [X=Y=Bottom],

which in turn equals

100% - [X>Y] - [X=Y=Bottom], since  100%= [X>Y] + [Y>=X].

So X beats Y iff

[X>Y] > 100% - [X>Y] - [X=Y=Bottom].

If you add [X.Y] to both sides and divide by 2, you get

[X>Y] +[X=Y=Bottom]/2 > 50%,

precisely the "majority-with- half-power-truncation" rule.

So (my version of) ICA is precisely equivalent to MDDA(pt/2).

I believe it to be completely adequate for defending against burial,
truncation, and Chicken Defection.

Now suppose that p<q<r, and p+q+r=100%, and we have three factions of
respective sizes p, q, and r:, with r + q > 50%.

p: C
q: A>>B
r: B>>A

Then under the pt/2 rule both C and B are eliminated, but not A, so A is
elected.

Suppose that the B factions defects.

Then A is also eliminated, and the approval winner C is elected.

Etc.

So which of the two equivalent formulations is easier to sell?  ICA or
MDDA(pt/2) ?

Forest

Chris, I'm convinced; the default approval should be top set only. How much control the voters have over adjusting that cutoff on their ballots is still up for grabs. I like keeping it simple, but Michael nade some good points about allowing voters to specify individual disapprovals. Good point about presenting half-power-truncation as symmetric completion for truncated candidates. It's easier to motivate it from that perspective. The more I think about it the more I like symmetric completion for all equal rankings below the approval cutoff, not just for truncation. Then not only do we have mono-add-plump, but also this more detailed property: If a new ballot is added that doesn't rank any (previously) disqualified candidate above all of her disqualifiers or equal to any approved disqualifier, then the new winner will be from the candidates that are approved on the new ballot. What more could we ask for by way of participation incentive? Forest On Sun, Nov 20, 2016 at 3:59 PM, C.Benham <cbenham@adam.com.au> wrote: > On 11/19/2016 10:26 AM, Forest Simmons wrote: > > An interesting fact is that MDDA(pt/2) is just another formulation of my > version of ICA. > > > Yes, that had dawned on me. It's also like symmetrically completing > ballots only at the bottom, saying > that above-bottom equal-rankings contribute nothing to the pairwise scores > of the candidates with the > same above-bottom ranking versus each other, and then saying that unless > all candidates have a majority- > strength defeat any that do are disqualified. > > But isn't that a little bit different from the normal version of the > "Tied-at-the-Top Rule", because that treats > equal-top equal ranking differently from all below-top equal-ranking? > > I am a bit concerned about this (sincere) scenario: > > 40: A>B > 10: A=B > 35: B > 15: C > > With all the voters' approval cutoffs left in the default position B wins > but A is the CW. Of course if the 40 A>B > preferrers vote A>>B there is no problem, but might there be a case for > the default placement being just below > the top-voted candidate/s? > > For a method with this cute game-theoretic defence of the 'sincere CW who > is the smallest faction's favourite' and also > a way of addressing the Chicken Dilemma scenario , this looks very good. > > It meets FBC, Mono-add-Plump and Irrelevant Ballots Independence, > Plurality and Mono-raise. > > Chris Benham > > > > > On 11/19/2016 10:26 AM, Forest Simmons wrote: > > Does optional approval cutoff wreck burial protection? > > Suppose we have a sincere scenario > > 40 C>B > 35 A>B > 25 B>C > > and the C faction decides to bury the CWs B. The B faction anticipates > this and responds by truncating C. It is in the interest of the A faction > to leave the default implicit approval cutoff in place. The C faction > doesn't want to give A too much support so they use the explicit cutoff > option: > > 40 C>>A > 35 A>B > 25 B > > The approval winner is B the CWs. > > If they left the implicit cutoff in place it would be worse for them; > their last choice would be elected. > > So I think MDDA with optional explicit cutoff is fine with respect to > truncation and burial. > > How about the CD? > > In this case the sincere profile is > > 40 C > 35 A>B > 25 B>A > > The B>A faction threatens to defect from the AB coalition. > The A faction responds by using the explicit cutoff: > > 40 C > 35 A>>B > 25 B > > The approval winner is C, so the threatened defection back-fires. > > It seems to me like that is plenty of chicken defection insurance. > > The obvious equilibrium position (for the chicken scenario) is > > 40 C > 35 A>>B > 25 B>>A > > Under MDDA(pt/2) the only uneliminated candidate is A. > > But if the B faction defects, all candidates are eliminated, and the > approval winner C is elected. > > This is why I like MDDA(pt/2). > > An interesting fact is that MDDA(pt/2) is just another formulation of my > version of ICA. They are precisely equivalent. Here's why: > > In my version of ICA, X beats Y iff > > [X>Y] > [Y>X] + [X=Y=T] + [X=Y=between] , in other words, > > [X>Y] > [Y:>=X] - [X=Y=Bottom], > > which in turn equals > > 100% - [X>Y] - [X=Y=Bottom], since 100%= [X>Y] + [Y>=X]. > > So X beats Y iff > > [X>Y] > 100% - [X>Y] - [X=Y=Bottom]. > > If you add [X.Y] to both sides and divide by 2, you get > > [X>Y] +[X=Y=Bottom]/2 > 50%, > > precisely the "majority-with- half-power-truncation" rule. > > So (my version of) ICA is precisely equivalent to MDDA(pt/2). > > I believe it to be completely adequate for defending against burial, > truncation, and Chicken Defection. > > > Now suppose that p<q<r, and p+q+r=100%, and we have three factions of > respective sizes p, q, and r:, with r + q > 50%. > > p: C > q: A>>B > r: B>>A > > Then under the pt/2 rule both C and B are eliminated, but not A, so A is > elected. > > Suppose that the B factions defects. > > Then A is also eliminated, and the approval winner C is elected. > > Etc. > > So which of the two equivalent formulations is easier to sell? ICA or > MDDA(pt/2) ? > > Forest > > > >
MO
Michael Ossipoff
Mon, Nov 21, 2016 10:55 PM

On Sat, Nov 19, 2016 at 12:18 AM, C.Benham cbenham@adam.com.au wrote:

On 11/19/2016 3:14 AM, Michael Ossipoff wrote:

If the more embarrassing Mono-Raise failure doesn't give IRV any
acceptance or enactment problem, then why should the less embarrassing
Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment
problem?

Because what you consider more or less "embarrassing" I am sure isn't in
accord with what most people would find unacceptably ridiculous.

You're right. What could be considered ridiculous about making a candidate
lose by raising hir from last choice to 1st choice in your ranking?

:^)

With MDDTR, if your plump for X makes X lose, it's because you added a
ballot. It has nothing whatsoever to do with the fact that you voted
favorably to X.

That's right. "You" should have found some way to vote for X without
adding a ballot. Unfortunately removing someone else's ballot when you are
in the
polling station is usually impossible or legally risky.

Then let me reword it:

With MDDTR, if your plump for X makes hir lose, it's because you added a
ballot. It has nothing whatsoever to do with the fact that the new ballot
plumped for X.

Your ballot made X lose in spite of the fact that it was a plump for X, not
because it was a plump for X.

But in IRV, when you make X lose by raising hir from last place to 1st
place, that raising of X was the only thing that you did, and it is the
reason why X lost.

Anyway, if IRV is so widely used and successful, then why would
nonmonotonicity be a problem for MDDTR?

Because IRV has a traditional and (for many) intuitive algorithm

So, tradition before merit?

, and a solid "maximal"  set of criterion compliances and MDDTR doesn't.

No doubt everyone has own definition of "solid maximal".

MDDTR avoids chicken dilemma and meets FBC.

IRV avoids chicken dilemma but fails FBC.

IRV was thrown out in Burlington because the CWs's voters have no way to
protect hir from defeat if hir faction is smallest, and neither does anyone
else, short of favorite-burial.

MDDTR doesn't have that problem. Though MDDTR's protection of a CWs isn't
as good as that of Simmons (unless, with Simmons, that CWs is being denied
approval due to a chicken-dilemma situation), MDDTR still offers some
burial deterrence (helped by voters, including the CWs's voters, refusing
to rank past the CWs), and full truncation-proofness.

IRV is pretty much unique, in the degree to which no one can do anything to
protect a small-faction CWs.

I don't oppose IRV, though I don't advocate it either (unless the only
alternative is no change from Plurality).

As I said in another thread, IRV's long track-record in elections for
national office, is one of 2-party domination.

Earlier you attempted to ridicule my observation that MDDTR fails
Irrelevant Ballots Independence by suggesting that might indirectly
motivate a higher
turnout.

There's nothing wrong with working to increase turnout.

Well, just as some might have an interest in promoting that (for voters
who'll ignore the competitive/viable candidates) so as to wash away
an otherwise likely majority-defeat disqualification so would opposed
forces have an interest in doing the opposite.

Sure, some might have incentive to suppress turnout. That that's true
anyway, with any method. Anyway, measures to reduce turnout would be
difficult to justify in Congress, and, in some instances, under existing
law, would be illegal. I don't think that turnout-suppression with MDDTR
would be a problem.

In any case, the Mono-Add-Plump failure of MDDA & MDDTR is now moot,
because it's avoided by the pt/2 provision.

Chris said:

Just the knowledge that a failure of Mono-add-Plump  is theoretically
possible could reduce people's enthusiasm for voting and make it more
likely that those who like to vote by just plumping for their favourite
will stay home.

[endquote]

.Then the fact that ranking someone 1st place instead of last place could
make hir lose will likewise make you stay home instead of showing up and
top-ranking your favorite in IRV.
.
Chris said:

Whereas IRV doesn't just meet mono-add-plump. It also meet Mono-add-Top

[endquote]

...and fails Mono-Raise, and fails FBC in a particularly flagrant way that
won't be unusual..

C: Failing mono-add-plump is as stupid as a quasi-"intelligent" device can
be, in a pure and starkly obvious way, and with the lamest possible excuse.

The algorithm/device decides that X should win, and then receives some more
ballots that contain nothing whatsoever but the pure and simple message:
"You are right! X should win" and responds with the bizarre malfunction
"I've changed my mind, Y should win" and offers the nonsensical excuse "Hey
those
extra ballots didn't just say that X should win. They also increased the
total number of ballots!".

C: What (arguably) desirable properties (or criterion compliances)  are
incompatible with meeting Mono-add-Plump?

Mike: FBC, CD, & wv-like strategy are evidently require failing
Mono-Add-Plump, or having MMPO's Hitler-with-2-votes problem.

With MDDTR, the price of FBC, CD & wv-like strategy is Mono-Add-Plump.

C: There are methods that meet  FBC and CD and mono-add-plump. So your
proposition boils down to saying that it's worth giving up compliance with
mono-add-plump just to gain "wv-like strategy"

.

Sure, I'm more interested in making voting easier, and making sincerity
safer, than in embarrassment criteria. (...and IRV has an at least equally
ridiculous nonmonotonicity).

I now realize that MDDTR doesn't have wv strategy, though it does have full
truncation-proofness.

Simmons, MMPO(pt/2), IC,MMPO, and probably other methods meet FBC & CD, and
let voters protect a CWs to varying degrees under different
conditions...something that you have to give up when you choose IRV, in
which a CWs automatically loses if its faction is smallest.

I'm not saying that the overall IRV package couldn't be ok, if people
understand and accept IRV's problem and won't let it make them
favorite-bury.

Anyway, we now know that, with the pt/2 provision, MDDA & MDDTR needn't
give up Mono-Add-Plump.  ...and evidently MMPO needn't have the
Hitler-with-2-votes problem.

Michael Ossipoff

Chris Benham

On 11/19/2016 3:14 AM, Michael Ossipoff wrote:

I don't mean that IRV isn't ok. IRV's Mono-Raise failure doesn't bother me.
Neither does MDDTR's Mono-Add-Plump failure.

Voting's purpose is probabilistic anyway. You vote to improve the
probability of a better outcome. The possible nonmonotonicity of IRV
& MDDTR doesn't invalidate that.

My point, in asking about when you make someone lose by raising hir from
last place to 1st place, was just that IRV is popular and widely used. It's
been used in Australia for a long time, and it's used in a fair number of
cities in this country.  ...and now has been adopted by the state of Maine.

...in spite of its Mono-Raise failure.

If the more embarrassing Mono-Raise failure doesn't give IRV any
acceptance or enactment problem, then why should the less embarrassing
Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment
problem?

There of course have been objections to IRV, some valid, some not. But I
haven't heard any of the IRV critics in the various cities complain about
its nonmonotonicity. They object to implementation complexity. They
invalidly claim voting complexity. They invalidly complain because
supposedly voting is supposed to be by Plurality. They repealed IRV in
Burlington because of the elimination of a CWv.  But none of the
complaints that I've heard, in cities using it or considering IRV, have
been about its nonmonotonicity.

Why I say that Mono-Raise failure is more embarrassing:

With MDDTR, if your plump for X makes X lose, it's because you added a
ballot. It has nothing whatsoever to do with the fact that you voted
favorably to X.

With IRV, if raising X from bottom to top makes X lose, then X lost for no
other reason than because you helped hir more.

There are 2 kinds of nonmonotonicity:

Did you make X lose in spite of voting favorably for hir?

or

Did you make X lose because you voted hir more favorably?

Of those 2 kinds of nonmonotonicity the 2nd one is more of an
embarrassment to the method. There, the method is more directly acting
oppositely to your action.

Maybe it could be said that the 2nd kind of nonmonotonicity is twice as
embarrassing to the voting-system.

Anyway, if IRV is so widely used and successful, then why would
nonmonotonicity be a problem for MDDTR?

I now feel that IRV's (mitigated) problem isn't an unusually high price
for CD, isn't more than the "going rate" for CD. IRV & its derivatives are
at the top of my ranking of method-merit for electorates who want &/or need
ranking.

Michael Ossipoff

On Fri, Nov 18, 2016 at 1:23 AM, Michael Ossipoff email9648742@gmail.com
wrote:

Forest--

You wrote:

But MAI still fails FBC.

Failing both FBC & CD isn't good.

So to me the best proposal is ICA with default approval cutoff at
truncation to help punish burial and truncation with an option to raise the
cutoff to withstand a CD attack.

But buriers or truncators could raise that approval cutoff too. Someone
could bury X under Z without having to approve Z. That loses the deterrence
that would exist if that burier had to approve Z in order to rank hir over
someone, as would be so if ranking is counted as approval.

So CD still comes at the cost of a lot less protection against burial,
or, in ICT's case, trunction too.

But that just means that it isn't better than MDDTR in that regard. It
doesn't mean that it's worse.

And it doesn't have Mono-Add-Plump failure.

So, the method has CD as MDDTR does, and trades truncation-proofness for
Mono-Add-Plump.

I value strategy protections more than embarrassment criteria. (But I
realize that proposal-opponents can use embarrassment criteria criticisms,
and that proponents aren't likely to be able to afford as much media time,
to answer the criticisms.)

[Replying farther down] :

Here's my version (slightly different from the original):

Candidate X strongly beats candidate Y iff

the number of ballots on which X is ranked over Y is greater than

the number of ballots on which Y is ranked equal to or greater than Y.

[Note Y is not ranked equal to X if Y is not ranked.]

If not all of the candidates are strongly beaten, disqualify all of the
ones who are.

Elect the most approved qualified candidate.

I think that this method has all of the good properties of MDDA with
mono-add-plump to boot.

I've only had a preliminary look at it, but it seems to me, right now,
that the separate approval-cutoff that the voter can raise from the default
spoils protection from burial & truncation.

You wrote:

We still need to explore MDDA with the half power truncation rule, since
it would also satisfy mono-add-plump if I am not mistaken.

Yes, it seems to me that a 1/2 power-truncation would get rid of the
Mono-Add-Plump failure. If, by not ranking a certain 2 candidates, you give
them each at least half of a vote against eachother, that would bring
Mono-Add-Plump compliance, it seems to me.

So maybe it would avoid criticism of MDDA.

But, if used with MDDTR, it would spoil CD.

You wrote:

I agree with Chris Benham that mono-add-plump failure would be fatal in
a public proposal.

What if you're going to rank X last in your ranking. With all the
ballots, including yours, X will win. But then you move X to 1st place in
your ranking, and that makes X lose.

Would that be ok?

Michael Ossipoff

On Thu, Nov 17, 2016 at 2:12 PM, Michael Ossipoff <
email9648742@gmail.com> wrote:

I meant to ask: Did you say that MTRI doesn't pass FBC? How does FBC
failure happen? In return for FBC, it should beat MDDTR at vulnerability to
burial, and not be vulnerable to truncation.

Anyway, anything you can tell me about the properties comparison
between MTRI & MDDTR would be helpful.

MIchael Ossipoff

On Thu, Nov 17, 2016 at 5:05 PM, Michael Ossipoff <
email9648742@gmail.com> wrote:

For this method, MTRI, the procedural definition is more
understandable than the recursive definition (though the recursive
definition's brevity could be useful).

So this is what I understand MTRI's procedural definition to be:

  1. Order the candidates by their top-count score, with higher scores
    at top.

  2. Switch the lowest pair of adjacent candidates whose lower candidate
    pair-beats the higher one.

Repeat till there are no more pairs to switch. The highest candidate
in the order at that time wins.


As a CD rank method, this method is a competitor of MDDTR. What are
the property differences between MTRI & MDDTR?

In particular, how does MTRI compare with MDDTR in regards to
protection of a CWs against truncation & burial?

Michael Ossipoff

On Thu, Nov 17, 2016 at 2:55 PM, Forest Simmons fsimmons@pcc.edu
wrote:

On Thu, Nov 17, 2016 at 10:54 AM, Michael Ossipoff <
email9648742@gmail.com> wrote:

But wouldn't Smith//Approval, with approval cutoffs in the rankings,
share MDDTR's burial-vullnerability?

...with, additionally, vulnerability to truncation, which MDDTR
doesn't have?

And Smith//Approval trades MDDTR's FBC for Smith, which I consider
an unfavorable trade.

Perhaps make truncation the default approval cutoff, but let voters
move it higher as an option:

45 C
30 A>B or A>>B
25 B

Voting A>>B would be the chicken defense (where sincere is 25 B>A).

Voting A>B would be the truncation defense (where sincere is 45 C>B).

With this option, MDDA would be an FBC compliant method that is
truncation and burial resistant as well as quasi CD compliant.

Is there a way to modify MDDA to make it satisfy mono-add-plump?

How about incorporating some form of power truncation.  When you
plump X and reduce the majority victory of Y over Z to a sub-majority, it
would revert to a majority if you counted the common truncation of Y and Z
against each other as even half a point.

Btw, in case you didn't see it, one of my new favorite non-FBC
methods is Most Approved Immune(MAI):  Elect the most approved immune
candidate.

This means elect the most approved candidate X that is unbeaten
pairwise by the candidate that would win (recursively) if the method were
applied to the same ballot set with X disqualified or withdrawn.

It is the simplest approval based rank method that confers immunity
from second place complaints on its winners.

It is quasi CD compliant if voters can specify their approval cutoffs
above the truncation level when they want to.

A top rank version of this method is fully CD compliant:

Elect the Most Top Ranked Immune candidate. (MTRI)

In other words elect the most top ranked candidate X that is unbeaten
pairwise by the candidate that would win (recursively) if the method were
applied to the same ballot set with X disqualified or withdrawn.

Forest

On Sat, Nov 19, 2016 at 12:18 AM, C.Benham <cbenham@adam.com.au> wrote: > On 11/19/2016 3:14 AM, Michael Ossipoff wrote: > > If the more embarrassing Mono-Raise failure doesn't give IRV any > acceptance or enactment problem, then why should the less embarrassing > Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment > problem? > > > Because what you consider more or less "embarrassing" I am sure isn't in > accord with what most people would find unacceptably ridiculous. > You're right. What could be considered ridiculous about making a candidate lose by raising hir from last choice to 1st choice in your ranking? :^) > > > With MDDTR, if your plump for X makes X lose, it's because you added a > ballot. It has nothing whatsoever to do with the fact that you voted > favorably to X. > > > That's right. "You" should have found some way to vote for X without > adding a ballot. Unfortunately removing someone else's ballot when you are > in the > polling station is usually impossible or legally risky. > Then let me reword it: With MDDTR, if your plump for X makes hir lose, it's because you added a ballot. It has nothing whatsoever to do with the fact that the new ballot plumped for X. Your ballot made X lose in spite of the fact that it was a plump for X, not because it was a plump for X. But in IRV, when you make X lose by raising hir from last place to 1st place, that raising of X was the only thing that you did, and it is the reason why X lost. > > Anyway, if IRV is so widely used and successful, then why would > nonmonotonicity be a problem for MDDTR? > > > Because IRV has a traditional and (for many) intuitive algorithm > So, tradition before merit? > , and a solid "maximal" set of criterion compliances and MDDTR doesn't. > No doubt everyone has own definition of "solid maximal". MDDTR avoids chicken dilemma and meets FBC. IRV avoids chicken dilemma but fails FBC. IRV was thrown out in Burlington because the CWs's voters have no way to protect hir from defeat if hir faction is smallest, and neither does anyone else, short of favorite-burial. MDDTR doesn't have that problem. Though MDDTR's protection of a CWs isn't as good as that of Simmons (unless, with Simmons, that CWs is being denied approval due to a chicken-dilemma situation), MDDTR still offers some burial deterrence (helped by voters, including the CWs's voters, refusing to rank past the CWs), and full truncation-proofness. IRV is pretty much unique, in the degree to which no one can do anything to protect a small-faction CWs. I don't oppose IRV, though I don't advocate it either (unless the only alternative is no change from Plurality). As I said in another thread, IRV's long track-record in elections for national office, is one of 2-party domination. > Earlier you attempted to ridicule my observation that MDDTR fails > Irrelevant Ballots Independence by suggesting that might indirectly > motivate a higher > turnout. > There's nothing wrong with working to increase turnout. > Well, just as some might have an interest in promoting that (for voters > who'll ignore the competitive/viable candidates) so as to wash away > an otherwise likely majority-defeat disqualification so would opposed > forces have an interest in doing the opposite. > Sure, some might have incentive to suppress turnout. That that's true anyway, with any method. Anyway, measures to reduce turnout would be difficult to justify in Congress, and, in some instances, under existing law, would be illegal. I don't think that turnout-suppression with MDDTR would be a problem. In any case, the Mono-Add-Plump failure of MDDA & MDDTR is now moot, because it's avoided by the pt/2 provision. Chris said: Just the knowledge that a failure of Mono-add-Plump is theoretically possible could reduce people's enthusiasm for voting and make it more likely that those who like to vote by just plumping for their favourite will stay home. [endquote] .Then the fact that ranking someone 1st place instead of last place could make hir lose will likewise make you stay home instead of showing up and top-ranking your favorite in IRV. . Chris said: Whereas IRV doesn't just meet mono-add-plump. It also meet Mono-add-Top [endquote] ...and fails Mono-Raise, and fails FBC in a particularly flagrant way that won't be unusual.. C: Failing mono-add-plump is as stupid as a quasi-"intelligent" device can be, in a pure and starkly obvious way, and with the lamest possible excuse. The algorithm/device decides that X should win, and then receives some more ballots that contain nothing whatsoever but the pure and simple message: "You are right! X should win" and responds with the bizarre malfunction "I've changed my mind, Y should win" and offers the nonsensical excuse "Hey those extra ballots didn't just say that X should win. They also increased the total number of ballots!". C: What (arguably) desirable properties (or criterion compliances) are incompatible with meeting Mono-add-Plump? Mike: FBC, CD, & wv-like strategy are evidently require failing Mono-Add-Plump, or having MMPO's Hitler-with-2-votes problem. With MDDTR, the price of FBC, CD & wv-like strategy is Mono-Add-Plump. C: There are methods that meet FBC and CD and mono-add-plump. So your proposition boils down to saying that it's worth giving up compliance with mono-add-plump just to gain "wv-like strategy" . Sure, I'm more interested in making voting easier, and making sincerity safer, than in embarrassment criteria. (...and IRV has an at least equally ridiculous nonmonotonicity). I now realize that MDDTR doesn't have wv strategy, though it does have full truncation-proofness. Simmons, MMPO(pt/2), IC,MMPO, and probably other methods meet FBC & CD, and let voters protect a CWs to varying degrees under different conditions...something that you have to give up when you choose IRV, in which a CWs automatically loses if its faction is smallest. I'm not saying that the overall IRV package couldn't be ok, if people understand and accept IRV's problem and won't let it make them favorite-bury. Anyway, we now know that, with the pt/2 provision, MDDA & MDDTR needn't give up Mono-Add-Plump. ...and evidently MMPO needn't have the Hitler-with-2-votes problem. Michael Ossipoff Chris Benham On 11/19/2016 3:14 AM, Michael Ossipoff wrote: > I don't mean that IRV isn't ok. IRV's Mono-Raise failure doesn't bother me. > Neither does MDDTR's Mono-Add-Plump failure. > > Voting's purpose is probabilistic anyway. You vote to improve the > probability of a better outcome. The possible nonmonotonicity of IRV > & MDDTR doesn't invalidate that. > > My point, in asking about when you make someone lose by raising hir from > last place to 1st place, was just that IRV is popular and widely used. It's > been used in Australia for a long time, and it's used in a fair number of > cities in this country. ...and now has been adopted by the state of Maine. > > ...in spite of its Mono-Raise failure. > > If the more embarrassing Mono-Raise failure doesn't give IRV any > acceptance or enactment problem, then why should the less embarrassing > Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment > problem? > > There of course have been objections to IRV, some valid, some not. But I > haven't heard any of the IRV critics in the various cities complain about > its nonmonotonicity. They object to implementation complexity. They > invalidly claim voting complexity. They invalidly complain because > supposedly voting is supposed to be by Plurality. They repealed IRV in > Burlington because of the elimination of a CWv. But none of the > complaints that I've heard, in cities using it or considering IRV, have > been about its nonmonotonicity. > > Why I say that Mono-Raise failure is more embarrassing: > > With MDDTR, if your plump for X makes X lose, it's because you added a > ballot. It has nothing whatsoever to do with the fact that you voted > favorably to X. > > With IRV, if raising X from bottom to top makes X lose, then X lost for no > other reason than because you helped hir more. > > There are 2 kinds of nonmonotonicity: > > Did you make X lose _in spite of_ voting favorably for hir? > > or > > Did you make X lose _because_ you voted hir more favorably? > > Of those 2 kinds of nonmonotonicity the 2nd one is more of an > embarrassment to the method. There, the method is more directly acting > oppositely to your action. > > Maybe it could be said that the 2nd kind of nonmonotonicity is twice as > embarrassing to the voting-system. > > Anyway, if IRV is so widely used and successful, then why would > nonmonotonicity be a problem for MDDTR? > > I now feel that IRV's (mitigated) problem isn't an unusually high price > for CD, isn't more than the "going rate" for CD. IRV & its derivatives are > at the top of my ranking of method-merit for electorates who want &/or need > ranking. > > Michael Ossipoff > > > > > > > > On Fri, Nov 18, 2016 at 1:23 AM, Michael Ossipoff <email9648742@gmail.com> > wrote: > >> Forest-- >> >> You wrote: >> >>> >>> But MAI still fails FBC. >>> >> >> Failing both FBC & CD isn't good. >> >> >>> >>> So to me the best proposal is ICA with default approval cutoff at >>> truncation to help punish burial and truncation with an option to raise the >>> cutoff to withstand a CD attack. >>> >> >> But buriers or truncators could raise that approval cutoff too. Someone >> could bury X under Z without having to approve Z. That loses the deterrence >> that would exist if that burier had to approve Z in order to rank hir over >> someone, as would be so if ranking is counted as approval. >> >> So CD still comes at the cost of a lot less protection against burial, >> or, in ICT's case, trunction too. >> >> But that just means that it isn't _better_ than MDDTR in that regard. It >> doesn't mean that it's worse. >> >> And it doesn't have Mono-Add-Plump failure. >> >> So, the method has CD as MDDTR does, and trades truncation-proofness for >> Mono-Add-Plump. >> >> I value strategy protections more than embarrassment criteria. (But I >> realize that proposal-opponents can use embarrassment criteria criticisms, >> and that proponents aren't likely to be able to afford as much media time, >> to answer the criticisms.) >> >> [Replying farther down] : >> >> >> >>> >>> Here's my version (slightly different from the original): >>> >>> Candidate X strongly beats candidate Y iff >>> >>> the number of ballots on which X is ranked over Y is greater than >>> >>> the number of ballots on which Y is *ranked* equal to or greater than Y. >>> >>> [Note Y is not ranked equal to X if Y is not ranked.] >>> >>> If not all of the candidates are strongly beaten, disqualify all of the >>> ones who are. >>> >>> Elect the most approved qualified candidate. >>> >>> I think that this method has all of the good properties of MDDA with >>> mono-add-plump to boot. >>> >> >> I've only had a preliminary look at it, but it seems to me, right now, >> that the separate approval-cutoff that the voter can raise from the default >> spoils protection from burial & truncation. >> >> >> You wrote: >> >> >>> We still need to explore MDDA with the half power truncation rule, since >>> it would also satisfy mono-add-plump if I am not mistaken. >>> >> >> Yes, it seems to me that a 1/2 power-truncation would get rid of the >> Mono-Add-Plump failure. If, by not ranking a certain 2 candidates, you give >> them each at least half of a vote against eachother, that would bring >> Mono-Add-Plump compliance, it seems to me. >> >> So maybe it would avoid criticism of MDDA. >> >> But, if used with MDDTR, it would spoil CD. >> >> You wrote: >> >> >> >>> I agree with Chris Benham that mono-add-plump failure would be fatal in >>> a public proposal. >>> >>> >> What if you're going to rank X last in your ranking. With all the >> ballots, including yours, X will win. But then you move X to 1st place in >> your ranking, and that makes X lose. >> >> Would that be ok? >> >> Michael Ossipoff >> >> >> >> >>> On Thu, Nov 17, 2016 at 2:12 PM, Michael Ossipoff < >>> email9648742@gmail.com> wrote: >>> >>>> I meant to ask: Did you say that MTRI doesn't pass FBC? How does FBC >>>> failure happen? In return for FBC, it should beat MDDTR at vulnerability to >>>> burial, and not be vulnerable to truncation. >>>> >>>> Anyway, anything you can tell me about the properties comparison >>>> between MTRI & MDDTR would be helpful. >>>> >>>> MIchael Ossipoff >>>> >>>> On Thu, Nov 17, 2016 at 5:05 PM, Michael Ossipoff < >>>> email9648742@gmail.com> wrote: >>>> >>>>> For this method, MTRI, the procedural definition is more >>>>> understandable than the recursive definition (though the recursive >>>>> definition's brevity could be useful). >>>>> >>>>> So this is what I understand MTRI's procedural definition to be: >>>>> >>>>> 1. Order the candidates by their top-count score, with higher scores >>>>> at top. >>>>> >>>>> 2. Switch the lowest pair of adjacent candidates whose lower candidate >>>>> pair-beats the higher one. >>>>> >>>>> Repeat till there are no more pairs to switch. The highest candidate >>>>> in the order at that time wins. >>>>> >>>>> ----------------------------------------------- >>>>> >>>>> As a CD rank method, this method is a competitor of MDDTR. What are >>>>> the property differences between MTRI & MDDTR? >>>>> >>>>> In particular, how does MTRI compare with MDDTR in regards to >>>>> protection of a CWs against truncation & burial? >>>>> >>>>> Michael Ossipoff >>>>> >>>>> >>>>> On Thu, Nov 17, 2016 at 2:55 PM, Forest Simmons <fsimmons@pcc.edu> >>>>> wrote: >>>>> >>>>>> On Thu, Nov 17, 2016 at 10:54 AM, Michael Ossipoff < >>>>>> email9648742@gmail.com> wrote: >>>>>> >>>>>>> But wouldn't Smith//Approval, with approval cutoffs in the rankings, >>>>>>> share MDDTR's burial-vullnerability? >>>>>>> >>>>>>> ...with, additionally, vulnerability to truncation, which MDDTR >>>>>>> _doesn't_ have? >>>>>>> >>>>>>> And Smith//Approval trades MDDTR's FBC for Smith, which I consider >>>>>>> an unfavorable trade. >>>>>>> >>>>>> >>>>>> Perhaps make truncation the default approval cutoff, but let voters >>>>>> move it higher as an option: >>>>>> >>>>>> 45 C >>>>>> 30 A>B or A>>B >>>>>> 25 B >>>>>> >>>>>> Voting A>>B would be the chicken defense (where sincere is 25 B>A). >>>>>> >>>>>> Voting A>B would be the truncation defense (where sincere is 45 C>B). >>>>>> >>>>>> With this option, MDDA would be an FBC compliant method that is >>>>>> truncation and burial resistant as well as quasi CD compliant. >>>>>> >>>>>> Is there a way to modify MDDA to make it satisfy mono-add-plump? >>>>>> >>>>>> How about incorporating some form of power truncation. When you >>>>>> plump X and reduce the majority victory of Y over Z to a sub-majority, it >>>>>> would revert to a majority if you counted the common truncation of Y and Z >>>>>> against each other as even half a point. >>>>>> >>>>>> Btw, in case you didn't see it, one of my new favorite non-FBC >>>>>> methods is Most Approved Immune(MAI): Elect the most approved immune >>>>>> candidate. >>>>>> >>>>>> This means elect the most approved candidate X that is unbeaten >>>>>> pairwise by the candidate that would win (recursively) if the method were >>>>>> applied to the same ballot set with X disqualified or withdrawn. >>>>>> >>>>>> It is the simplest approval based rank method that confers immunity >>>>>> from second place complaints on its winners. >>>>>> >>>>>> It is quasi CD compliant if voters can specify their approval cutoffs >>>>>> above the truncation level when they want to. >>>>>> >>>>>> A top rank version of this method is fully CD compliant: >>>>>> >>>>>> Elect the Most Top Ranked Immune candidate. (MTRI) >>>>>> >>>>>> In other words elect the most top ranked candidate X that is unbeaten >>>>>> pairwise by the candidate that would win (recursively) if the method were >>>>>> applied to the same ballot set with X disqualified or withdrawn. >>>>>> >>>>>> Forest >>>>>> >>>>>> >>>>> >>>> >>> >> > > >
MO
Michael Ossipoff
Mon, Nov 21, 2016 11:03 PM

"Just the knowledge that a failure of Mono-add-Plump  is theoretically
possible could reduce people's enthusiasm for voting and make it more
likely that those who like to vote by just plumping for their favourite
will stay home."

...or make you rank your favorite last instead of first in IRV because
ranking hir first instead of last could make hir lose?

...or just not vote because you know that IRV can act oppositely to changes
in your vote?

Michael Ossipoff

On Sat, Nov 19, 2016 at 12:18 AM, C.Benham cbenham@adam.com.au wrote:

On 11/19/2016 3:14 AM, Michael Ossipoff wrote:

If the more embarrassing Mono-Raise failure doesn't give IRV any
acceptance or enactment problem, then why should the less embarrassing
Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment
problem?

Because what you consider more or less "embarrassing" I am sure isn't in
accord with what most people would find unacceptably ridiculous.

With MDDTR, if your plump for X makes X lose, it's because you added a
ballot. It has nothing whatsoever to do with the fact that you voted
favorably to X.

That's right. "You" should have found some way to vote for X without
adding a ballot. Unfortunately removing someone else's ballot when you are
in the
polling station is usually impossible or legally risky.

Anyway, if IRV is so widely used and successful, then why would
nonmonotonicity be a problem for MDDTR?

Because IRV has a traditional and (for many) intuitive algorithm, and a
solid "maximal"  set of criterion compliances and MDDTR doesn't.

Earlier you attempted to ridicule my observation that MDDTR fails
Irrelevant Ballots Independence by suggesting that might indirectly
motivate a higher
turnout.  Well, just as some might have an interest in promoting that (for
voters who'll ignore the competitive/viable candidates) so as to wash away
an otherwise likely majority-defeat disqualification so would opposed
forces have an interest in doing the opposite.

In fact you could have post-election recriminations reminiscent of those
that were aimed at Nader and those who voted for him supposedly allowing
Bush to
win a few years ago. "Those idiots weren't even really interested in who
won, why didn't they just stay home?!" could be the lament.

Just the knowledge that a failure of Mono-add-Plump  is theoretically
possible could reduce people's enthusiasm for voting and make it more
likely that those who like to vote by just plumping for their favourite
will stay home.

Whereas IRV doesn't just meet mono-add-plump. It also meet Mono-add-Top.

C: Failing mono-add-plump is as stupid as a quasi-"intelligent" device can
be, in a pure and starkly obvious way, and with the lamest possible excuse.

The algorithm/device decides that X should win, and then receives some
more ballots that contain nothing whatsoever but the pure and simple
message:
"You are right! X should win" and responds with the bizarre malfunction
"I've changed my mind, Y should win" and offers the nonsensical excuse "Hey
those
extra ballots didn't just say that X should win. They also increased the
total number of ballots!".

C: What (arguably) desirable properties (or criterion compliances)  are
incompatible with meeting Mono-add-Plump?

Mike: FBC, CD, & wv-like strategy are evidently require failing
Mono-Add-Plump, or having MMPO's Hitler-with-2-votes problem.

With MDDTR, the price of FBC, CD & wv-like strategy is Mono-Add-Plump.

C: There are methods that meet  FBC and CD and mono-add-plump. So your
proposition boils down to saying that it's worth giving up compliance with
mono-add-plump just to gain "wv-like strategy".

Chris Benham

On 11/19/2016 3:14 AM, Michael Ossipoff wrote:

I don't mean that IRV isn't ok. IRV's Mono-Raise failure doesn't bother me.
Neither does MDDTR's Mono-Add-Plump failure.

Voting's purpose is probabilistic anyway. You vote to improve the
probability of a better outcome. The possible nonmonotonicity of IRV
& MDDTR doesn't invalidate that.

My point, in asking about when you make someone lose by raising hir from
last place to 1st place, was just that IRV is popular and widely used. It's
been used in Australia for a long time, and it's used in a fair number of
cities in this country.  ...and now has been adopted by the state of Maine.

...in spite of its Mono-Raise failure.

If the more embarrassing Mono-Raise failure doesn't give IRV any
acceptance or enactment problem, then why should the less embarrassing
Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment
problem?

There of course have been objections to IRV, some valid, some not. But I
haven't heard any of the IRV critics in the various cities complain about
its nonmonotonicity. They object to implementation complexity. They
invalidly claim voting complexity. They invalidly complain because
supposedly voting is supposed to be by Plurality. They repealed IRV in
Burlington because of the elimination of a CWv.  But none of the
complaints that I've heard, in cities using it or considering IRV, have
been about its nonmonotonicity.

Why I say that Mono-Raise failure is more embarrassing:

With MDDTR, if your plump for X makes X lose, it's because you added a
ballot. It has nothing whatsoever to do with the fact that you voted
favorably to X.

With IRV, if raising X from bottom to top makes X lose, then X lost for no
other reason than because you helped hir more.

There are 2 kinds of nonmonotonicity:

Did you make X lose in spite of voting favorably for hir?

or

Did you make X lose because you voted hir more favorably?

Of those 2 kinds of nonmonotonicity the 2nd one is more of an
embarrassment to the method. There, the method is more directly acting
oppositely to your action.

Maybe it could be said that the 2nd kind of nonmonotonicity is twice as
embarrassing to the voting-system.

Anyway, if IRV is so widely used and successful, then why would
nonmonotonicity be a problem for MDDTR?

I now feel that IRV's (mitigated) problem isn't an unusually high price
for CD, isn't more than the "going rate" for CD. IRV & its derivatives are
at the top of my ranking of method-merit for electorates who want &/or need
ranking.

Michael Ossipoff

On Fri, Nov 18, 2016 at 1:23 AM, Michael Ossipoff email9648742@gmail.com
wrote:

Forest--

You wrote:

But MAI still fails FBC.

Failing both FBC & CD isn't good.

So to me the best proposal is ICA with default approval cutoff at
truncation to help punish burial and truncation with an option to raise the
cutoff to withstand a CD attack.

But buriers or truncators could raise that approval cutoff too. Someone
could bury X under Z without having to approve Z. That loses the deterrence
that would exist if that burier had to approve Z in order to rank hir over
someone, as would be so if ranking is counted as approval.

So CD still comes at the cost of a lot less protection against burial,
or, in ICT's case, trunction too.

But that just means that it isn't better than MDDTR in that regard. It
doesn't mean that it's worse.

And it doesn't have Mono-Add-Plump failure.

So, the method has CD as MDDTR does, and trades truncation-proofness for
Mono-Add-Plump.

I value strategy protections more than embarrassment criteria. (But I
realize that proposal-opponents can use embarrassment criteria criticisms,
and that proponents aren't likely to be able to afford as much media time,
to answer the criticisms.)

[Replying farther down] :

Here's my version (slightly different from the original):

Candidate X strongly beats candidate Y iff

the number of ballots on which X is ranked over Y is greater than

the number of ballots on which Y is ranked equal to or greater than Y.

[Note Y is not ranked equal to X if Y is not ranked.]

If not all of the candidates are strongly beaten, disqualify all of the
ones who are.

Elect the most approved qualified candidate.

I think that this method has all of the good properties of MDDA with
mono-add-plump to boot.

I've only had a preliminary look at it, but it seems to me, right now,
that the separate approval-cutoff that the voter can raise from the default
spoils protection from burial & truncation.

You wrote:

We still need to explore MDDA with the half power truncation rule, since
it would also satisfy mono-add-plump if I am not mistaken.

Yes, it seems to me that a 1/2 power-truncation would get rid of the
Mono-Add-Plump failure. If, by not ranking a certain 2 candidates, you give
them each at least half of a vote against eachother, that would bring
Mono-Add-Plump compliance, it seems to me.

So maybe it would avoid criticism of MDDA.

But, if used with MDDTR, it would spoil CD.

You wrote:

I agree with Chris Benham that mono-add-plump failure would be fatal in
a public proposal.

What if you're going to rank X last in your ranking. With all the
ballots, including yours, X will win. But then you move X to 1st place in
your ranking, and that makes X lose.

Would that be ok?

Michael Ossipoff

On Thu, Nov 17, 2016 at 2:12 PM, Michael Ossipoff <
email9648742@gmail.com> wrote:

I meant to ask: Did you say that MTRI doesn't pass FBC? How does FBC
failure happen? In return for FBC, it should beat MDDTR at vulnerability to
burial, and not be vulnerable to truncation.

Anyway, anything you can tell me about the properties comparison
between MTRI & MDDTR would be helpful.

MIchael Ossipoff

On Thu, Nov 17, 2016 at 5:05 PM, Michael Ossipoff <
email9648742@gmail.com> wrote:

For this method, MTRI, the procedural definition is more
understandable than the recursive definition (though the recursive
definition's brevity could be useful).

So this is what I understand MTRI's procedural definition to be:

  1. Order the candidates by their top-count score, with higher scores
    at top.

  2. Switch the lowest pair of adjacent candidates whose lower candidate
    pair-beats the higher one.

Repeat till there are no more pairs to switch. The highest candidate
in the order at that time wins.


As a CD rank method, this method is a competitor of MDDTR. What are
the property differences between MTRI & MDDTR?

In particular, how does MTRI compare with MDDTR in regards to
protection of a CWs against truncation & burial?

Michael Ossipoff

On Thu, Nov 17, 2016 at 2:55 PM, Forest Simmons fsimmons@pcc.edu
wrote:

On Thu, Nov 17, 2016 at 10:54 AM, Michael Ossipoff <
email9648742@gmail.com> wrote:

But wouldn't Smith//Approval, with approval cutoffs in the rankings,
share MDDTR's burial-vullnerability?

...with, additionally, vulnerability to truncation, which MDDTR
doesn't have?

And Smith//Approval trades MDDTR's FBC for Smith, which I consider
an unfavorable trade.

Perhaps make truncation the default approval cutoff, but let voters
move it higher as an option:

45 C
30 A>B or A>>B
25 B

Voting A>>B would be the chicken defense (where sincere is 25 B>A).

Voting A>B would be the truncation defense (where sincere is 45 C>B).

With this option, MDDA would be an FBC compliant method that is
truncation and burial resistant as well as quasi CD compliant.

Is there a way to modify MDDA to make it satisfy mono-add-plump?

How about incorporating some form of power truncation.  When you
plump X and reduce the majority victory of Y over Z to a sub-majority, it
would revert to a majority if you counted the common truncation of Y and Z
against each other as even half a point.

Btw, in case you didn't see it, one of my new favorite non-FBC
methods is Most Approved Immune(MAI):  Elect the most approved immune
candidate.

This means elect the most approved candidate X that is unbeaten
pairwise by the candidate that would win (recursively) if the method were
applied to the same ballot set with X disqualified or withdrawn.

It is the simplest approval based rank method that confers immunity
from second place complaints on its winners.

It is quasi CD compliant if voters can specify their approval cutoffs
above the truncation level when they want to.

A top rank version of this method is fully CD compliant:

Elect the Most Top Ranked Immune candidate. (MTRI)

In other words elect the most top ranked candidate X that is unbeaten
pairwise by the candidate that would win (recursively) if the method were
applied to the same ballot set with X disqualified or withdrawn.

Forest

"Just the knowledge that a failure of Mono-add-Plump is theoretically possible could reduce people's enthusiasm for voting and make it more likely that those who like to vote by just plumping for their favourite will stay home." ...or make you rank your favorite last instead of first in IRV because ranking hir first instead of last could make hir lose? ...or just not vote because you know that IRV can act oppositely to changes in your vote? Michael Ossipoff On Sat, Nov 19, 2016 at 12:18 AM, C.Benham <cbenham@adam.com.au> wrote: > On 11/19/2016 3:14 AM, Michael Ossipoff wrote: > > If the more embarrassing Mono-Raise failure doesn't give IRV any > acceptance or enactment problem, then why should the less embarrassing > Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment > problem? > > > Because what you consider more or less "embarrassing" I am sure isn't in > accord with what most people would find unacceptably ridiculous. > > With MDDTR, if your plump for X makes X lose, it's because you added a > ballot. It has nothing whatsoever to do with the fact that you voted > favorably to X. > > > That's right. "You" should have found some way to vote for X without > adding a ballot. Unfortunately removing someone else's ballot when you are > in the > polling station is usually impossible or legally risky. > > Anyway, if IRV is so widely used and successful, then why would > nonmonotonicity be a problem for MDDTR? > > > Because IRV has a traditional and (for many) intuitive algorithm, and a > solid "maximal" set of criterion compliances and MDDTR doesn't. > > Earlier you attempted to ridicule my observation that MDDTR fails > Irrelevant Ballots Independence by suggesting that might indirectly > motivate a higher > turnout. Well, just as some might have an interest in promoting that (for > voters who'll ignore the competitive/viable candidates) so as to wash away > an otherwise likely majority-defeat disqualification so would opposed > forces have an interest in doing the opposite. > > In fact you could have post-election recriminations reminiscent of those > that were aimed at Nader and those who voted for him supposedly allowing > Bush to > win a few years ago. "Those idiots weren't even really interested in who > won, why didn't they just stay home?!" could be the lament. > > Just the knowledge that a failure of Mono-add-Plump is theoretically > possible could reduce people's enthusiasm for voting and make it more > likely that those who like to vote by just plumping for their favourite > will stay home. > > Whereas IRV doesn't just meet mono-add-plump. It also meet Mono-add-Top. > > C: Failing mono-add-plump is as stupid as a quasi-"intelligent" device can > be, in a pure and starkly obvious way, and with the lamest possible excuse. > > The algorithm/device decides that X should win, and then receives some > more ballots that contain nothing whatsoever but the pure and simple > message: > "You are right! X should win" and responds with the bizarre malfunction > "I've changed my mind, Y should win" and offers the nonsensical excuse "Hey > those > extra ballots didn't just say that X should win. They also increased the > total number of ballots!". > > > C: What (arguably) desirable properties (or criterion compliances) are > incompatible with meeting Mono-add-Plump? > > Mike: FBC, CD, & wv-like strategy are evidently require failing > Mono-Add-Plump, or having MMPO's Hitler-with-2-votes problem. > > With MDDTR, the price of FBC, CD & wv-like strategy is Mono-Add-Plump. > > > C: There are methods that meet FBC and CD and mono-add-plump. So your > proposition boils down to saying that it's worth giving up compliance with > mono-add-plump just to gain "wv-like strategy". > > > Chris Benham > > > > On 11/19/2016 3:14 AM, Michael Ossipoff wrote: > > I don't mean that IRV isn't ok. IRV's Mono-Raise failure doesn't bother me. > Neither does MDDTR's Mono-Add-Plump failure. > > Voting's purpose is probabilistic anyway. You vote to improve the > probability of a better outcome. The possible nonmonotonicity of IRV > & MDDTR doesn't invalidate that. > > My point, in asking about when you make someone lose by raising hir from > last place to 1st place, was just that IRV is popular and widely used. It's > been used in Australia for a long time, and it's used in a fair number of > cities in this country. ...and now has been adopted by the state of Maine. > > ...in spite of its Mono-Raise failure. > > If the more embarrassing Mono-Raise failure doesn't give IRV any > acceptance or enactment problem, then why should the less embarrassing > Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment > problem? > > There of course have been objections to IRV, some valid, some not. But I > haven't heard any of the IRV critics in the various cities complain about > its nonmonotonicity. They object to implementation complexity. They > invalidly claim voting complexity. They invalidly complain because > supposedly voting is supposed to be by Plurality. They repealed IRV in > Burlington because of the elimination of a CWv. But none of the > complaints that I've heard, in cities using it or considering IRV, have > been about its nonmonotonicity. > > Why I say that Mono-Raise failure is more embarrassing: > > With MDDTR, if your plump for X makes X lose, it's because you added a > ballot. It has nothing whatsoever to do with the fact that you voted > favorably to X. > > With IRV, if raising X from bottom to top makes X lose, then X lost for no > other reason than because you helped hir more. > > There are 2 kinds of nonmonotonicity: > > Did you make X lose _in spite of_ voting favorably for hir? > > or > > Did you make X lose _because_ you voted hir more favorably? > > Of those 2 kinds of nonmonotonicity the 2nd one is more of an > embarrassment to the method. There, the method is more directly acting > oppositely to your action. > > Maybe it could be said that the 2nd kind of nonmonotonicity is twice as > embarrassing to the voting-system. > > Anyway, if IRV is so widely used and successful, then why would > nonmonotonicity be a problem for MDDTR? > > I now feel that IRV's (mitigated) problem isn't an unusually high price > for CD, isn't more than the "going rate" for CD. IRV & its derivatives are > at the top of my ranking of method-merit for electorates who want &/or need > ranking. > > Michael Ossipoff > > > > > > > > On Fri, Nov 18, 2016 at 1:23 AM, Michael Ossipoff <email9648742@gmail.com> > wrote: > >> Forest-- >> >> You wrote: >> >>> >>> But MAI still fails FBC. >>> >> >> Failing both FBC & CD isn't good. >> >> >>> >>> So to me the best proposal is ICA with default approval cutoff at >>> truncation to help punish burial and truncation with an option to raise the >>> cutoff to withstand a CD attack. >>> >> >> But buriers or truncators could raise that approval cutoff too. Someone >> could bury X under Z without having to approve Z. That loses the deterrence >> that would exist if that burier had to approve Z in order to rank hir over >> someone, as would be so if ranking is counted as approval. >> >> So CD still comes at the cost of a lot less protection against burial, >> or, in ICT's case, trunction too. >> >> But that just means that it isn't _better_ than MDDTR in that regard. It >> doesn't mean that it's worse. >> >> And it doesn't have Mono-Add-Plump failure. >> >> So, the method has CD as MDDTR does, and trades truncation-proofness for >> Mono-Add-Plump. >> >> I value strategy protections more than embarrassment criteria. (But I >> realize that proposal-opponents can use embarrassment criteria criticisms, >> and that proponents aren't likely to be able to afford as much media time, >> to answer the criticisms.) >> >> [Replying farther down] : >> >> >> >>> >>> Here's my version (slightly different from the original): >>> >>> Candidate X strongly beats candidate Y iff >>> >>> the number of ballots on which X is ranked over Y is greater than >>> >>> the number of ballots on which Y is *ranked* equal to or greater than Y. >>> >>> [Note Y is not ranked equal to X if Y is not ranked.] >>> >>> If not all of the candidates are strongly beaten, disqualify all of the >>> ones who are. >>> >>> Elect the most approved qualified candidate. >>> >>> I think that this method has all of the good properties of MDDA with >>> mono-add-plump to boot. >>> >> >> I've only had a preliminary look at it, but it seems to me, right now, >> that the separate approval-cutoff that the voter can raise from the default >> spoils protection from burial & truncation. >> >> >> You wrote: >> >> >>> We still need to explore MDDA with the half power truncation rule, since >>> it would also satisfy mono-add-plump if I am not mistaken. >>> >> >> Yes, it seems to me that a 1/2 power-truncation would get rid of the >> Mono-Add-Plump failure. If, by not ranking a certain 2 candidates, you give >> them each at least half of a vote against eachother, that would bring >> Mono-Add-Plump compliance, it seems to me. >> >> So maybe it would avoid criticism of MDDA. >> >> But, if used with MDDTR, it would spoil CD. >> >> You wrote: >> >> >> >>> I agree with Chris Benham that mono-add-plump failure would be fatal in >>> a public proposal. >>> >>> >> What if you're going to rank X last in your ranking. With all the >> ballots, including yours, X will win. But then you move X to 1st place in >> your ranking, and that makes X lose. >> >> Would that be ok? >> >> Michael Ossipoff >> >> >> >> >>> On Thu, Nov 17, 2016 at 2:12 PM, Michael Ossipoff < >>> email9648742@gmail.com> wrote: >>> >>>> I meant to ask: Did you say that MTRI doesn't pass FBC? How does FBC >>>> failure happen? In return for FBC, it should beat MDDTR at vulnerability to >>>> burial, and not be vulnerable to truncation. >>>> >>>> Anyway, anything you can tell me about the properties comparison >>>> between MTRI & MDDTR would be helpful. >>>> >>>> MIchael Ossipoff >>>> >>>> On Thu, Nov 17, 2016 at 5:05 PM, Michael Ossipoff < >>>> email9648742@gmail.com> wrote: >>>> >>>>> For this method, MTRI, the procedural definition is more >>>>> understandable than the recursive definition (though the recursive >>>>> definition's brevity could be useful). >>>>> >>>>> So this is what I understand MTRI's procedural definition to be: >>>>> >>>>> 1. Order the candidates by their top-count score, with higher scores >>>>> at top. >>>>> >>>>> 2. Switch the lowest pair of adjacent candidates whose lower candidate >>>>> pair-beats the higher one. >>>>> >>>>> Repeat till there are no more pairs to switch. The highest candidate >>>>> in the order at that time wins. >>>>> >>>>> ----------------------------------------------- >>>>> >>>>> As a CD rank method, this method is a competitor of MDDTR. What are >>>>> the property differences between MTRI & MDDTR? >>>>> >>>>> In particular, how does MTRI compare with MDDTR in regards to >>>>> protection of a CWs against truncation & burial? >>>>> >>>>> Michael Ossipoff >>>>> >>>>> >>>>> On Thu, Nov 17, 2016 at 2:55 PM, Forest Simmons <fsimmons@pcc.edu> >>>>> wrote: >>>>> >>>>>> On Thu, Nov 17, 2016 at 10:54 AM, Michael Ossipoff < >>>>>> email9648742@gmail.com> wrote: >>>>>> >>>>>>> But wouldn't Smith//Approval, with approval cutoffs in the rankings, >>>>>>> share MDDTR's burial-vullnerability? >>>>>>> >>>>>>> ...with, additionally, vulnerability to truncation, which MDDTR >>>>>>> _doesn't_ have? >>>>>>> >>>>>>> And Smith//Approval trades MDDTR's FBC for Smith, which I consider >>>>>>> an unfavorable trade. >>>>>>> >>>>>> >>>>>> Perhaps make truncation the default approval cutoff, but let voters >>>>>> move it higher as an option: >>>>>> >>>>>> 45 C >>>>>> 30 A>B or A>>B >>>>>> 25 B >>>>>> >>>>>> Voting A>>B would be the chicken defense (where sincere is 25 B>A). >>>>>> >>>>>> Voting A>B would be the truncation defense (where sincere is 45 C>B). >>>>>> >>>>>> With this option, MDDA would be an FBC compliant method that is >>>>>> truncation and burial resistant as well as quasi CD compliant. >>>>>> >>>>>> Is there a way to modify MDDA to make it satisfy mono-add-plump? >>>>>> >>>>>> How about incorporating some form of power truncation. When you >>>>>> plump X and reduce the majority victory of Y over Z to a sub-majority, it >>>>>> would revert to a majority if you counted the common truncation of Y and Z >>>>>> against each other as even half a point. >>>>>> >>>>>> Btw, in case you didn't see it, one of my new favorite non-FBC >>>>>> methods is Most Approved Immune(MAI): Elect the most approved immune >>>>>> candidate. >>>>>> >>>>>> This means elect the most approved candidate X that is unbeaten >>>>>> pairwise by the candidate that would win (recursively) if the method were >>>>>> applied to the same ballot set with X disqualified or withdrawn. >>>>>> >>>>>> It is the simplest approval based rank method that confers immunity >>>>>> from second place complaints on its winners. >>>>>> >>>>>> It is quasi CD compliant if voters can specify their approval cutoffs >>>>>> above the truncation level when they want to. >>>>>> >>>>>> A top rank version of this method is fully CD compliant: >>>>>> >>>>>> Elect the Most Top Ranked Immune candidate. (MTRI) >>>>>> >>>>>> In other words elect the most top ranked candidate X that is unbeaten >>>>>> pairwise by the candidate that would win (recursively) if the method were >>>>>> applied to the same ballot set with X disqualified or withdrawn. >>>>>> >>>>>> Forest >>>>>> >>>>>> >>>>> >>>> >>> >> > > >
MP
Monkey Puzzle
Mon, Nov 21, 2016 11:29 PM

Forest, Michael, Chris:

It seems that you are converging toward consensus on a modified version of
ICA that is equivalent to MDDTR(pt/2), if

Both these methods have scattered definitions on the list that go back
years, and the current discussion has moved toward something different than
the ICA description here:
http://wiki.electorama.com/wiki/Improved_Condorcet_Approval .

Would it be possible to have a concise restatement/correction of the
method(s) somewhere, preferably on electorama?

Thank you!

Frango ut patefaciam -- I break so that I may reveal

On Mon, Nov 21, 2016 at 3:03 PM, Michael Ossipoff email9648742@gmail.com
wrote:

"Just the knowledge that a failure of Mono-add-Plump  is theoretically
possible could reduce people's enthusiasm for voting and make it more
likely that those who like to vote by just plumping for their favourite
will stay home."

...or make you rank your favorite last instead of first in IRV because
ranking hir first instead of last could make hir lose?

...or just not vote because you know that IRV can act oppositely to
changes in your vote?

Michael Ossipoff

On Sat, Nov 19, 2016 at 12:18 AM, C.Benham cbenham@adam.com.au wrote:

On 11/19/2016 3:14 AM, Michael Ossipoff wrote:

If the more embarrassing Mono-Raise failure doesn't give IRV any
acceptance or enactment problem, then why should the less embarrassing
Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment
problem?

Because what you consider more or less "embarrassing" I am sure isn't in
accord with what most people would find unacceptably ridiculous.

With MDDTR, if your plump for X makes X lose, it's because you added a
ballot. It has nothing whatsoever to do with the fact that you voted
favorably to X.

That's right. "You" should have found some way to vote for X without
adding a ballot. Unfortunately removing someone else's ballot when you are
in the
polling station is usually impossible or legally risky.

Anyway, if IRV is so widely used and successful, then why would
nonmonotonicity be a problem for MDDTR?

Because IRV has a traditional and (for many) intuitive algorithm, and a
solid "maximal"  set of criterion compliances and MDDTR doesn't.

Earlier you attempted to ridicule my observation that MDDTR fails
Irrelevant Ballots Independence by suggesting that might indirectly
motivate a higher
turnout.  Well, just as some might have an interest in promoting that
(for voters who'll ignore the competitive/viable candidates) so as to wash
away
an otherwise likely majority-defeat disqualification so would opposed
forces have an interest in doing the opposite.

In fact you could have post-election recriminations reminiscent of those
that were aimed at Nader and those who voted for him supposedly allowing
Bush to
win a few years ago. "Those idiots weren't even really interested in who
won, why didn't they just stay home?!" could be the lament.

Just the knowledge that a failure of Mono-add-Plump  is theoretically
possible could reduce people's enthusiasm for voting and make it more
likely that those who like to vote by just plumping for their favourite
will stay home.

Whereas IRV doesn't just meet mono-add-plump. It also meet Mono-add-Top.

C: Failing mono-add-plump is as stupid as a quasi-"intelligent" device
can be, in a pure and starkly obvious way, and with the lamest possible
excuse.

The algorithm/device decides that X should win, and then receives some
more ballots that contain nothing whatsoever but the pure and simple
message:
"You are right! X should win" and responds with the bizarre malfunction
"I've changed my mind, Y should win" and offers the nonsensical excuse "Hey
those
extra ballots didn't just say that X should win. They also increased the
total number of ballots!".

C: What (arguably) desirable properties (or criterion compliances)  are
incompatible with meeting Mono-add-Plump?

Mike: FBC, CD, & wv-like strategy are evidently require failing
Mono-Add-Plump, or having MMPO's Hitler-with-2-votes problem.

With MDDTR, the price of FBC, CD & wv-like strategy is Mono-Add-Plump.

C: There are methods that meet  FBC and CD and mono-add-plump. So your
proposition boils down to saying that it's worth giving up compliance with
mono-add-plump just to gain "wv-like strategy".

Chris Benham

On 11/19/2016 3:14 AM, Michael Ossipoff wrote:

I don't mean that IRV isn't ok. IRV's Mono-Raise failure doesn't bother
me.
Neither does MDDTR's Mono-Add-Plump failure.

Voting's purpose is probabilistic anyway. You vote to improve the
probability of a better outcome. The possible nonmonotonicity of IRV
& MDDTR doesn't invalidate that.

My point, in asking about when you make someone lose by raising hir from
last place to 1st place, was just that IRV is popular and widely used. It's
been used in Australia for a long time, and it's used in a fair number of
cities in this country.  ...and now has been adopted by the state of Maine.

...in spite of its Mono-Raise failure.

If the more embarrassing Mono-Raise failure doesn't give IRV any
acceptance or enactment problem, then why should the less embarrassing
Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment
problem?

There of course have been objections to IRV, some valid, some not. But I
haven't heard any of the IRV critics in the various cities complain about
its nonmonotonicity. They object to implementation complexity. They
invalidly claim voting complexity. They invalidly complain because
supposedly voting is supposed to be by Plurality. They repealed IRV in
Burlington because of the elimination of a CWv.  But none of the
complaints that I've heard, in cities using it or considering IRV, have
been about its nonmonotonicity.

Why I say that Mono-Raise failure is more embarrassing:

With MDDTR, if your plump for X makes X lose, it's because you added a
ballot. It has nothing whatsoever to do with the fact that you voted
favorably to X.

With IRV, if raising X from bottom to top makes X lose, then X lost for
no other reason than because you helped hir more.

There are 2 kinds of nonmonotonicity:

Did you make X lose in spite of voting favorably for hir?

or

Did you make X lose because you voted hir more favorably?

Of those 2 kinds of nonmonotonicity the 2nd one is more of an
embarrassment to the method. There, the method is more directly acting
oppositely to your action.

Maybe it could be said that the 2nd kind of nonmonotonicity is twice as
embarrassing to the voting-system.

Anyway, if IRV is so widely used and successful, then why would
nonmonotonicity be a problem for MDDTR?

I now feel that IRV's (mitigated) problem isn't an unusually high price
for CD, isn't more than the "going rate" for CD. IRV & its derivatives are
at the top of my ranking of method-merit for electorates who want &/or need
ranking.

Michael Ossipoff

On Fri, Nov 18, 2016 at 1:23 AM, Michael Ossipoff <email9648742@gmail.com

wrote:

Forest--

You wrote:

But MAI still fails FBC.

Failing both FBC & CD isn't good.

So to me the best proposal is ICA with default approval cutoff at
truncation to help punish burial and truncation with an option to raise the
cutoff to withstand a CD attack.

But buriers or truncators could raise that approval cutoff too. Someone
could bury X under Z without having to approve Z. That loses the deterrence
that would exist if that burier had to approve Z in order to rank hir over
someone, as would be so if ranking is counted as approval.

So CD still comes at the cost of a lot less protection against burial,
or, in ICT's case, trunction too.

But that just means that it isn't better than MDDTR in that regard. It
doesn't mean that it's worse.

And it doesn't have Mono-Add-Plump failure.

So, the method has CD as MDDTR does, and trades truncation-proofness for
Mono-Add-Plump.

I value strategy protections more than embarrassment criteria. (But I
realize that proposal-opponents can use embarrassment criteria criticisms,
and that proponents aren't likely to be able to afford as much media time,
to answer the criticisms.)

[Replying farther down] :

Here's my version (slightly different from the original):

Candidate X strongly beats candidate Y iff

the number of ballots on which X is ranked over Y is greater than

the number of ballots on which Y is ranked equal to or greater than
Y.

[Note Y is not ranked equal to X if Y is not ranked.]

If not all of the candidates are strongly beaten, disqualify all of the
ones who are.

Elect the most approved qualified candidate.

I think that this method has all of the good properties of MDDA with
mono-add-plump to boot.

I've only had a preliminary look at it, but it seems to me, right now,
that the separate approval-cutoff that the voter can raise from the default
spoils protection from burial & truncation.

You wrote:

We still need to explore MDDA with the half power truncation rule,
since it would also satisfy mono-add-plump if I am not mistaken.

Yes, it seems to me that a 1/2 power-truncation would get rid of the
Mono-Add-Plump failure. If, by not ranking a certain 2 candidates, you give
them each at least half of a vote against eachother, that would bring
Mono-Add-Plump compliance, it seems to me.

So maybe it would avoid criticism of MDDA.

But, if used with MDDTR, it would spoil CD.

You wrote:

I agree with Chris Benham that mono-add-plump failure would be fatal in
a public proposal.

What if you're going to rank X last in your ranking. With all the
ballots, including yours, X will win. But then you move X to 1st place in
your ranking, and that makes X lose.

Would that be ok?

Michael Ossipoff

On Thu, Nov 17, 2016 at 2:12 PM, Michael Ossipoff <
email9648742@gmail.com> wrote:

I meant to ask: Did you say that MTRI doesn't pass FBC? How does FBC
failure happen? In return for FBC, it should beat MDDTR at vulnerability to
burial, and not be vulnerable to truncation.

Anyway, anything you can tell me about the properties comparison
between MTRI & MDDTR would be helpful.

MIchael Ossipoff

On Thu, Nov 17, 2016 at 5:05 PM, Michael Ossipoff <
email9648742@gmail.com> wrote:

For this method, MTRI, the procedural definition is more
understandable than the recursive definition (though the recursive
definition's brevity could be useful).

So this is what I understand MTRI's procedural definition to be:

  1. Order the candidates by their top-count score, with higher scores
    at top.

  2. Switch the lowest pair of adjacent candidates whose lower
    candidate pair-beats the higher one.

Repeat till there are no more pairs to switch. The highest candidate
in the order at that time wins.


As a CD rank method, this method is a competitor of MDDTR. What are
the property differences between MTRI & MDDTR?

In particular, how does MTRI compare with MDDTR in regards to
protection of a CWs against truncation & burial?

Michael Ossipoff

On Thu, Nov 17, 2016 at 2:55 PM, Forest Simmons fsimmons@pcc.edu
wrote:

On Thu, Nov 17, 2016 at 10:54 AM, Michael Ossipoff <
email9648742@gmail.com> wrote:

But wouldn't Smith//Approval, with approval cutoffs in the
rankings, share MDDTR's burial-vullnerability?

...with, additionally, vulnerability to truncation, which MDDTR
doesn't have?

And Smith//Approval trades MDDTR's FBC for Smith, which I consider
an unfavorable trade.

Perhaps make truncation the default approval cutoff, but let voters
move it higher as an option:

45 C
30 A>B or A>>B
25 B

Voting A>>B would be the chicken defense (where sincere is 25 B>A).

Voting A>B would be the truncation defense (where sincere is 45 C>B).

With this option, MDDA would be an FBC compliant method that is
truncation and burial resistant as well as quasi CD compliant.

Is there a way to modify MDDA to make it satisfy mono-add-plump?

How about incorporating some form of power truncation.  When you
plump X and reduce the majority victory of Y over Z to a sub-majority, it
would revert to a majority if you counted the common truncation of Y and Z
against each other as even half a point.

Btw, in case you didn't see it, one of my new favorite non-FBC
methods is Most Approved Immune(MAI):  Elect the most approved immune
candidate.

This means elect the most approved candidate X that is unbeaten
pairwise by the candidate that would win (recursively) if the method were
applied to the same ballot set with X disqualified or withdrawn.

It is the simplest approval based rank method that confers immunity
from second place complaints on its winners.

It is quasi CD compliant if voters can specify their approval
cutoffs above the truncation level when they want to.

A top rank version of this method is fully CD compliant:

Elect the Most Top Ranked Immune candidate. (MTRI)

In other words elect the most top ranked candidate X that is
unbeaten pairwise by the candidate that would win (recursively) if the
method were applied to the same ballot set with X disqualified or withdrawn.

Forest


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

Forest, Michael, Chris: It seems that you are converging toward consensus on a modified version of ICA that is equivalent to MDDTR(pt/2), if Both these methods have scattered definitions on the list that go back years, and the current discussion has moved toward something different than the ICA description here: http://wiki.electorama.com/wiki/Improved_Condorcet_Approval . Would it be possible to have a concise restatement/correction of the method(s) somewhere, preferably on electorama? Thank you! Frango ut patefaciam -- I break so that I may reveal On Mon, Nov 21, 2016 at 3:03 PM, Michael Ossipoff <email9648742@gmail.com> wrote: > "Just the knowledge that a failure of Mono-add-Plump is theoretically > possible could reduce people's enthusiasm for voting and make it more > likely that those who like to vote by just plumping for their favourite > will stay home." > > ...or make you rank your favorite last instead of first in IRV because > ranking hir first instead of last could make hir lose? > > ...or just not vote because you know that IRV can act oppositely to > changes in your vote? > > Michael Ossipoff > > On Sat, Nov 19, 2016 at 12:18 AM, C.Benham <cbenham@adam.com.au> wrote: > >> On 11/19/2016 3:14 AM, Michael Ossipoff wrote: >> >> If the more embarrassing Mono-Raise failure doesn't give IRV any >> acceptance or enactment problem, then why should the less embarrassing >> Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment >> problem? >> >> >> Because what you consider more or less "embarrassing" I am sure isn't in >> accord with what most people would find unacceptably ridiculous. >> >> With MDDTR, if your plump for X makes X lose, it's because you added a >> ballot. It has nothing whatsoever to do with the fact that you voted >> favorably to X. >> >> >> That's right. "You" should have found some way to vote for X without >> adding a ballot. Unfortunately removing someone else's ballot when you are >> in the >> polling station is usually impossible or legally risky. >> >> Anyway, if IRV is so widely used and successful, then why would >> nonmonotonicity be a problem for MDDTR? >> >> >> Because IRV has a traditional and (for many) intuitive algorithm, and a >> solid "maximal" set of criterion compliances and MDDTR doesn't. >> >> Earlier you attempted to ridicule my observation that MDDTR fails >> Irrelevant Ballots Independence by suggesting that might indirectly >> motivate a higher >> turnout. Well, just as some might have an interest in promoting that >> (for voters who'll ignore the competitive/viable candidates) so as to wash >> away >> an otherwise likely majority-defeat disqualification so would opposed >> forces have an interest in doing the opposite. >> >> In fact you could have post-election recriminations reminiscent of those >> that were aimed at Nader and those who voted for him supposedly allowing >> Bush to >> win a few years ago. "Those idiots weren't even really interested in who >> won, why didn't they just stay home?!" could be the lament. >> >> Just the knowledge that a failure of Mono-add-Plump is theoretically >> possible could reduce people's enthusiasm for voting and make it more >> likely that those who like to vote by just plumping for their favourite >> will stay home. >> >> Whereas IRV doesn't just meet mono-add-plump. It also meet Mono-add-Top. >> >> C: Failing mono-add-plump is as stupid as a quasi-"intelligent" device >> can be, in a pure and starkly obvious way, and with the lamest possible >> excuse. >> >> The algorithm/device decides that X should win, and then receives some >> more ballots that contain nothing whatsoever but the pure and simple >> message: >> "You are right! X should win" and responds with the bizarre malfunction >> "I've changed my mind, Y should win" and offers the nonsensical excuse "Hey >> those >> extra ballots didn't just say that X should win. They also increased the >> total number of ballots!". >> >> >> C: What (arguably) desirable properties (or criterion compliances) are >> incompatible with meeting Mono-add-Plump? >> >> Mike: FBC, CD, & wv-like strategy are evidently require failing >> Mono-Add-Plump, or having MMPO's Hitler-with-2-votes problem. >> >> With MDDTR, the price of FBC, CD & wv-like strategy is Mono-Add-Plump. >> >> >> C: There are methods that meet FBC and CD and mono-add-plump. So your >> proposition boils down to saying that it's worth giving up compliance with >> mono-add-plump just to gain "wv-like strategy". >> >> >> Chris Benham >> >> >> >> On 11/19/2016 3:14 AM, Michael Ossipoff wrote: >> >> I don't mean that IRV isn't ok. IRV's Mono-Raise failure doesn't bother >> me. >> Neither does MDDTR's Mono-Add-Plump failure. >> >> Voting's purpose is probabilistic anyway. You vote to improve the >> probability of a better outcome. The possible nonmonotonicity of IRV >> & MDDTR doesn't invalidate that. >> >> My point, in asking about when you make someone lose by raising hir from >> last place to 1st place, was just that IRV is popular and widely used. It's >> been used in Australia for a long time, and it's used in a fair number of >> cities in this country. ...and now has been adopted by the state of Maine. >> >> ...in spite of its Mono-Raise failure. >> >> If the more embarrassing Mono-Raise failure doesn't give IRV any >> acceptance or enactment problem, then why should the less embarrassing >> Mono-Add-Plump failure of MDDTR give MDDTR an acceptance or enactment >> problem? >> >> There of course have been objections to IRV, some valid, some not. But I >> haven't heard any of the IRV critics in the various cities complain about >> its nonmonotonicity. They object to implementation complexity. They >> invalidly claim voting complexity. They invalidly complain because >> supposedly voting is supposed to be by Plurality. They repealed IRV in >> Burlington because of the elimination of a CWv. But none of the >> complaints that I've heard, in cities using it or considering IRV, have >> been about its nonmonotonicity. >> >> Why I say that Mono-Raise failure is more embarrassing: >> >> With MDDTR, if your plump for X makes X lose, it's because you added a >> ballot. It has nothing whatsoever to do with the fact that you voted >> favorably to X. >> >> With IRV, if raising X from bottom to top makes X lose, then X lost for >> no other reason than because you helped hir more. >> >> There are 2 kinds of nonmonotonicity: >> >> Did you make X lose _in spite of_ voting favorably for hir? >> >> or >> >> Did you make X lose _because_ you voted hir more favorably? >> >> Of those 2 kinds of nonmonotonicity the 2nd one is more of an >> embarrassment to the method. There, the method is more directly acting >> oppositely to your action. >> >> Maybe it could be said that the 2nd kind of nonmonotonicity is twice as >> embarrassing to the voting-system. >> >> Anyway, if IRV is so widely used and successful, then why would >> nonmonotonicity be a problem for MDDTR? >> >> I now feel that IRV's (mitigated) problem isn't an unusually high price >> for CD, isn't more than the "going rate" for CD. IRV & its derivatives are >> at the top of my ranking of method-merit for electorates who want &/or need >> ranking. >> >> Michael Ossipoff >> >> >> >> >> >> >> >> On Fri, Nov 18, 2016 at 1:23 AM, Michael Ossipoff <email9648742@gmail.com >> > wrote: >> >>> Forest-- >>> >>> You wrote: >>> >>>> >>>> But MAI still fails FBC. >>>> >>> >>> Failing both FBC & CD isn't good. >>> >>> >>>> >>>> So to me the best proposal is ICA with default approval cutoff at >>>> truncation to help punish burial and truncation with an option to raise the >>>> cutoff to withstand a CD attack. >>>> >>> >>> But buriers or truncators could raise that approval cutoff too. Someone >>> could bury X under Z without having to approve Z. That loses the deterrence >>> that would exist if that burier had to approve Z in order to rank hir over >>> someone, as would be so if ranking is counted as approval. >>> >>> So CD still comes at the cost of a lot less protection against burial, >>> or, in ICT's case, trunction too. >>> >>> But that just means that it isn't _better_ than MDDTR in that regard. It >>> doesn't mean that it's worse. >>> >>> And it doesn't have Mono-Add-Plump failure. >>> >>> So, the method has CD as MDDTR does, and trades truncation-proofness for >>> Mono-Add-Plump. >>> >>> I value strategy protections more than embarrassment criteria. (But I >>> realize that proposal-opponents can use embarrassment criteria criticisms, >>> and that proponents aren't likely to be able to afford as much media time, >>> to answer the criticisms.) >>> >>> [Replying farther down] : >>> >>> >>> >>>> >>>> Here's my version (slightly different from the original): >>>> >>>> Candidate X strongly beats candidate Y iff >>>> >>>> the number of ballots on which X is ranked over Y is greater than >>>> >>>> the number of ballots on which Y is *ranked* equal to or greater than >>>> Y. >>>> >>>> [Note Y is not ranked equal to X if Y is not ranked.] >>>> >>>> If not all of the candidates are strongly beaten, disqualify all of the >>>> ones who are. >>>> >>>> Elect the most approved qualified candidate. >>>> >>>> I think that this method has all of the good properties of MDDA with >>>> mono-add-plump to boot. >>>> >>> >>> I've only had a preliminary look at it, but it seems to me, right now, >>> that the separate approval-cutoff that the voter can raise from the default >>> spoils protection from burial & truncation. >>> >>> >>> You wrote: >>> >>> >>>> We still need to explore MDDA with the half power truncation rule, >>>> since it would also satisfy mono-add-plump if I am not mistaken. >>>> >>> >>> Yes, it seems to me that a 1/2 power-truncation would get rid of the >>> Mono-Add-Plump failure. If, by not ranking a certain 2 candidates, you give >>> them each at least half of a vote against eachother, that would bring >>> Mono-Add-Plump compliance, it seems to me. >>> >>> So maybe it would avoid criticism of MDDA. >>> >>> But, if used with MDDTR, it would spoil CD. >>> >>> You wrote: >>> >>> >>> >>>> I agree with Chris Benham that mono-add-plump failure would be fatal in >>>> a public proposal. >>>> >>>> >>> What if you're going to rank X last in your ranking. With all the >>> ballots, including yours, X will win. But then you move X to 1st place in >>> your ranking, and that makes X lose. >>> >>> Would that be ok? >>> >>> Michael Ossipoff >>> >>> >>> >>> >>>> On Thu, Nov 17, 2016 at 2:12 PM, Michael Ossipoff < >>>> email9648742@gmail.com> wrote: >>>> >>>>> I meant to ask: Did you say that MTRI doesn't pass FBC? How does FBC >>>>> failure happen? In return for FBC, it should beat MDDTR at vulnerability to >>>>> burial, and not be vulnerable to truncation. >>>>> >>>>> Anyway, anything you can tell me about the properties comparison >>>>> between MTRI & MDDTR would be helpful. >>>>> >>>>> MIchael Ossipoff >>>>> >>>>> On Thu, Nov 17, 2016 at 5:05 PM, Michael Ossipoff < >>>>> email9648742@gmail.com> wrote: >>>>> >>>>>> For this method, MTRI, the procedural definition is more >>>>>> understandable than the recursive definition (though the recursive >>>>>> definition's brevity could be useful). >>>>>> >>>>>> So this is what I understand MTRI's procedural definition to be: >>>>>> >>>>>> 1. Order the candidates by their top-count score, with higher scores >>>>>> at top. >>>>>> >>>>>> 2. Switch the lowest pair of adjacent candidates whose lower >>>>>> candidate pair-beats the higher one. >>>>>> >>>>>> Repeat till there are no more pairs to switch. The highest candidate >>>>>> in the order at that time wins. >>>>>> >>>>>> ----------------------------------------------- >>>>>> >>>>>> As a CD rank method, this method is a competitor of MDDTR. What are >>>>>> the property differences between MTRI & MDDTR? >>>>>> >>>>>> In particular, how does MTRI compare with MDDTR in regards to >>>>>> protection of a CWs against truncation & burial? >>>>>> >>>>>> Michael Ossipoff >>>>>> >>>>>> >>>>>> On Thu, Nov 17, 2016 at 2:55 PM, Forest Simmons <fsimmons@pcc.edu> >>>>>> wrote: >>>>>> >>>>>>> On Thu, Nov 17, 2016 at 10:54 AM, Michael Ossipoff < >>>>>>> email9648742@gmail.com> wrote: >>>>>>> >>>>>>>> But wouldn't Smith//Approval, with approval cutoffs in the >>>>>>>> rankings, share MDDTR's burial-vullnerability? >>>>>>>> >>>>>>>> ...with, additionally, vulnerability to truncation, which MDDTR >>>>>>>> _doesn't_ have? >>>>>>>> >>>>>>>> And Smith//Approval trades MDDTR's FBC for Smith, which I consider >>>>>>>> an unfavorable trade. >>>>>>>> >>>>>>> >>>>>>> Perhaps make truncation the default approval cutoff, but let voters >>>>>>> move it higher as an option: >>>>>>> >>>>>>> 45 C >>>>>>> 30 A>B or A>>B >>>>>>> 25 B >>>>>>> >>>>>>> Voting A>>B would be the chicken defense (where sincere is 25 B>A). >>>>>>> >>>>>>> Voting A>B would be the truncation defense (where sincere is 45 C>B). >>>>>>> >>>>>>> With this option, MDDA would be an FBC compliant method that is >>>>>>> truncation and burial resistant as well as quasi CD compliant. >>>>>>> >>>>>>> Is there a way to modify MDDA to make it satisfy mono-add-plump? >>>>>>> >>>>>>> How about incorporating some form of power truncation. When you >>>>>>> plump X and reduce the majority victory of Y over Z to a sub-majority, it >>>>>>> would revert to a majority if you counted the common truncation of Y and Z >>>>>>> against each other as even half a point. >>>>>>> >>>>>>> Btw, in case you didn't see it, one of my new favorite non-FBC >>>>>>> methods is Most Approved Immune(MAI): Elect the most approved immune >>>>>>> candidate. >>>>>>> >>>>>>> This means elect the most approved candidate X that is unbeaten >>>>>>> pairwise by the candidate that would win (recursively) if the method were >>>>>>> applied to the same ballot set with X disqualified or withdrawn. >>>>>>> >>>>>>> It is the simplest approval based rank method that confers immunity >>>>>>> from second place complaints on its winners. >>>>>>> >>>>>>> It is quasi CD compliant if voters can specify their approval >>>>>>> cutoffs above the truncation level when they want to. >>>>>>> >>>>>>> A top rank version of this method is fully CD compliant: >>>>>>> >>>>>>> Elect the Most Top Ranked Immune candidate. (MTRI) >>>>>>> >>>>>>> In other words elect the most top ranked candidate X that is >>>>>>> unbeaten pairwise by the candidate that would win (recursively) if the >>>>>>> method were applied to the same ballot set with X disqualified or withdrawn. >>>>>>> >>>>>>> Forest >>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >> >> > > ---- > Election-Methods mailing list - see http://electorama.com/em for list info > >