Re: [Please Help] Pattern Matching Comparison

[Darren Cook <darren@xxxxxxxxxxxxxx>]

>    1. PAT Tree: guess all of you guys know what it is. If not, go read some
>algorithm books.

What is a PAT Tree? :-)

Yes, I looked in an algorithm book and it doesn't have it. Closest was
Patricia Tree - is that what you mean?


A few thoughts about how humans use patterns (and IMHO how computers should
use them):

1.Stones and points have meaning. If your patterns just store
empty/black/white the program won't appreciate the real meaning. The larger
the pattern the less this matters, but the fewer times your pattern can be
used. A database of whole board fuseki patterns is an example.

2.Variable size and shape. Patterns are normally bounded by features. A
feature is what you meet at the edge of a featureless region. So in the
fuseki the features are a long way away (so the patterns are big) and in
yose/tesuji patterns the features are very close (so the patterns are small). 

3.The pattern accross time (a.k.a. moves sequences; joseki) is almost as
important as the spatial pattern [1]. [2]

4.Human patterns are extremely rich in context. Programs should have as
much context in their patterns as possible [3], but it still won't be good
enough. However they can make up for this by using lots and lots of
patterns [4]

Darren



[1]: Ooh! Clever word :-).

[2]: Just being pretentious. I'm not entirely sure what I mean by this.

[3]: This is very difficult.

[4]: Which is why I firmly believe you must be automatically generating
your patterns, not putting them in by hand.