POTY 2019 Voting

[Pavgran]

#01 ***
#02 **
#05 **
#06 **
#07 *
#08 ***
#10 **
#12 *
#16 ***
#19 **
#20 **
#21 ***
#22 **
#23 **
#26 *

[Macbi]

#01 ***
#02 **
#03 *
#05 ***
#06 *
#07 **
#08 ***
#13 *
#17 *
#18 *
#19 *
#21 ***
#22 *
#23 *
#25 *
#26 **

[Huzhanshao]

#01 ***
#02 **
#03 **
#04 **
#05 **
#06 ***
#07 *
#08 ***
#09 **
#10 ***
#11 *
#12 *
#13 **
#14 *
#15 *
#16 ***
#17 **
#18 **
#19 **
#20 **
#21 ***
#22 *
#23 ***
#24 ***
#25 **
#26 **
#27 *

[yujh]

#01**
#02***
#03**
#04**
#05**
#06**
#07**
#08***
#09**
#10**
#11**
#12***
#13**
#14**
#15**
#16***
#17**
#18**
#19***
#20**
#21**
#22***
#23***
#24**
#25***
#26***
#27***

(My kindness made me give at least 2)

[simsim314]

and not like any other format that doesn't consist of pound signs at the very beginning of each vote line in the message, followed immediately by two digits matching a numbered item from the list below, followed by a space, followed by one or two or three asterisks.

Hello Ian. I think the vote is belonging to the community. That means that your script should support the "common" community way of expressing their preferences rather than obviously ignoring some votes because your script will ignore anything not satisfying the format. Even if my attention span is large enough to change my vote, you can see several other community members that voted in similar fashion. Expecting everyone to express opinion on everything and then formatting it correctly for script to capture is not a valid expectation of this community. I would count by hand myself or write a better script rather than trying to enforce my format over everyone in the community, which as you can see yourself is not reasonable expectation of 50% of the members.

[Hunting]

and not like any other format that doesn't consist of pound signs at the very beginning of each vote line in the message, followed immediately by two digits matching a numbered item from the list below, followed by a space, followed by one or two or three asterisks.

Hello Ian. I think the vote is belonging to the community. That means that your script should support the "common" community way of expressing their preferences rather than obviously ignoring some votes because your script will ignore anything not satisfying the format. Even if my attention span is large enough to change my vote, you can see several other community members that voted in similar fashion. Expecting everyone to express opinion on everything and then formatting it correctly for script to capture is not a valid expectation of this community. I would count by hand myself or write a better script rather than trying to enforce my format over everyone in the community, which as you can see yourself is not reasonable expectation of 50% of the members.

Following a certain format is the rule. For example, you can't post a pattern by using 0 and 1 and@rowett and say there is a bug in LifeViewer.

[simsim314]

Following a certain format is the rule.

Who decides the "rule"? I can write a script in different way and if Ian will open the script, I'm capable of adding another rule. Can you as a person understand my preferences? If the answer is yes, adapt the script to fit the member preferred way of expressing themselves rather than enforce your rules. If you can't manage this type of parsing, the community should prefer the script that can (or even old fashion by hand counting).

[Hunting]

Following a certain format is the rule.

Who decides the "rule"? I can write a script in different way and if Ian will open the script, I'm capable of adding another rule. Can you as a person understand my preferences? If the answer is yes, adapt the script to fit the member preferred way of expressing themselves rather than enforce your rules. If you can't manage this type of parsing, the community should prefer the script that can.

The rule is in the first page by testitem, TWO DIGITS.

As a person, you can understand

Code: Select all

010
111
001

But does that means LifeViewer has to support that?

[simsim314]

I still don't see the similarity. We're talking about modifying 100 lines of script with 2 lines of code. If we're perceiving it as community expression of voting of the year, please let me personally add the option to count without spacing. The voting belongs to the community, not to the script owners. BTW LifeViwer and Golly both open source, and if I want it to support another format nothing is stopping me. If Ian wants help with the script to support more formats I would be glad to help.

[simsim314]

Really it would be easy enough to fix the script to handle simsim314's variation of the vote format.

Hey I look at a script you posted and on line 43 the while loop without spacing will work. Don't see why you think it needs spacing? The script as it's now looks fine for my format as well.

[dvgrn]

Hey I look at a script you posted and on line 43 the while loop without spacing will work. Don't see why you think it needs spacing? The script as it's now looks fine for my format as well.

It used to require a space. I adjusted it to allow your variant of the format a week or two ago. The version with the space is still preferable, just for readability, and because that’s what the first post asked for.

The reason that I (not Ian07, he was just quoting the first post) tried to define a very clear and specific voting format from the start, is that in past years people have used all kinds of non-script-compatible ways of casting their votes, from muzik’s “prose style”, to putting votes in a BBCode list, to using random Unicode bullet characters instead of #s. There’s no hope of writing a script that can correctly count every possible silly vote format, and trying to support too many variants will just make the script buggy and unreliable, and therefore not worth using.

