> From: Richard Brown <[EMAIL PROTECTED]>
>
> "The enemy's key point is my own" is often invoked, for example, as a
> reason to occupy the central point of a _nakade_ shape, or to play a
> double sente point, or to make an extension that would also be an
> extension for the opponent.
<snippage>
> Not only is the enemy's key point my own, but if I know _a_priori_ what
> sorts of behavior in which my _specific_ enemy is likely to indulge,
> perhaps I may be able to play, sometimes anyway, on the very points
> where he or she (or it) is likely to play!
>
> The hypothesis outlined above, as of yet, has neither been confirmed
> nor falsified by experimentation, but it kinda gives a whole new
> meaning to the proverb, don't it?
Sluggo has ( or had ) a particularly nasty form of "the enemy's key point is my
own" - the program actually ran the GnuGo engine, so Sluggo knew precisely
where GnuGo was most likely to play, and ( using a large cluster ) could give
GnuGo a five stone handicap and win "convincingly and consistently", according
to David Doshay, the author of Sluggo - google "sluggo gnugo evil twin" for
more information.
The downside of overfitting to a particular opponent is that little improvement
versus other opponents was seen.
I always wondered if it would be useful to exploit certain information which
GnuGo knows how to calculate, but does not actually use in play - I suspect
that life-and-death and semeai information which GnuGo knows how to discover
may not actually be used, in some cases.
_______________________________________________
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
