[mink]

Hi,

since BBO Indi tourneys existed, at least in unclocked tourneys it could happen that I have the same opp more than once. However, I never experienced that I had the same partner twice, until it recently happened. In the 8-board-indy I played today it happened even twice. In one of the 2 cases even one of the opps stayed the same, so that the table was changed only in one seat. I cannot imagine that this behavior is necessary in a tourney with 152 participants. However, no big deal of course.

Karl

[barmar]

As explained in this post, in an unclocked indy the movement is totally random. And a proper random sequence sometimes has repeats -- if it didn't, it wouldn't be random (e.g. if you flip a coin 100 times, I'd be very suspicious if there weren't some runs of 4 or 5 heads in there).

In a clocked indy we use a more complicated algorithm that shouldn't allow you to have the same partner twice in a row.

[mink]

Sorry I missed the other post on this subject. However, "Totally Random" is not enough to characterize the non-clocked movement. It would be interesting what triggers the software to start moving players to new tables of a new round. Is it done say once each minute? Or does the software wait until a minimum number of tables has finished the previous round? Or a combination of both? If it is possible by the current algorithm that only 8 players a randomly reseated at 2 tables, I would suggest to increase this minimum number of tables in order to allow more randomness to happen. Maybe a good idea would be to set the minimum_number_of_tables_to_be_moved to some fraction of the total_number_of_tables.

Karl