[Computer-go] Go Aesthetics

2016-01-11 Thread Gonçalo Mendes Ferreira
Hi, some time back I mentioned creating a program that evaluates the aesthetics of a game of Go. Has anyone given it some thought? I'd love to have a comparison between professional and amateur dan matches, or across time periods or players. There are a few papers on aesthetics for chess so I

Re: [Computer-go] Go Aesthetics

2016-01-11 Thread Robert Jasiek
Is playing bad moves good for aesthetics? No? Then why call it aesthetics? Call it perfect / good play. The most "beautiful" stone is bad if it is dead. -- robert jasiek ___ Computer-go mailing list Computer-go@computer-go.org

Re: [Computer-go] Go Aesthetics

2016-01-11 Thread Steven Clark
It's an inherently subjective thought-exercise -- ask 10 different players and you will get 10 different ideas of what constitutes beauty. I'm not even sure I agree with the metrics proposed in http://www.wseas.us/e-library/transactions/computers/2008/26-184.pdf for chess -- why is it inherently

Re: [Computer-go] PhD thesis on MCTS

2016-01-11 Thread valkyria
My first montecarloprogram Viking worked something like this (this was before UCT). It used alpha-beta evaluating each terminal node with 500 simulations. But I would do early cutoffs after 50 moves or so if a coinfidence interval was outside the current alfa or beta. This together with heavy

Re: [Computer-go] PhD thesis on MCTS

2016-01-11 Thread Hendrik Baier
Hi Xavier, I have considered this, but even level-2 Nested MCTS requires quite a bit of thinking time. Let's say you can do 1000 playouts per second in your game, and you want to do at least 500 playouts on levels 1 and 2 for each move decision. Assume your playouts have 50 moves on average. Then

Re: [Computer-go] Computer-go Digest, Vol 72, Issue 9

2016-01-11 Thread Yuandong Tian
Hi Nick, Thanks for mentioning our team! This is our first tournament. Hopefully we could do better next time. Best, Yuandong On Mon, Jan 11, 2016 at 4:00 AM, wrote: > Send Computer-go mailing list submissions to > computer-go@computer-go.org > >