Perhaps the best thing to do is to cancel the 19x19 and schedule it again later?
regards, David > -----Original Message----- > From: [email protected] [mailto:computer-go- > [email protected]] On Behalf Of David Fotland > Sent: Saturday, June 30, 2012 6:15 PM > To: [email protected]; [email protected] > Subject: Re: [Computer-go] TCGA 19x19 Computer Go Tournament, error > report > > It looks like in rounds 10-15 every match timed out, which put the > tournament back on schedule. These matches should not be counted in > the official totals. > > David > > > -----Original Message----- > > From: [email protected] [mailto:computer-go- > > [email protected]] On Behalf Of Nick Wedd > > Sent: Saturday, June 30, 2012 4:19 PM > > To: [email protected] > > Subject: [Computer-go] TCGA 19x19 Computer Go Tournament, error > report > > > > This report is about incidents in the ongoing TCGA 19x19 Computer Go > > Tournament, now running on KGS. I am writing this for the record, so > > that the players and organisers will be aware of all the information > > that I have. > > > > These statements are made for the record. I hope I can be regarded > as > > impartial. I am only making statements of fact anyway. > > > > __Incident 1. > > > > During round 2, I removed 'ntnu' from the tournament, at the request > > of its operator. > > > > I hoped that this would reduce the length of the tournament from 36 > > rounds to a more manageable 30, which would allow it to end before > the > > start of the July KGS tournament. > > However, it seems that that is not how the scheduler for a multiple- > > round-robin works. Round 10, with eight players, has three games and > > two byes, rather than the four games that one might expect. I assume > > that the entire schedule was drawn up in advance, and one of the two > > "byes" was scheduled as a game against the now-absent 'ntnu'. > > > > I do not know how to avoid a clash with the schedule of the KGS July > > bot tournament. I am now too tired to think sensibly about it, and > > will go to bed soon. I will leave 'guxxan' to think about it. > > > > > > __Incident 2. > > > > During round 3, 'ajahuang' saw that Fuego19, which he was operating, > > had a hopeless position against nomitan440, and proposed logging in > > and resigning for it. If I had been more alert, I would have > realised > > what was likely to happen, and told him not to; but I said nothing. > > > > He logged in to Fuego19's account, and resigned for it. The KGS > > tournament system observed a human using a bot's account in a bot > > tournament, regarded this as an attempt to cheat, and marked the game > > as lost by "Forfeit". Thus this round 2 game has two different > > results: KGS sees it as lost by Fuego19 by resignation, while the > KGS > > tournament system sees it as lost by Fuego19 by Forfeit. > > > > There is no significant problem so far, this outcome was what I had > > expected. > > > > However, the tournament was running behind the optimistic > > 25-minutes-a- round specified when it was set up. So when this round > > 2 game ended (all the other round 2 games had already ended), round 3 > > began immediately. And ajahuang was still logged in to Fuego19's > account. > > So Fuego19's round 3 game (against AyaMC5) was also treated, by the > > tournament system, as lost by Fuego19, by Forfeit. But the game > > continued to be played. > > > > When the other round 3 games were finished, round 4 started (the > > tournament system regarding the Fuego19/AyaMC5 game as already > > decided). I realised that Fuego19 and AyaMC we still playing in > their > > round 3 game and had not joined their round > > 4 games, so, to free them up and let them play in round 4, I used my > > admin power to "kill" this game. I believe that > > Fuego19 had been winning it at the time. I killed it rather too > > slowly, so that when AyaMC5 joined its round 4 game against Zen19S, > it > > has already lost one of its 15-second overtime periods. I apologise > > to AyaMC5's operator for this. > > Fuego19 did not suffer loss of an overtime period, as it had a bye in > > round 4. > > > > Nick > > -- > > Nick Wedd > > [email protected] > > > > _______________________________________________ > > Computer-go mailing list > > [email protected] > > http://dvandva.org/cgi-bin/mailman/listinfo/computer-go > > _______________________________________________ > Computer-go mailing list > [email protected] > http://dvandva.org/cgi-bin/mailman/listinfo/computer-go _______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
