Star Voter Season 6
|
| 1 person marked this as a favorite. |
Me and my husband have discovered some odd occurrences of having the same exact item pairs to vote on on more than one occasion and have successfully found the cause.
When we both click submit on an item at the same time, most of the time we get the same exact pair delivered to us, 90% of the time in the same order on both computers, left side/right side matches, and only occasionally the same pair but reversed sides.
It is easy to setup, and we wanted to let someone know, in case this is not desirable voting mechanics.
Even if we start with 2 different items, simply clicking one them at the same time generates a like pair for both of us. Now this could be simply as we are on the same IP (router) or something but I figured I'd report it.
Yeah, makes sense.
The pairings can't be totally random or else the chance that a mediocre item will end up to 32 because it mostly got paired against bad items would be too high.
So I guess the pairings are determined by an algorithm (items rank and level of uncertanty) and thus each voter gets the same pairings at the same time.
It makes a LOT of sense. If the two of you reach into the pool of available items at the same time, the same items will come out as currently needing a vote, since that specific pairing won't be marked as voted on until you actually vote on it.
Not a terrible thing, since you are two different people voting using two different accounts, and it is doing what's intended. I don't even think there's anything to fix in this circumstance.
| 1 person marked this as a favorite. |
I think what they may be worried about is...
you are supposed to get each item pair in the pool voted on before cycling a new pool to ensure each item/pair has the same number of appearances during the voting period.
So with a non time locked pairing like this, it could indicate some items are getting more appearances than they should - in the example given two items appeared twice from the same cycle of pool. Therefore one of those items could score 2 votes to other items in the pool potentially only scoring 1.
This is the fear and I think it is good to raise it so that the techie guys can say something like "it's not a huge problem, when we create the next cycle, if items have more appearances than they should have had, they skip a cycle to bring back in line" or something like that.
| 1 person marked this as a favorite. |
We're aware of this: We wish it weren't the case, but avoiding it would dramatically increase the amount of time it would take to fetch a voting pair, which would impair the entire site's performance.
If you vote a little more out-of-sync, you should get different pairs of items.
I think what they may be worried about is...
you are supposed to get each item pair in the pool voted on before cycling a new pool to ensure each item/pair has the same number of appearances during the voting period.
So with a non time locked pairing like this, it could indicate some items are getting more appearances than they should - in the example given two items appeared twice from the same cycle of pool. Therefore one of those items could score 2 votes to other items in the pool potentially only scoring 1.
Oh, I get it. But it will be self-correcting. Think of it as the two items getting their N+1 vote slightly early. In the overall scheme of things, it won't really matter, since in the long run they'll get the correct number of votes.