Often one program resigns early. Usually the programs don't use all of their time, but more like 80% or 90% of it. If any traditional programs enter they will finish much earlier.
If you schedule rigid round start times, you have to allow for the worst case possible time for both programs, and some extra time to figure out the pairings between rounds. You will also need rigid times for meal breaks. Your 22 ronnd would probably take more like 44 hours to play, 10 hours for breaks (one hour for meals every four hours), and 4 hours for pairings, so 55-60 hours total. Free pairing should use about 1.5 hours per round, and you can let programs that are behind play though breaks, and you don't need any time to do pairings, so you can finish in about 33 hours. The other alternative to allow round robin would be to shorten the time per program from 60 minutes to 45 minutes. David > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:computer-go- > [EMAIL PROTECTED] On Behalf Of Peter Drake > Sent: Wednesday, June 04, 2008 9:14 PM > To: computer-go > Subject: Re: [computer-go] Tournament at US Go Congress > > On Jun 4, 2008, at 7:07 PM, David Doshay wrote: > > > I would like to strongly suggest that enough rounds be run that > > every program plays every other program twice, once as B and once > > as W. > > This seems like a good idea, but I have two concerns: > > 1) Can the KGS tournament system support this? Nick, Bill? > > 2) If we get, say, a dozen programs, each program will have to play > 22 games, right? That's conceivably 44 hours. > > I was at first mystified by David Fotland's comment that "A round > robin can get many more rounds in the same time." Are you pointing > out that, if programs resign, other rounds can begin? Do a lot of the > KGS monthly tournament games end in resignation with a lot of time > left on the clock? Monte Carlo players tend to use almost all of > their time. > > Perhaps I should say something like, "Time permitting, we will run a > double round-robin tournament." > > > As set, the schedule does not have breaks for meals, and I think > > that for the health and happiness of the programmers, such breaks > > would be a good idea. I know that 3 days in a row without a proper > > dinner break will be very hard on my stomach. > > For what it's worth, the current schedule has dinner from 5:30-7:00. > > Peter Drake > http://www.lclark.edu/~drake/ > > > _______________________________________________ > computer-go mailing list > [email protected] > http://www.computer-go.org/mailman/listinfo/computer-go/ _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
