From what I know about rulesets, I actually prefer AGA. I believe it
was designed to have the same result for both area and territory
scoring. It has the pass costs one point rule. There's something
special about if white passes first because then the number of stones
places on the board are
However, I will probably maintain the current scheduling
algorithm which
will make the larger mismatches fairly rare though not impossible.
This
will be good because it means we will still prefer non-handicap games,
and
I'm guessing that the vast majority of games will not be be large
hendicap
My plan was to simply use the same scheduling algorithm I currently
use. I would take the weaker base player and see if handicap
versions of himself more closely matches the ELO rating needed to
give an even game.
I assume the same method of an updated engine connecting with a new
login still
There are 3 gtp commands for handling this:
fixed_handicap
place_free_handicap
set_free_handicap
You are arguing that fixed_handicap, even though it's quite
explicit, is the wrong one to use in this situation?
set_free_handicap would also work - the server just specifies
the points and
Yes, in Chinese rules you need to compensate white for the extra area
you gain from the actual stones. The handicap is only meant to be the
extra strength/stability.
To be slightly more specific, the extra compensation is specific to
area scoring rule systems. In a game with only two passes,
this might be a counterproductive idea,
but does anyone who mc's also ponder?
I think I've heard that valkyra ponders.
___
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
You
published it everybody will appreciate, and start using. But I
guess
it wasn't easy to see benefits.
I wonder how many really good ideas came through this list
unnoticed.
Best Regards,
Lukasz
On 12/11/06, House, Jason J. [EMAIL PROTECTED] wrote:
Wow. Did
DAG's have a problem with graph history, especially with super ko
considerations. Do you need the parent play for more than ko
considerations?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter Drake
Sent: Thursday, December 07, 2006 5:47 PM
To:
What are peoples perspectives on the KGSWishlist maintained at senseis?
It seems like someone long ago decided to overhaul the page(s) and then
stopped. For kgsGtp, I've seen more than one page dedicated to issues
(but only one has a response from wms). With cgoban3 out, is it a good
time to
I've debating trying to switch over to D with my project, but have not
yet done it. I use http://www.boost.org for a number of missing
features of C++ and worry about simply not having such things available
if I did switch over. I also worry that using D would scare away
developers.
I'd be a bit more careful about the comparison with alpha-beta in
section 2.3. I believe that iterative deepening of alpha-beta is very
common. It can be argued that when iterative deepening is used, an
early termination isn't very detrimental. I've seen people get
completely turned off to a
11 matches
Mail list logo
