Terry, Petr & David, many thanks for taking the time to review
peepo.com and the enthusiastic feedback,
html5 and the web offer fantastic opportunities to promote Go,
develop social networks and improve game tools and visualisations.
Its not just about Go, but also helping foster understanding of
complex issues.**
Terry,
I can only provide what the Go engine exposes, so please encourage the
developers,
in this case Fuego may not provide a kill alert, but certainly it is
in codebase, Fuego has strong kill facility.
I will also chase tx.
probably red is too emotional, see: How to use Colour on ATC radar
displays. L.Reynolds
all games are logged, originally there was a full play, match, chat,
clocks, game history etc interface in LAMP:
http://peepo.com/pics/lamp.jpg
but this remains to be moved across to nodejs-redis
Petr,
your sociomap visualisation in fig 4 is most interesting, what are the
three axis labels?
do you have other examples?
David,
try giving Fuego handicap (pass) stones assume 12k
see: http://peepo.com/pics/go.jpg
Fuego like most MC programs plays erratically once behind, in your
example the loss is extreme,
see thread: 4 'easy to avoid errors', your screengrab is a great
representation of this issue.
also,
I have asked the Fuego authors about enabling early resignation,
there is currently no simple method.
also see thread: Could a 'doubling dice'** encourage early
resignation by programs?
**read my chapter "Browser-native games that use real-world xml data"
to be published 02/2011 in the book: Business, Technological and
Social Dimensions of Computer Games
http://www.igi-global.com/bookstore/TitleDetails.aspx?TitleId=46177
_______________________________________________
Computer-go mailing list
[email protected]
http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
