Assuming that kgsGtp's way of compensating white for the handicap
stones is incompatible with CGOS's proposed handling, (in other words,
if it is the case that kgsGtp sends a komi value that does not include
this compensation, even though the final score will.  Is this true?) I
would like to briefly argue for the creation of a custom command that
will be sent by CGOS in order to make its expectations explicit,
simply because there would be less margin for error on the part of
programs' operators.  (in setting them up properly)

Of course, this command will be either unimplemented or a no-op, in my
own programs, simply because I think that this is already the must
sensible way to handle these points.  However, there may be some
reason that I am not aware of why some program authors might prefer
different behavior as a default.  Having the command may be a benefit
to them.

By the way, how is this same issue handled in .sgf files?  Do various
programs agree on the final scores of handicap games that are recorded
in .sgf, with a "KM" property specified?  (Might it depend on an "RU"
value that is specified?)

Weston

On 12/29/06, Don Dailey <[EMAIL PROTECTED]> wrote:
I agree with you.   Weston's post convinced me that the program should
know
in advance what the handicap is to be and thus sending consecutive
genmove
commands is not really correct technically speaking.

I don't like implied compensation, but apparently it is popular and KGS
does it.   However,  CGOS won't be doing it.

I am really torn about this,  but in the end I don't want to implement
something I consider slightly broken just because another server does
it.

I think currently this falls under the category that you need to tell
your program (via a command line parameter or config file) what the
rules of compensation are.   The rules for CGOS will be that komi
by itself tells you everything you need to know about compensation.

- Don


_______________________________________________
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/

Reply via email to