I still like having the script, and it seems perfectly reasonable for people to use an established format if they want their vote to be counted. However, an important point is that the script is not the only vote-counter. One or more people will no doubt do a hand count of the votes. If past years are any guide, the hand counts may all disagree with each other — it’s a tough job to count everything perfectly by hand. So the script comes in really handy as a double-check and corroboration of the hand count... but only if voters can be persuaded not to invent too many new formats in a given year.

One of these years the hand count(s) will agree with the script count right away, and we’ll get to avoid all the triple-checking and review. Maybe this will be the year! Everyone seems to have come pretty close to following the format so far.

[simsim314]

@dvgrn I would suggest to post the script on GitHub and anyone has two options:

1. Comply with the existing format.
2. Use their own format after updating the script themselves.

Thus we will allow more formats and less work for you.

[dvgrn]

@dvgrn I would suggest to post the script on GitHub and anyone has two options:

1. Comply with the existing format.
2. Use their own format after updating the script themselves.

Thus we will allow more formats and less work for you.

I think I'm going to politely decline to do any more work on this at all. The current script will be run in four days, and then the Great Vote Format Problem will stop being of interest to anyone at all for another year.

It strikes me as wildly unlikely that anyone would take the trouble to change the script and submit a pull request to support additional vote formats. If that happened, who would code-review it to make sure it doesn't introduce new bugs that might cause false-positive vote counts? It's much easier to simply read the instructions in the first post and follow the existing widely-accepted format, so I bet everyone will do that.

Of course, anyone is perfectly welcome to grab the publicly-posted script, put it on GitHub themselves, make it support Chaucerian East Midlands Middle English prose votes or whatever, and then take over running the script from now on. However, I have a long list of Life-related projects that I would respectfully suggest would be higher priority and more interesting than this one.

[Naszvadi]

...

Shall I correct my votes' indexing?

[dvgrn]

Shall I correct my votes' indexing?

No need if you don't want to. The script doesn't care about leading zeroes, it just converts any string of digits into a number and records the vote against that number.

[mscibing]

#01 **
#03 **
#07 ***
#08 **
#10 **
#11 *
#16 **
#19 **
#20 *
#21 ***
#23 **
#24 **
#25 **

[wildmyron]

#01 *
#02 **
#04 *
#05 **
#06 *
#07 **
#08 ***
#09 *
#10 **
#12 **
#13 *
#16 *
#17 *
#20 *
#21 ***
#22 *
#23 **
#24 *
#26 *
#27 *

[dvgrn]

Okay, here in North America it's still March 15th, the arbitrary date that I edited in to the first post as a closing day for voting.

Anyone else want to get a vote in before it's no longer March 15th anywhere in the world?

[Nathaniel]

I like to live dangerously and push deadlines.

#01 *
#04 **
#06 *
#08 ***
#12 *
#15 *
#17 **
#20 *
#22 *
#26 *
#27 *

[Goldtiger997]

#01 *
#02 ***
#04 **
#05 **
#06 *
#07 **
#08 ***
#09 *
#10 **
#11 *
#13 *
#16 *
#17 *
#18 *
#19 **
#20 *
#21 ***
#23 **
#24 **
#25 *
#26 *
#27 *

[Saka]

Just in time?
#02 *
#03 *
#04 **
#06 ***
#07 **
#08 ***
#09 *
#11 **
#12 *
#13 *
#15 *
#17 **
#18 **
#19 **
#21 **
#22 *
#24 *
#25 **
#26 **

[dvgrn]

Just in time?

You were way ahead of the deadline -- it's still March 15th in American Samoa (but not in Samoa) for another hour and change.

I suspect the last vote has come in now, so I've spent the two minutes to run the script, with the raw results quoted below. These translate to

 1st: 74 votes, #08 David Hilbert
 2nd: 66 votes, #21 Spider synthesis
 3rd: 53 votes, #06 Scholar
 4th: 48 votes, #07 46P4H1V0 synthesis and gun
 4th: 48 votes, #02 Cheap still life syntheses
 5th: 45 votes, #19 Knightwave stabilization
 5th: 45 votes, #10 Remini
 6th: 41 votes, #17 Dueling banjos and gun
 7th: 39 votes, #05 Slavic
 8th: 37 votes, #24 27P4H1V1 synthesis and gun
 8th: 37 votes, #23 Stable glider-to-spaceship converters
 9th: 36 votes, #04 66P13 and variations
10th: 35 votes, #18 p49 skewed pulsar hassler
11th: 34 votes, #22 Phoenix agars
11th: 34 votes, #16 60-line c/10 printer
12th: 33 votes, #20 R49
12th: 33, #12 New gun designs
12th: 33 votes, #01 Systematic survey of small patterns
13th: 32 votes, #26 99 bottles of beer on the wall
13th: 32 votes, #25 Spaghetti monster eater and Heisenburp
14th: 29 votes, #15 47575M and relatives
15th: 27 votes, #13 Mountain range patterns
16th: 26 votes, #27 New mid-period sparkers
16th: 26 votes, #03 Stably supported cyclotron gun
17th: 25 votes, #11 230P8
18th: 23 votes, #09 p250 c/10 orthogonal rake
19th: 19 votes, #14 Hackersaw

