Dave,
I ran current Fuego on my laptop for 600K simulations. Similar to the other
programs, it likes simply C7 with a .82 evaluation. However, the bad moves M19
and N19 are second and third in number of simulations. So there seems to be
some systematic problem with the playouts and/or the tree
Ok, so it's probably specific to Fuego like David Fotland and Magnus said.
Glad I could help ;)
Dave
Van: computer-go-boun...@dvandva.org namens Martin Mueller
Verzonden: vr 26-11-2010 16:49
Aan: computer-go@dvandva.org
Onderwerp: Re: [Computer-go] Dave Devos
Martin, how close were the 2nd and 3rd choices?
Looking at the bigger picture: is it yet possible for programs to do automatic
post-game reviews of losing games - possibly spending a few hours or days on a
single game - and locate weak spots in their own behavior?
Another question: at what
I'm working on Go Scoring Camera, an Android cell phone app that will
photograph a board, do image processing to figure out where the stones
are, and score the game for you. For the scoring part, I need a liveness
evaluator; and since this is a previously solved problem, I figure it
would be best
On Fri, Nov 26, 2010 at 1:50 PM, Michael Williams
michaelwilliam...@gmail.com wrote:
On Fri, Nov 26, 2010 at 1:43 PM, Jim Babcock jimrand...@gmail.com wrote:
I'm working on Go Scoring Camera, an Android cell phone app that will
photograph a board, do image processing to figure out where the
You should be able to rework Gnugo into a DLL life/death evaluator library.
Then you can use its evaluator in your payware app without having to
distribute your source code. You would just have to distribute the source
to the gnugo evaluation library.
I license Many Faces's engine for
The 4th UEC Cup start soon (10 am JST (+0900), November 27th) with 28
participants.
Top page: http://jsb.cs.uec.ac.jp/~igo/eng/index.html
Schedule: http://jsb.cs.uec.ac.jp/~igo/eng/schedule.html
Participants: http://jsb.cs.uec.ac.jp/~igo/eng/participant.html
Broadcasting on Ustream (semi final,
Le 26/11/2010 à 20:33, David Fotland a écrit :
You should be able to rework Gnugo into a DLL life/death evaluator library.
Then you can use its evaluator in your payware app without having to
distribute your source code. You would just have to distribute the source
to the gnugo evaluation
