You only need to keep track of one point. If the last move was a single
stone capture, then that point is the Ko point for the next move. A play by
the opponent on that point is disallowed unless it's a capturing move.
Urban
On Thu, Mar 12, 2015 at 6:07 AM, Ray Tayek wrote:
> i need to implemen
Alvaro, Urban,
thanks!
I've got an additional question.
It may be obvious but it is written a bit ambiguous imho on
senseis.xmp.net:
"A player's score is the number of points of her color, plus the number
of empty points that reach only her color."
So an empty point that can reach the border of
Hi,
It looks like I got the tromp/taylor scoring working in my program.
I'm now looking for testcases.
Sofar I only found the ones at
http://codegolf.stackexchange.com/questions/6693/score-a-game-of-go
Do I suck at googling and are there more?
thanks in advance
Folkert van Heusden
--
A follow up question. What if the bot is running on a remote machine (say
an AWS EC2 instance) and I want to observe locally? Obviously I can't use
gogui-display anymore. Is that what gogui-server and gogui-client are for?
So I would run gogui-server SOMEOPTIONS "program" on the remote instance as
On 12.03.2015 06:07, Ray Tayek wrote:
i need to implement a simple ko rule.
Supposing you want a strategically simple AND complete ko ruleset, you
can choose from:
1) short cycle loss (2 or 3 successive plays, see below) + long cycle
tie ko rule
2) basic ko rule + fixed ko rule (recreatin
Hi,
i need to implement a simple ko rule.
I wrote simple pure-MC and UCT sample.
http://www.yss-aya.com/puremc20150313e.zip
put() function handles a simple ko.
Regards,
Hiroshi Yamashita
___
Computer-go mailing list
Computer-go@computer-go.org
http
