Skip to main content.
August 27th, 2005

Tired of ads? Then register an account or login

Final round of Stellenbosch 3rd Quarter Handicap

The draw for the 3rd round and the current standings for the Stellenbosch 3rd Quarter Handicap Tournament are available. On the first board we have Johannes vs Louis, Louis has been promoted 4 ranks since the start of the tournament, while Johannes has been promoted 2. Louis is therefore the favourite in this tournament, also the only one to have won two games thus far. If Johannes were to win the game (against 2 handicap stones too many) we will have a tie between the two to be resolved by SOSOS (sum of opponents’ sum of opponents’ scores), and an opportunity for Wim to snatch first place, if he wins his game, also by SOSOS (i.e. the “luck of the draw” would then play a big role).

Wim, the tournament’s 30k player, defeated Johannes in the previous round, and so entered the running for the top positions (and probably guaranteed himself a promotion, as he had two handicap stones too few according to the current ranks). His next game is against Hanno with the aid of 9H and 30 komi. Jaco and Rory have both been promoted one rank since the tournament’s start, but Jaco lost his first game against Daniel, and an unfortunate miscommunication resulted in a loss for both Rory and Daniel in the second round. This leaves first place out of the grasp of all but the top three.

Pairings are now calculated by a script that firstly minimizes the maximum handicap. If there is more than one option, it minimizes the sum of squared handicaps. (All of this happens within the constraint of as good a swiss pairing as possible – minimizing mismatches in scores).

Posted by Hugo in Tournaments

2 Comments »

This entry was posted on Saturday, August 27th, 2005 at 11:58 am and is filed under Tournaments. You can follow any responses to this entry through the comments RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

2 Responses to “Final round of Stellenbosch 3rd Quarter Handicap”

  1. Hugo says:

    The script is a simple little python script. The second round minimized the maximum handicap, which turns out to not be the lowest sum of squared handicaps (ssh) pairing. The following pairing would have resulted in a ssh of 215 instead of 219:

    Rory Beling(W) vs Hugo van der Merwe(B) with 6H
    Johannes van der Horst(W) vs Louis de Jager(B) with 3H
    Daniel Wium(W) vs David Richfield(B) with 1H
    Hanno Botha(W) vs Wim Conradie(B) with 9H+30komi
    Jaco Swanepoel(W) vs Christina Auret(B) with 5H

    I think this is a good pairing, and that we can run all future handicap tournaments with minimum ssh.

    Interesting to note is what would have happened if we had a winner for Daniel vs Rory (I’m glad we didn’t):

    If Rory won, ssh=771:
    Rory Beling(W) vs Louis de Jager(B) with 9H+60komi
    Hanno Botha(W) vs Wim Conradie(B) with 9H+30komi
    Daniel Wium(W) vs Hugo van der Merwe(B) with 9H+20komi
    Jaco Swanepoel(W) vs Johannes van der Horst(B) with 9H+70komi
    David Richfield(W) vs Christina Auret(B) with 5H

    If Daniel won, ssh=621:
    Daniel Wium(W) vs Louis de Jager(B) with 9H+110komi
    Hanno Botha(W) vs Wim Conradie(B) with 9H+30komi
    Jaco Swanepoel(W) vs Rory Beling(B) with 4H
    Hugo van der Merwe(W) vs Johannes van der Horst(B) with 6H
    David Richfield(W) vs Christina Auret(B) with 5H

    The ssh for the actual third round pairing is 315. Here’s to hoping we can have 12 or more players next quarter, maybe even an odd number, having a bye to work with will help reduce the ssh. 😉

  2. Hugo says:

    I was unaware of the fact that the official policy was to minimize the maximum handicap. The 3rd round pairing does minimize the maximum handicap as well, so it is not a problem. The script has been corrected to mimize maximum handicap for future tournaments. (First and foremost remains the requirement for an “ideal” swiss pairing. Sum of Squared Handicaps will be used to choose between pairings with the same maximum handicap.)

Leave a Reply

You must be logged in to post a comment.