[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: computer-go: rules

At 02:52 PM 11/21/99 -0800, you wrote:


I haven't tried to explicitely code any of his rules, just
thought about some of them.  One example:  I took a lesson
from him on crosscuts, and he has a rule about when to extend
and when to atari.  It goes something like:  If you can save
both of your stones, extend and fight.  If you can't, choose one
to sacrifice, and atari both sides.  He went through a bunch
of examples, and it helped my game.

i think his current version of this is:

1. can you save both? (if yes, help the weakest)
2. which stone is more important?
3. which stone is more valuable (if both are important)?

the last two are sometimes hard to answer.


  But coding this for a
computer is difficult.
maybe some of the rules would be more simple, but this appears to be high
level stuff.

Either do a lot of local reading to see if
the stones can both be saved, or recognize many different local shapes.
and as you have already stated, this look ahead had to be deep and smart
(maybe goal directed?)

A strong player can usually tell without much reading if the stones
can be saved, but there is a lot of unconscious pattern recognition

unfortunate, but true


... Ray Tayek wrote:
>
>i''ve been hanging around mr. yang for a number of years now ...
>his set of rules does seem fairly small ....

---
Ray (will hack java for food) http://home.pacbell.net/rtayek/
hate spam? http://www.blighty.com/products/spade/