Reply to thread

Message

<blockquote data-quote="Conaill" data-source="post: 2062260" data-attributes="member: 1264">Wrapping up a few open questions from the sidelines <img src="https://cdn.jsdelivr.net/joypixels/assets/8.0/png/unicode/64/1f609.png" class="smilie smilie--emoji" loading="lazy" width="64" height="64" alt=";)" title="Wink&nbsp; &nbsp; ;)"&nbsp; data-smilie="2"data-shortname=";)" />Pretty much all these methods can easily be adapted to find a second place winner as well. There are two basic approaches:1) Just pick the candidate that does second best on whatever your method is measuring. In IRV, this could be the second candidate remaining after you've eliminated all but two, or the second-highest votes when the winner gets 50% (not necessarily the same). In Approval Voting, it would simply be the one getting the second most votes.2) Rerun the system to see who would win if the 1st-place winner wasn't in the race. In IRV, this could produce yet another 2nd-place winner than in the approach described above. In Approval Voting, both approaches will give the same result.As Michael already stated - if we can dream it up, he can program it.IRV would require a bit of careful scripting for the interface - need to make sure each product is ranked only once, and each rank is used only once. Implementing, testing and debugging the IRV algorithm itself shouldn't take more than a few hours. Approval Voting can probably be written and tested in under half an hour - interface and all.That is very similar in flavor to the system used last year, except with a ranked vote instead of a 1-10 score.Problem is that in the absence of &quot;don't know&quot; votes, this is actually equivalent to Borda Count, with all the drawbacks that come with that. Good try though!</blockquote>

[QUOTE="Conaill, post: 2062260, member: 1264"] Wrapping up a few open questions from the sidelines ;) Pretty much all these methods can easily be adapted to find a second place winner as well. There are two basic approaches: 1) Just pick the candidate that does second best on whatever your method is measuring. In IRV, this could be the second candidate remaining after you've eliminated all but two, or the second-highest votes when the winner gets 50% (not necessarily the same). In Approval Voting, it would simply be the one getting the second most votes. 2) Rerun the system to see who would win if the 1st-place winner wasn't in the race. In IRV, this could produce yet another 2nd-place winner than in the approach described above. In Approval Voting, both approaches will give the same result. As Michael already stated - if we can dream it up, he can program it. IRV would require a bit of careful scripting for the interface - need to make sure each product is ranked only once, and each rank is used only once. Implementing, testing and debugging the IRV algorithm itself shouldn't take more than a few hours. Approval Voting can probably be written and tested in under half an hour - interface and all. That is very similar in flavor to the system used last year, except with a ranked vote instead of a 1-10 score. Problem is that in the absence of "don't know" votes, this is actually equivalent to Borda Count, with all the drawbacks that come with that. Good try though! [/QUOTE]

Verification