[computer-go] Positions illustrative of computer stupidity ?

[Chrilly]

> One could use the heuristic that the outside is larger than the
> inside, but perhaps a situation can be created where this is not  true. 
> This might even be something beginning Go players could see/ understand.
>
> Peter Drake
> Assistant Professor of Computer Science
> Lewis & Clark College
> http://www.lclark.edu/~drake/
>
>
One could try to solve the problem by the additional rule: The inside point 
must be inside the bounding-rectangle of the string. This works in the 
position in InsideOutside.sgf, but if fails in InsideOutside2.sgf.
The problem can be solved reasonably. My point is: Even a - from the human 
point of view - simple problem is quite tricky. It is difficult to define 
"waterproof" rules.

This is one of the reasons that full-width Alpha-Beta does not work well. If 
there are some exceptions to a rule a (deep) searcher finds them. In chess 
one solves the problem by giving only the 100% rules a full weigth. 100% 
sure is the material-count, mate and stalemate. If e.g. a piece is attacked, 
there is some extra bonus for the attack, but this bonus is small in 
comparison to the material value of the piece. The full attack-bonus is only 
given when the piece is definetly off the board. The most difficult piece to 
evaluate is a passed pawn. There is no clear material value of a passed 
pawn.

Chrilly

-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsideOutside.sgf
Type: application/octet-stream
Size: 100 bytes
Desc: not available
Url : http://computer-go.org/pipermail/computer-go/attachments/20061122/096d7f4f/InsideOutside.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: InsideOutside2.sgf
Type: application/octet-stream
Size: 237 bytes
Desc: not available
Url : http://computer-go.org/pipermail/computer-go/attachments/20061122/096d7f4f/InsideOutside2.obj