Links to all these can be found in the first post in this thread. Somebody should double-check all this -- it would be rare and wonderful if I haven't managed to let some kind of error creep in somehow.

Many thanks to all who participated in the voting, and/or in the complex logistical negotiations leading up to it. I hope we'll have just as much fun discussing voting methods and formatting in 2021 when we tackle POTY 2020... or even in a month or three, if someone wants to get the Pattern of the Decade voting thread in motion now!

Code: Select all

074, #08, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3
066, #21, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 2, 3, 3, 3, 2
053, #06, 2, 2, 3, 2, 3, 2, 3, 3, 2, 3, 2, 3, 3, 2, 2, 2, 2, 1, 3, 2, 1, 1, 1, 3
048, #07, 2, 2, 3, 1, 3, 2, 2, 2, 1, 3, 2, 3, 3, 2, 2, 1, 2, 1, 2, 3, 2, 2, 2
048, #02, 3, 3, 2, 2, 3, 3, 2, 1, 2, 3, 3, 2, 2, 2, 2, 2, 2, 3, 2, 3, 1
045, #19, 3, 2, 2, 2, 2, 2, 3, 1, 1, 3, 1, 1, 2, 2, 1, 3, 2, 1, 2, 3, 2, 2, 2
045, #10, 2, 1, 1, 2, 2, 2, 2, 3, 3, 3, 2, 2, 1, 3, 3, 2, 3, 2, 2, 2, 2
041, #17, 2, 1, 3, 2, 2, 2, 3, 3, 1, 2, 1, 3, 1, 2, 2, 1, 2, 2, 1, 2, 1, 2
039, #05, 2, 1, 2, 2, 2, 1, 1, 1, 2, 2, 2, 2, 1, 1, 1, 3, 2, 3, 2, 2, 2, 2
037, #24, 3, 1, 3, 1, 3, 2, 2, 1, 1, 1, 1, 3, 2, 2, 3, 2, 2, 1, 2, 1
037, #23, 3, 2, 2, 2, 3, 1, 1, 2, 1, 3, 2, 2, 1, 3, 3, 2, 2, 2
036, #04, 3, 3, 1, 2, 2, 2, 1, 1, 2, 1, 1, 3, 1, 2, 2, 2, 1, 2, 2, 2
035, #18, 2, 1, 3, 1, 2, 2, 2, 2, 2, 2, 1, 2, 1, 2, 2, 1, 2, 2, 1, 2
034, #22, 3, 1, 1, 3, 2, 2, 2, 2, 2, 1, 1, 2, 2, 2, 1, 1, 3, 1, 1, 1
034, #16, 3, 2, 2, 1, 3, 3, 2, 2, 1, 1, 1, 3, 3, 3, 2, 1, 1
033, #20, 2, 3, 1, 1, 2, 3, 1, 2, 2, 2, 2, 2, 2, 2, 2, 1, 1, 1, 1
033, #12, 2, 1, 3, 2, 2, 2, 2, 1, 2, 1, 1, 3, 2, 1, 1, 3, 2, 1, 1
033, #01, 2, 1, 1, 1, 2, 1, 1, 1, 1, 1, 2, 2, 1, 3, 3, 3, 2, 2, 1, 1, 1
032, #26, 3, 2, 2, 1, 1, 3, 2, 1, 1, 1, 2, 1, 2, 2, 3, 1, 1, 1, 2
032, #25, 2, 3, 1, 2, 2, 1, 1, 2, 1, 1, 3, 2, 1, 2, 3, 2, 1, 2
029, #15, 2, 2, 3, 1, 1, 2, 2, 2, 1, 1, 1, 1, 2, 1, 2, 1, 2, 1, 1
027, #13, 2, 2, 2, 2, 1, 2, 1, 1, 1, 3, 2, 1, 2, 2, 1, 1, 1
026, #27, 2, 2, 1, 1, 2, 3, 1, 1, 1, 1, 2, 2, 1, 3, 1, 1, 1
026, #03, 1, 3, 1, 1, 2, 1, 1, 1, 1, 2, 1, 2, 1, 1, 2, 2, 2, 1
025, #11, 1, 2, 1, 1, 2, 2, 1, 1, 1, 1, 2, 1, 2, 1, 2, 1, 1, 2
023, #09, 1, 2, 2, 1, 2, 1, 1, 1, 1, 1, 1, 2, 2, 2, 1, 1, 1
019, #14, 1, 1, 3, 1, 1, 1, 1, 1, 1, 1, 3, 1, 1, 2

Might as well include the whole script with the HTML from the two pages of this thread, also:

POTY2019-vote-count.zip

Python script used to count POTY2019 votes

(34.92 KiB) Downloaded 217 times

[Hunting]

Too bad that almost everyone skips Hackersaw.