[Computer-go] Are 4 'easy to avoid errors' common to all MC programs?

[Stefan Kaitschick]

> My experiments were are 9x9 too.
>
> I believe what was happening with my implementations of this is that 
> it worked well most of the time,  but not when it really mattered.   
>  When it didn't work,  it was turning a simple win into a struggle and 
> sometimes a loss.
>
> Don

Why would a simple win be lost? Within competitive winrate bounds, there 
shouldn't even be dynamic komi.
Only positions where the program thinks that one side should almost 
resign should be affected.
Does that mean that positions were lost because the program burdend 
itself with a negative komi in a high winrate position and played 
needlessly adventurous moves?
If that is the case, dyn. komi should not be used as a fix for the "win 
by 0.5" syndrome, but only in the opening and middle game.
To fix the 0.5 mess, maybe the score could be slightly incorporated into 
the evaluation function when positions are stable. (When the playouts 
come back with few total win/total loss results)

Stefan