[Willem]

Hi all,

I understand (but please correct me when I am wrong) that in unclocked mode pairs who finish first will meet each other in the next round (and therefore might play each other several times in one tournament).
But I wonder how movements are made in clocked mode. Is it done randomly, by results (like Swiss), or any other way?
Is it possible for the host to influence the pairing?
The reason I am asking this is I want to organize a competition which consists of several tournaments, and I like each pair to meet the other contestants about the same number of times.

Thanks, Willem

[uday]

Unclocked:
When a table finishes, it waits for another table. When another is available, the pairs are matched up. Problems occur when 2 tables are faster or slower than the others

Clocked:
Field is split into sections of no more than 15 tables (if additional tables are needed they are added to section1, then section 2, etc).
Within a section, NS is stationary. EW moves "up" each round (going back to the start of the section as needed).


In the next server release ( not sure when i will release, i am dithering) the unclocked should be much better. If the field is large, the server will wait for up to 6 or more tables to complete. I have an alternative movement ready as well, in which a table that is completeis only paired up with another waiting table if the combination produces no playbacks.


Finally, the next client will allow the host to specify a Swiss movement (but this, of course, will allow playbacks).


I do not think the server can support what you are suggesting, even with the new version. Each tourney is independent of any other, and there is currently no capability for multi-session support.

[Gerardo]

Quote

Finally, the next client will allow the host to specify a Swiss movement (but this, of course, will allow playbacks).

That's against the definition of Swiss I have :- (chess background, so you have to take color alternating/balancing into account, that's more important than pair similar ranked players, but paramount is no playblacks [Last round can be difficult, particularly if even number of rounds]

In fact, when you get a playback [or a color problem], a backtrack is necessary to take another choice of pairings which has no issues.

Of course, no playbacks can only be implemented in clocked tourneys, as in unclocked you'll always have an incomplete choice of pairings available at any point.

I think you meant "pair similar ranked (players/pairs/teams [not yet ])", sorry for being picky

Quote

I do not think the server can support what you are suggesting, even with the new version. Each tourney is independent of any other, and there is currently no capability for multi-session support.

Not sure for tourneys, but maybe for matches can be handy, with competitions currently running with two sessions format, to link one match with a previous one, provided:
1) Match still available in list [for now]
2) Teams names are repeated exactly

Then info about 1st session result is made available in tourney description.

OTOH, that's just a bit of sugar, just low priority thing.

[uday]

"
In fact, when you get a playback [or a color problem], a backtrack is necessary to take another choice of pairings which has no issues.
"

Is this true? In other words, must a "swiss" movement reject plabacks, or are they considered legit?

[mycroft]

All swiss movements that I know of in bridge are "no playback" movements. I have seen the odd one that specifically says "there may be a repeat in the last round", but that would be an exception.

Now, of course, I am going to be proved wrong, somewhere "Swiss" pairing is "1-2, 3-4, 5-6,..., irrespective of previous plays". But at least in the ACBL, this is a no-go anywhere.

Michael.

[uday]

Bah

I will probably change it - but first i will release as is [ with playbacks, but more "head to head"] , to make sure the rest of the code works , unless i hear a lot of squawking.

My plan is to release a new server first anyway - the rest of you wont be able to create these tourneys until 3.5.2 of the client is released - and this wont happen for a couple of weeks, at least ( we're off to the nationals this week ).

We'll sort this out before we release 3.5.2 - we will have a chance to see how the swiss works this way and collect some feedback