Re: [computer-go] Re: Core i7 performance in computer-go

2009-06-07 Thread Łukasz Lew
2009/6/6 Hideki Kato hideki_ka...@ybb.ne.jp: Hi Lukasz, I have five core2 and one i7 computers running at home.  I prefer i7, though don't have exact measure. The most important difference is the memory interface, ie, core2 uses a obsolete common bus (FSB) while i7 uses p2p connection with

Re: [computer-go] Tweak to MCTS selection criterion

2009-06-07 Thread Christian Nentwich
This is kind of interesting. Is anybody measuring their playout performance in real-time at the moment and performing this sort of computation, to check if overtaking the leading move is mathematically impossible? It's interesting with UCT because of the interplay between the time

Re: [computer-go] Tweak to MCTS selection criterion

2009-06-07 Thread Magnus Persson
I think all principles I use in the time management for Valkyria came up in this thread more or less. 1) Valkyria selects move that has been searched the most. 2) It is given a base time for example 20 seconds early on on 9x9 CGOS 3) The base time is adjusted down if the program is winning

Re: [computer-go] Tweak to MCTS selection criterion

2009-06-07 Thread Don Dailey
2009/6/6 dhillism...@netscape.net I had the early stop rule and didn't know if anyone else had thought of it. But I never considered the pebbles rule, which somewhat conflicts with the early stop rule. But as I layed out above I think you could do both. This is probably one of those

Re: [computer-go] bots and handicaps (Re: New CGOS)

2009-06-07 Thread steve uurtamo
The handicap system is imperfect anyway, it's almost a coincidence that it works as well as it does. okay, this sounds like chess bias. the handicap system *defines* the difference in skill levels in go. it's a coincidence that something like ELO can match fairly well to stones. not the

Re: [computer-go] Re: Core i7 performance in computer-go

2009-06-07 Thread Hideki Kato
Łukasz, is the program multi-threaded? Corei7 920 runs about 7% slower than core2 at the same clock. Possibly due to the optimized code for core2? Experimental results follow. On a 3 GHz (333 x 9) core2 Q6600: 20 playouts in 1.49209 seconds 134.04 kpps 44.6798 kpps/GHz (clock independent)

Re: [computer-go] bots and handicaps (Re: New CGOS)

2009-06-07 Thread Don Dailey
On Sun, Jun 7, 2009 at 11:02 AM, steve uurtamo uurt...@gmail.com wrote: The handicap system is imperfect anyway, it's almost a coincidence that it works as well as it does. okay, this sounds like chess bias. the handicap system *defines* the difference in skill levels in go. it's a

Re: [computer-go] Re: Core i7 performance in computer-go

2009-06-07 Thread Łukasz Lew
2009/6/7 Hideki Kato hideki_ka...@ybb.ne.jp: Łukasz, is the program multi-threaded? Is is single threaded and 32-bit. Corei7 920 runs about 7% slower than core2 at the same clock. Possibly due to the optimized code for core2? That is my belief. I will reconsider buying i7. Thank you for

Re: [computer-go] bots and handicaps (Re: New CGOS)

2009-06-07 Thread terry mcintyre
Pro ranks are assumed to be about 1/3 of a stone; the one stone per rank formula applies to amateur ranks. I have watched a pro 8p regularly give three stones to a 6 dan amateur. A weaker pro might give the same player 2 stones. Some ( including myself in the past ) have argued that they can

RE: [computer-go] bots and handicaps (Re: New CGOS)

2009-06-07 Thread David Fotland
I can't really agree with this statement. My customers tell me they would much rather play a challenging even game against an opponent of their level, than a challenging handicap game against a much stronger or much weaker opponent. This is why version 12 of Many Faces has levels that are

Re: [computer-go] bots and handicaps (Re: New CGOS)

2009-06-07 Thread Jason House
At 1 or 2 stones difference, the handicap system works well.At greater handicaps it's skewed. The coincidence that I'm talking about is that it works to a reasonable degree at larger handicaps. The handicap system is based on the idea that no matter what your level of play, you

RE: [computer-go] Tweak to MCTS selection criterion

2009-06-07 Thread David Fotland
Many Faces does this. This is kind of interesting. Is anybody measuring their playout performance in real-time at the moment and performing this sort of computation, to check if overtaking the leading move is mathematically impossible? Christian Don Dailey wrote: 2009/6/6

Re: [computer-go] bots and handicaps (Re: New CGOS)

2009-06-07 Thread terry mcintyre
I was referring to matches against pro players. It's going to be a while before a computer can win even games against pros, therefore we must assume that any such matches will involve the program taking a handicap. My personal preference is the strongest possible opponent. When reviewing games

RE: [computer-go] bots and handicaps (Re: New CGOS)

2009-06-07 Thread dave.devos
Don Daily wrote: so for instance a professional player with a relatively low professional ranking does not need as many stones as indicated by his opponents ranking to beat another professional WHO IS SEVERAL RANKS HIGHER. For centuries pro ranks were defined by the handicap required against

RE: [computer-go] bots and handicaps (Re: New CGOS)

2009-06-07 Thread dave.devos
I am 3k on KGS and I'd say that I win nearly every game that I give handicap and lose over half the games that I receive handicap. That would seem to imply that more handicap should be given near my rank. That is because the KGS rating system is not based on handicap. It is

[computer-go] Tweak to MCTS selection criterion

2009-06-07 Thread Brian Sheppard
check if overtaking the leading move is mathematically impossible? Yes. Pebbles does this. Please note that the discussion has veered into time control policy, which is not the subject of the original post. The original post discusses move selection policy: when your program stops, for