On Mon, May 16, 2011 at 03:39:08PM +0100, Willemien wrote:
> There is allready GTP see
> - http://senseis.xmp.net/?GoTextProtocol
> - http://www.lysator.liu.se/~gunnar/gtp/
>
> Maybe it is best to find something that extents the gtp protocol.
> (but keeping most of it)
I think basing this on GTP would be a mistake. It is synchronous in
nature and is not as easy to parse as something JSONish. Also, it makes
assumptions about one side being a go robot. Of course, it makes a lot
of sense to reuse the concepts behind but I think the commonalities
won't amount to too much in the end.
> A questions where stands JSON for?
Google it out. ;-) It's a generic protocol syntax that is trivial to
parse on the client side.
> A suggestion, lets start a page on sensei's about it
I think this thread stems from a previous conversation between me and
Jonathan about making information about progressive reading of a program
more easy to parse by something external that visualizes them on board
(and incidentally, that something will be web-based). My proposed
example of how information "packet" that could be easily generated by
some MCTS Go Program (i.e. Pachi) would look like:
{ "playouts": 10000, "best": { "move": "F6", "value": 0.580823 },
"can": [ { "move": "F6", "value": 0.581 }, { "move": "F7", "value": 0.553 }, {
"move": "F8", "value": 0.614 }, { "move": "G7", "value": 0.528 } ], "seq": [
"F6", "C6", "C7", "D7" ], "owner_stats": [ { "move": "A1", "value": 0.31 }, ...
], "laddered_groups": [ "C3", "G5", ... ], ... }
Originally I assumed this would just go by a different channel than all
the genmoves, but maybe Jonathan wants to conceptually shift this
upwards.
--
Petr "Pasky" Baudis
UNIX is user friendly, it's just picky about who its friends are.
_______________________________________________
Computer-go mailing list
[email protected]
http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
