Re: [computer-go] Pattern matching - example play

["Frank de Groot" <frank@xxxxxxxxxxxxx>]

----- Original Message ----- 
From: "Ray Tayek" <rtayek@xxxxxxxxxxxxxxxxx>
Subject: Re: [computer-go] Pattern matching - example play



> your prediction rate sounds great. does it vary much between the
beginning,
> middle and end stages of the game?

Yes.
The prediction graph looks like a bathtub.

At the start, the system's Fuseki patterns are used.
Then the Joskie patterns are used and a whole lot of patterns that are not
striclt Joseki but large patterns that are common in the first 100 moves.

The more "tactical" a game is with (for me) an "erratic" game development (I
mean games that not are about a slow building up of equilibrium but are more
like one big exploding fight), the less well the pattern system predicts. I
have seen prediction rates as low as 19% for such games.

At the end, the pattern system also works well because end patterns are
about filling dame etc. Well-established ways to finish up things. So I
often see a 60% prediction rate in the first 100 moves or so.


> sure. but i suspect that most of them were trying to be helpful.

Nope. Most of them are trying to be asses.
The helpful people can be counted on the fingers of one hand, the rest has
made it a mission to tell me that I need to shut up until I am a good Go
player, or that I will be a failure with a Go program because I have made
the world's best Joseki expert system.
It really is very annoying and obvious some ego's feel threatened. It
becomes pure harrassment however when I start to receive private emails
with: "It won't work" and "You should learn G first". That sort of thing
doesn't help with tolerating the religious "arguments" here (starting with:
"I refuse to believe that.."). Plus the fact that I suffer from a brain
problem that makes me attack at the slightest provocation. I am not very
bothered by that anyway.


> good luck with your research.

You give me too much honor.
It's not research, really.
I look at things from a simple engineering POV. I am a "company" and the
only employee is me, and I am a "technician".
Implementing solutions is what I'm after, not endless debate and
experimentation..

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