-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instructions were unclear #1
Comments
Thanks for your feedback, there hasn't been a lot of user testing. I totally agree that it may be confusing. Do you have concrete suggestions how the instructions should be altered? I made some changes already. |
Not sure, I'll try and get round to doing some proper thinking on it :) |
I found it so confusing and difficult to use that I had to fork it - my fork allows you to enter the list indexed by order of preference - e.g. if the icecream list is: Chocolate, Vanilla, Strawberry, and your favorites are Vanilla, Strawberry, Chocolate - you enter "2,3,1" rather than what this system would call for, which is: "3,1,2". The big advantage of my fork, though, is that it allows entry of just "3" if your favorite is just Strawberry, and it will assign zeros to anything following it - which would be equivalent to an entry of "0,0,1". |
@cmcnulty I try to explain the logic behind the current way of doing it. This IRV site was created to help count paper ballots and thus optimizes for transcribing paper ballots. A paper ballot has a list of Your input format is certainly more intuitive to understand, I think it could be even better when you replace numbers with the actual candidate names! But unfortunately it doesn't line up with what I wrote before. If you like, we could merge something like that as an alternative input method. |
I completely understand now - it's all about how the ballots are distributed and how the votes are collected - I optimized for the case where, for instance, a numbered list is sent out via e-mail, with instructions to send back a list of numbers in the order of preference. Your code is optimized for a situation with a printed ballot with instructions to add a number next to each line on the ballot indicating order of preference. In the end the code to translate between the two methods is pretty trivial - I think the best direction for this project, to be honest, would be to split the vote handling code into it's own nodeJS module, and handle the ballot parsing in a separate UI only project. |
Candidates
Ballots
Actual result
Expected result If this issue can be dismissed by my lack of knowledge - feel free. To me this seems wrong. |
@hfossli-agens As Hollande lost round 1 now for every ballot with Hollande as "first votes" the "second votes" will become the new "first votes". In this case Merkel gets two extract "first votes". Did you expect it to remain a tie? It is the concept of IRV to still consider the preferences of ballots that didn't get their first wish. |
I expected obama and merkel to tie with 4 - 4 in round 2 and a new loser be selected randomly. I might be uninformed.
Håvard
… 27. nov. 2020 kl. 18:42 skrev Peter Grassberger ***@***.***>:
@hfossli-agens As Hollande lost round 1 now for every ballot with Hollande as "first votes" the "second votes" will become the new "first votes". In this case Merkel gets two extract "first votes". Did you expect it to remain a tie? It is the concept of IRV to still consider the preferences of ballots that didn't get their first wish.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
The program wants each ballot to rank the candidates 1-n, with each position left-to-right corresponding to a candidate top-to-bottom, but this is not clear. When I first used the program, I thought it wanted most-desired to least-desired, left to right, with the number corresponding to the candidate, rather than the position. In this way a partial ballot would simply leave off candidates from the end of their list.
Without a GUI, the instructions need to be very clear.
The text was updated successfully, but these errors were encountered: