I ended up using gnugo --score aftermath --capture-all-dead to determine
the final state of the board. Thanks to Petr for the suggestion! This
worked within a 1pt margin of error for probably 95% of the games, which
was good enough for my purposes.
-Justin
On 7/25/2015 8:57 PM, Rafael Sakurai wrote:
... I'm also new with computer Go, and I have the same doubt. ...
Hi Justin, I started to draft a Go API in Java, the goal is to create
an API with the main game logic and anyone can use with their own
visual interface ...
Please, let me know if
On Sun, Jul 26, 2015 at 12:22:57AM -0400, David Fotland wrote:
In general this is beyond the state of the art of the strongest go programs.
You can’t score without determining the status of every group (live, dead,
seki), and you may need to identify required interior defensive moves that
Hello everyone.
I'm also new with computer Go, and I have the same doubt. I read many
articles about computer Go, but few of them talk about score calculation
and determine the status from groups of stones.
Hi Justin, I started to draft a Go API in Java, the goal is to create an
API with the
In general this is beyond the state of the art of the strongest go programs.
You can’t score without determining the status of every group (live, dead,
seki), and you may need to identify required interior defensive moves that have
not been played.
David
From: Computer-go
