RE: computer-go: Pattern matching

["Xu, Mousheng" <moushengxu@xxxxxxxxxxxxxxxx>]

Choosing patterns is easy.  I look at games the program played, and when
it
makes a bad move because a pattern is missing, I add it.  Since patterns
are
suggesting moves, not evaluating them, there is no issue with having too
many 
patterns, or multiple similar patterns that suggest the same move.  All
moves
are suggested for a reason, which leads to a natural partitioning of
patterns

* One question:
	Suppose for a board status, many (say 50 or 200) patterns are
matched, do you prioritize the patterns before you do the evaluation or
you evaluate every one of them?

* Thanks, David. You are really a open-minded person to share all of
your thinkings with us.

-- Mousheng