Re: [gnugo-devel] Twogtp test replay result

[SP Lee]

Here is the replay result with gnugo 3.5.3 as white for the same game I
posted earlier.

Move 2 (white): GNU Go plays C4 (75.00) - Game move D16 (74.00)
Move 4 (white): GNU Go plays D4 (75.00) - Game move D3 (74.00)
Move 26 (white): GNU Go plays O16 (24.12) - Game move R14 (24.13)
Move 44 (white): GNU Go plays G3 (16.14) - Game move Q3 (3.57)
Move 50 (white): GNU Go plays S10 (14.43) - Game move M13 (12.14)
Move 52 (white): GNU Go plays R10 (10.28) - Game move K15 (8.26)
Move 54 (white): GNU Go plays M16 (14.49) - Game move M16 (14.49)
Move 72 (white): GNU Go plays J4 (17.97) - Game move L17 (16.78)
Move 80 (white): GNU Go plays C2 (47.71) - Game move H2
Move 86 (white): GNU Go plays F14 (8.29) - Game move D11 (7.81)
Move 94 (white): GNU Go plays F12 (6.95) - Game move F14 (6.94)
Move 100 (white): GNU Go plays D19 (7.31) - Game move E2
Move 124 (white): GNU Go plays J2 (9.70) - Game move M1 (9.51)
Move 130 (white): GNU Go plays Q18 (4.37) - Game move O13 (4.21)
Move 218 (white): GNU Go plays G18 (34.52) - Game move H18 (14.00)

Compared to the current cvs, gnugo 3.5.3 agreeed with gnugo 3.4 on move
38, 58, 96 and 138. The move 138 (life and death problem) is related to
owl tuning, I think. So the owl tuning after 3.5.3 should be checked for
the mistake of the current cvs on move 138. There is still a big mistake
on move 218. So maybe the semeai changes from 3.4 to 3.5.3 should be
checked.


SP Lee