[computer-go] CGOS Monte Carlo Simulations

[Don Dailey]

I'm working on a new server and I am considering how to deal with this. 

I have had a few requests to provide a way to "erase" an entry.  Entries
cannot technically be wiped because CGOS keeps a record of all the games
it's ever player and so this might cause some confusion, but we could
provide a way to "clean" it from the main list.

I have also considered to add versioning.  It would be a separate field
that distinguishes the main program from other versions of itself.  It
would still be considered a separate entity for rating purposes but it
might start out its life with the same rating as the nearest version of
the same main program, but with a much higher K-factor.  

It's not clear to me what is best - but I'm thinking about it.   I don't
intend to get too complicated and I won't provide every bell and
whistle, but I would like to make some improvement in this regard with
something simple.

The interface to this is what is more complicated.  Version number by
itself is very simple, but providing options for deleting entries and
other things is less natural.

One consideration is that you have to register an entry via a web page
and also use this page to provide some configuration options and the
ability to remove entries from the display.    But now it's starting to
get more complicated!

Ideas?   The first consideration is what extra features do we want to
provide, then it becomes "how to provide it."    I think the first
consideration is:

   1.  More control over "clearing" an entry from the main page.

   2.  Separate version info.   GTP provides this so there is no 
       interfacing issues, but the behavior needs to be defined.

I already have a functioning server with a viewing client - you can
watch any number of games (as an observer) being played in real time.

- Don


On Mon, 2006-09-11 at 06:40 -0500, William Harold Newman wrote:
> On Sun, Sep 10, 2006 at 12:51:22PM -0700, Christoph Birk wrote:
> > >I expect most programmers to change the name if the program changes.
> > 
> > Even just for a bug-fix?
> > But it's ok ...  I'll change 'myCtest' after the weekend.
> 
> Probably some people release changed versions in smaller steps than
> others.
> 
> I don't have a program on the server yet, alas. But tentatively my
> lesson learned from this conversation is that when and if (1) I do
> have a program on the served and (2) I have reason to believe that the
> program has gotten a few stones stronger than the old version, then it
> is time to start over on the server with a new name. (Perhaps change
> name from myprog-1.2 to myprog-1.3, perhaps from
> myprog-takes-n-komi-vs-gnugo to myprog-takes-nprime-komi-vs-gnugo.)
>