FBPPAR: Difference between revisions

From electowiki
Content added Content deleted
VisualWikitext
imported>Homunq
No edit summary
m (fbc category)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The following system is called FBPPAR voting, for "Favorite-Betrayal-Proof Prefer Accept Reject". It is a version of [[PAR voting]], with an extra "stand aside" option in order to pass the [[favorite betrayal criterion]] (FBC).
The following system is called FBPPAR voting, for "Favorite-Betrayal-Proof Prefer Accept Reject". It is a version of [[PAR voting]], with an extra "stand aside" option in order to pass the [[favorite betrayal criterion]] (FBC).


Here's the procedure. Note that the two steps with extra indentation (1.1 and 3.1) only rarely matter, so it's best to understand the system without them first.
# Voters can Prefer, Accept, or Reject each candidate. Default is "Reject" for voters who do not explicitly reject any candidates, and "Accept" otherwise.
## For any candidate they prefer, voters may also check "stand aside". (This is rarely useful; it is only worthwhile if they think that the candidate might become the leader in step 3 and stand in the way of a stronger compromise leader.) "Stand aside" has no effect if it is checked along with any option other than "prefer", or with no option.
# Candidates get 1 point for every ballot that prefers them.
⚫
# Candidates with over 25% Prefer, and less than 50% Reject, are called viable. The viable candidates (if any) with the most non-stand-aside preferences is given the label of leader.
## If the leader would not have been viable counting all "prefer/stand aside" votes as "reject", then the label of leader switches to the next lower candidate in non-stand-aside preferences.
# Viable candidates get 1 point for every ballot that accepts them and does not prefer the leader.
# Winner is the highest score.


# '''Voters Prefer, Accept, or Reject each candidate.''' On ballots which don't explicitly use "Reject", blanks count as "Reject"; otherwise, blanks count as "Accept".
⚫
This is largely a theoretical proposal. In real-world elections, the "stand aside" option would probably almost never be useful; certainly not enough to justify the extra complexity.
## For candidates a voter prefers, they may also mark a "stand aside" option. This has no effect when combined with "accept" or "reject". It is useful for those rare cases when you prefer a candidate, and think they would be the leader in step 2, but do not think they can actually win; so that you think you'd be better off if voters like you compromise more.
⚫
# '''Candidates with at least 25% Prefer, and no more than 50% reject, are "viable"'''. The most-preferred viable candidate (if any) is the leader.
## When designating the leader (including who counts as "viable" for that purpose only), all "prefer/stand aside" votes count as if they were "reject".
# Each "prefer" is worth 1 point. For viable candidates, each "accept" on a ballot which doesn't prefer the leader is also worth 1 point. '''Most points wins.'''

⚫
This is largely a theoretical proposal. In real-world elections, the "stand aside" option would probably almost never be useful enough to justify the extra complexity.


For instance, consider the voting scenarios which meet the following restrictions:
For instance, consider the voting scenarios which meet the following restrictions:
Line 21: Line 21:




[[Category:Graded Bucklin systems]]
[[Category:Graded Bucklin methods]]
[[Category:No-favorite-betrayal electoral systems]]
{{DEFAULTSORT:PARFBP}}
{{DEFAULTSORT:PARFBP}}

Latest revision as of 12:39, 21 July 2022

The following system is called FBPPAR voting, for "Favorite-Betrayal-Proof Prefer Accept Reject". It is a version of PAR voting, with an extra "stand aside" option in order to pass the favorite betrayal criterion (FBC).

Here's the procedure. Note that the two steps with extra indentation (1.1 and 3.1) only rarely matter, so it's best to understand the system without them first.

  1. Voters Prefer, Accept, or Reject each candidate. On ballots which don't explicitly use "Reject", blanks count as "Reject"; otherwise, blanks count as "Accept".
    1. For candidates a voter prefers, they may also mark a "stand aside" option. This has no effect when combined with "accept" or "reject". It is useful for those rare cases when you prefer a candidate, and think they would be the leader in step 2, but do not think they can actually win; so that you think you'd be better off if voters like you compromise more.
  2. Candidates with at least 25% Prefer, and no more than 50% reject, are "viable". The most-preferred viable candidate (if any) is the leader.
    1. When designating the leader (including who counts as "viable" for that purpose only), all "prefer/stand aside" votes count as if they were "reject".
  3. Each "prefer" is worth 1 point. For viable candidates, each "accept" on a ballot which doesn't prefer the leader is also worth 1 point. Most points wins.

This is largely a theoretical proposal. In real-world elections, the "stand aside" option would probably almost never be useful enough to justify the extra complexity.

For instance, consider the voting scenarios which meet the following restrictions:

  1. Each candidate either comes from one of no more than 3 "ideological categories", or is "nonviable".
  2. No "nonviable" candidate is preferred by more than 25%.
  3. Each voter rejects at least one of the 3 "ideological categories" (that is, rejects all candidates in that category), and accepts or prefers all candidates in some other category.
  4. No honest Condorcet cycles.

If the above restrictions hold, then the "compromise" option would never be strategically favored, and so simple PAR voting would meet FBC. It is arguably likely that real-world voting scenarios will meet the above restrictions, except for a negligible fraction of "ideologically atypical" voters. Thus, as a real-world proposal, PAR voting's greater simplicity makes it better than FBPPAR.

Retrieved from "https://electowiki.org/wiki/FBPPAR?oldid=16158"