Black is flagged for an illegal Ko at the end of game 738921 on CGOS. Black
played H1, which looks legal to me. Server bug?
Scanning through the log today, I found a similar situation in game 738998.
The setup is that two stones in the corner are captured by playing 1 stone.
Recapture of the
That sounds like a classic _positional_ super ko violation. Any board
repetition is a ko violation, regardless of the player to play.
Sent from my iPhone
On Apr 13, 2009, at 9:32 AM, Brian Sheppard sheppar...@aol.com
wrote:
Black is flagged for an illegal Ko at the end of game 738921 on
Brian Sheppard wrote:
Black is flagged for an illegal Ko at the end of game 738921 on
CGOS. Black played H1, which looks legal to me. Server bug?
Scanning through the log today, I found a similar situation in game
738998.
The setup is that two stones in the corner are captured by playing 1
What tricks are people doing to minimize the performance degradation due to multiple threads contending for access to the tree (in MCTS)? Do you only lock a
portion of the tree? How would that work?
___
computer-go mailing list
Michael Williams wrote:
What tricks are people doing to minimize the performance degradation
due to multiple threads contending for access to the tree (in MCTS)?
Do you only lock a portion of the tree? How would that work?
___
computer-go mailing
I considered something similar. But instead of using a win count and a loss count, I use a win count and a simulation count. In that scenario, you would
update the simulation count immediately, and then maybe update the wincount once you know the result. But I haven't tried it either.
I use atomic increments and atomic reads. It's really simple x86
assembly. To do that, I used to have a counter for wins and a total
simulations counter, but switched to wins and losses counter. Doing
that allows independent increments to those counters.
I have not done a lockless
Hi Brain,
I get a superko bug report or two almost every month since CGOS has been
running (2 or 3 years?)It's usually due to a misunderstanding of
which specific superko rule CGOS uses. CGOS uses positional superko.
I'm quite sure there is no bug here. There are OTHER bugs in the
server,
it's simply too easy to write the code to check for this
on the server side for it to be a bug.
:)
s.
2009/4/13 Don Dailey dailey@gmail.com:
Hi Brain,
I get a superko bug report or two almost every month since CGOS has been
running (2 or 3 years?) It's usually due to a
