Re: [gnugo-devel] Patch for break_chain3_moves

[SP Lee]

> The following tweak makes gnugo generate more aggressive chain
breaking
> moves. The regression breakage (I might overlook some cases because
> there are recently lots of regression changes on the cvs):
>
> ./regress.sh . reading.tst
> 194 unexpected PASS!
> ./regress.sh . strategy.tst
> 13 unexpected PASS!
> ./regress.sh . lazarus.tst
> 5 unexpected PASS!
> 13 unexpected PASS!
> ./regress.sh . nngs.tst
> 370 unexpected PASS!
> 371 unexpected PASS!
> ./regress.sh . strategy3.tst
> 119 unexpected PASS!
> ./regress.sh . owl1.tst
> 263 unexpected PASS!
> ./regress.sh . century2002.tst
> 140 unexpected PASS!
> ./regress.sh . 9x9.tst
> 210 unexpected PASS!
>
> ./regress.sh . reading.tst
> 64 unexpected FAIL: Correct '3 N1', got '1 R3'
> ./regress.sh . arb.tst
> 203 unexpected FAIL: Correct 'T7', got 'N3'
> ./regress.sh . seki.tst
> 206 unexpected FAIL: Correct 'A1', got 'C9'
> 811 unexpected FAIL: Correct 'A1', got 'C9'
>
> These fails are all related to ko. Since now more moves are generated,
> the ko's may make things more complicated. I'll check this later.
>
> ./regress.sh . 13x13.tst
> 39 unexpected FAIL: Correct 'H4|J4', got 'J5'
>
> Actually I think J5 is not a bad move for this case.
>
> ./regress.sh . strategy4.tst
> 190 unexpected FAIL: Correct 'D13', got 'E14'
>
> D13 is better for sure, but E14 maybe also not bad, yet E14 generates
> many aji's.
>
> SP Lee
>

After further analysis, the fails of seki:206 and seki:811 are not due
to this patch, because there is no break_chain3 move generated at all.
For arb:203, the increased node count may contribute to the failure.

SP Lee