I”ve added a few brackets to the printable brackets page, including some for 64- and 128-team tourneys. I’ve also added guides in the notation from the last post identifying the structure for the brackets that were already there, and adopted a naming convention for new printable brackets whereby the name of the file itself is a variant of the notation.
The lowers for these big tournaments are provided mostly as a curiosity, as it’s uncommon for a double-elimination or consolation format to be used on a field so large. But there are, from time to time, practical uses for big brackets.
Continue reading “Big Brackets”
Tourneygeek has been quiet for a while, but that is not (or at least not mostly) because I’ve been idle. The new simulator is nearly ready to run, and there should soon be plenty of results to report. I hope these will include substantial progress on such matters as a coefficient of competitiveness, fairness (D), and new measures of efficiency based on modeling playing time.
In the meantime, I’ve been coding several basic tournament designs for the new simulator format. In the course of this, I’ve developed a shorthand way of describing lower brackets that is handy for showing how they are (or are not) shifted.
The idea is to show how the drops from the rounds in the bracket above are distributed among the rounds in the bracket receiving the drops.
Continue reading “A Notation for Bracket Structure”
I remember watching some television show, so many years ago that I cannot hope to remember the details or even the name of the show, that had one line of dialog that has stuck with me.
A man has gone to Las Vegas ready to become wealthy by using a secret betting system he’s devised. Things go badly. He’s broke and broken, and the casino has cut off his credit – it’s time for him to quit. He’s granted an interview with the casino manager, and complains that they’re kicking him out they’re afraid of him, because he’s got a system! Then comes the line I remember:
If we’d known you had a system, we’d have sent a car for you.
This post builds on yesterday’s post, Card Sense, by discussing gambling systems: the ones that will, indeed, get you kicked out of a casino, and the ones that may inspire them to send a car for you.
Continue reading “We’ll Send a Car for You”
People who are good at playing one game are often good at others. In particular, there seems to be a general ability, sometimes called “card sense”, that seems to enable a player who is good at one card game to excel at other card games.
Card games may have this distinctive skill because of the way that almost all card games, and very few other games, incorporate the element of chance.
Continue reading “Card Sense”
Today a small example of practical tournament administration.
The Indiana Challenge Cup is contested by three teams of six players from each of the three backgammon clubs in Indiana. The players are ranked, within the team, in order of their standing in the local club. They’re put into three pools, one with the first and second ranked players, another with the thirds and fourths, and the last with the fifths and sixths. A round robin is played within each pool (except that players from the same club don’t play each other), and the club championship is determined by the overall number of wins by the members of each club.
Last year, as it happened, the ICC suffered from one of the common maladies of round robin tournaments – the ambiguous result. At the end of the four rounds, the scores were 12-12-12, so that tiebreakers needed to be applied. One team was eliminated on the basis of the record of their first-ranked player, and the other two teams had a doubles playoff round.
My club hosts the tournament this year, and I’ve put some thought into the preparation.
Continue reading “A Little Round Robin”
Continuing with the discussion of the new tournament simulator that’s under construction, this time with the elements of the match model that relate to each individual iteration.
Continue reading “The Current Iteration”
There has been a hiatus on tourneygeek in the reporting of simulator results. That’s because I’m comprehensively rebuilding the program, trying to eliminate some of the shortcuts and assumptions that were embodied in earlier versions. This is going to take some time, as it involves my learning a new language – an object-oriented one.
This post will describe some of the basic structure and flow I’m developing for the new simulator.
Continue reading “Building a New Simulator”