Re: [gnugo-devel] Interference of break-in code with territoryestimation

[SP LEE]

> > Move generation values Q2 to 11.20
> >
> > Then I found the "erasing territory" comes from the break-in code. I
suppose this "erasing" work may result in not seeing the captured stones
in the function influence_delta_territory, so that the estimated
territorial value is too low. This would have a great impact on the move
valuation and I think the break in code needs to be checked on this
point.
> >
>
> The break-in code is allowed to overrule owl decisions. In this case,
it sees
> that from the alive stone R3, black can connect to the stones at N2
(by
> playing at Q3 or Q1). Hence these stones cannot logically be
considered
> captured by white.
>
> The only problem is that breakin.c isn't aware of ko results yet,
which it
> would need to be to correctly evaluate the position above. But it
definitely
> undestands the position better than the owl code.
>
> Arend
>
>

I don't have objection that break-in code can overrule owl decision. The
problem here is that the final score of 11.20 of Q2 is smaller than the
actual value. I had modified some pattern so that one of the position on
the board got slightly higher value than 11.20, which let gnugo forget
Q2. However, without break-in code, Q2 is valued as 21 point.

SP Lee