On Wed, Oct 13, 2010 at 8:20 AM, Michael Williams <
[email protected]> wrote:

> Good points, but the suggestion wasn't meant as a method of
> enforcement on the policy, but instead a feature of convenience to
> make it easier to follow the policy.  If the ratings converge fast,
> there is little reason to bypass the policy.
>

But it doesn't accomplish much and takes away a little flexibility.    A
learning program for instance would not be solved by this for instance so it
is not really particularly effective.

Don



>
>
> On Wed, Oct 13, 2010 at 8:08 AM, Don Dailey <[email protected]> wrote:
> >
> >
> > On Wed, Oct 13, 2010 at 7:57 AM, Michael Williams
> > <[email protected]> wrote:
> >>
> >> Yeah, but don't design the system for a case that isn't being done.
> >>
> >> You could even make this automatic in the CGOS client by specifying a
> >> base name in the config file and having the client append a hash of
> >> the executable.
> >>
> >
> > It's funny you say that,  I once considered doing exactly that.    I
> decided
> > not to however as I think it's messy.  it would be trivial to hack the
> > script to send the same checksum each time and it's not always going to
> work
> > anyway - if your binary is loaded via a shell script for instance you
> would
> > be checksumming the script, not the actual binary.     If your program is
> > called with different command line arguments (which some of mine did) you
> > essentially change the program without changing the binary.      I
> decided
> > it was too ambiguous and difficult to do right.
> > Since it is easily circumvented it seems like the best way is an advisory
> > system anyway.
> > Don
> >
> >
> >>
> >> On Wed, Oct 13, 2010 at 7:52 AM, Don Dailey <[email protected]>
> wrote:
> >> >
> >> >
> >> > On Wed, Oct 13, 2010 at 7:45 AM, Michael Williams
> >> > <[email protected]> wrote:
> >> >>
> >> >> Don, as for the program changing strength, I thought the recommended
> >> >> system was to create a new CGOS name when you change something in
> your
> >> >> program?  I know it can't be enforeced, but just reminding people to
> >> >> try to stick to that policy is probably enough.
> >> >
> >> > Yes, that is how it should be done.
> >> > The only issue here is if someone creates a program designed to learn
> as
> >> > it
> >> > plays.   If we do it bayes-like then a workaround would be to
> >> > periodically
> >> > rename the program.
> >> >
> >> >>
> >> >> On Tue, Oct 12, 2010 at 10:53 PM, Hideki Kato <
> [email protected]>
> >> >> wrote:
> >> >> > http://cgos.boardspace.net/19x19/bayes.html
> >> >> >
> >> >> > Hideki
> >> >> >
> >> >> > terry mcintyre: <[email protected]>:
> >> >> >>Is there a URL for the 19x19 bayeselo table?
> >> >> >> Terry McIntyre <[email protected]>
> >> >> >>
> >> >> >>
> >> >> >>Unix/Linux Systems Administration
> >> >> >>Taking time to do it right saves having to do it twice.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>---- inline file
> >> >> >>_______________________________________________
> >> >> >>Computer-go mailing list
> >> >> >>[email protected]
> >> >> >>http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
> >> >> > --
> >> >> > Hideki Kato <mailto:[email protected]>
> >> >> > _______________________________________________
> >> >> > Computer-go mailing list
> >> >> > [email protected]
> >> >> > http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
> >> >> >
> >> >> _______________________________________________
> >> >> Computer-go mailing list
> >> >> [email protected]
> >> >> http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
> >> >
> >> >
> >> > _______________________________________________
> >> > Computer-go mailing list
> >> > [email protected]
> >> > http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
> >> >
> >> _______________________________________________
> >> Computer-go mailing list
> >> [email protected]
> >> http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
> >
> >
> > _______________________________________________
> > Computer-go mailing list
> > [email protected]
> > http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
> >
> _______________________________________________
> Computer-go mailing list
> [email protected]
> http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
>
_______________________________________________
Computer-go mailing list
[email protected]
http://dvandva.org/cgi-bin/mailman/listinfo/computer-go

Reply via email to