We have encountered this consistently in our non-MC/UCT program.
Things that "fix an obvious problem" lead to unintended consequences
that sometimes take weeks to tease apart. So far we have been able to
understand how this comes about in each situation, but still have
little ability to predict in advance when the fix will simply work
(and thus improve play) and when it will lead to the unintended
consequences that result in worse play.
Cheers,
David
On 5, Jul 2007, at 9:50 AM, David Silver wrote:
Often we try something that seems like it should improve the
quality of the simulation player, but it makes the overall
performance worse. It is frustrating and surprising! Has anyone
else encountered this?
_______________________________________________
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
