[gnugo-devel] experimental code

[Evan Berggren Daniel]

OK, so it looks to me like fixing owl inconsistencies requires a far
greater understanding of the codebase than I have.  I'm happy to continue
work on matcher_check (does it need a new name now?) if that is desired;
would people have a use for replaying of sgf files or do we have the info
needed?

Aside from that, I went looking at archived discussions of
--experimental-connections, --experimental-semeai, etc.  It looks to me
like the general consensus is that this code should be turned on by
default, since it appears to improve things and we want bug reports, but
that it is too slow.  So, I propose to make a level 11 of play that turns
these on, but is otherwise equivalent to the current level 10 (I seem to
recall that GNU Go currently gets weaker beyond 10?).  We could then make
level 11 the default, but play online with level 10, or perhaps do
something to check the time constraints.

Does this sound like something that would be useful?  If not, does someone
have something to suggest instead?  currently I feel that my knowledge of
Go is too limited to help much outside the code, and that my understanding
of the code is too limited for more complex things.  There's only so much
I can pick up by just reading code.

Thanks

Evan Daniel