I'd like to say that the blunder moves in the tournament were caused by not hardware but my code (_ _). See my reply to Ingo for more.
Those blunder moves follow (some are not bad). Round1 (vs Nomitan): moves 100 (O3), 122 (N4), 140 (O14). Round3 (vs Pashi): moves 73 (B4), 109 (F6), 213 (G13) and 227 (T9). Round4 (vs Orego): move 149 (B3). Round7 (vs Nomitan): move 17 (J2). Round9 (vs CrazyStone): moves 146 (F1), 156 (F19) and 244 (S4). Round10 (vs CrazyStone): moves 31 (D15) and 227 (C1). Before round12, I found and fixed an error. Correction: In the third paragraph of Result section: the opponent of CrazyStone is not Zen19S but fuego19. On the first paragraph of Result section: The move 192 is not a bluder but the best move for Zen where the winrate was 21% already. After blunder moves O3, N4 and O14, winrate dropped from 68% to 56%, 56% to 56% and 54% to 16%, respectively. Clearly the first was recoverable, the second was not actually a bluder and the third was fatal where N5 could let W O5 group live (M7 and P4 miai). Hideki Nick Wedd: <[email protected]>: >Congratulations to CrazyStone, winner of the slow KGS bot tournament >with 12 wins from 12 games! The runners-up had eight wins each, so >it was a convincing win in this tournament with a particularly strong >set of entrants. > >My report is at http://www.weddslist.com/kgs/past/S13.1/index.html >I expect it contains at least as many errors as usual, so I will be >pleased if you point these out to me. > >Nick -- Hideki Kato <mailto:[email protected]> _______________________________________________ Computer-go mailing list [email protected] http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
