This is similar to the approach I used many years ago: i.e. a hash code that had a core and then added stones in the surrounding vicinity. I believe I stopped at first stone but it was good enough to be able to store the adjacent corners in 19x19 openings.This is my try to design a pattern database. http://senseis.xmp.net/?PatternMatching
In order to get a high "pro prediction" (relevancy) with an "exact matching" pattern-based approach, you need millions of patterns at minumum.I'd like to echo this point. I didn't have enough, so I had layered databases:
Another thing I found was that small pattern like 4x4 are of limited use. 5x5 is better, but only when you include info on # liberties & stones.And I'd like to echo this, but my conclusion was liberties is not enough and you need tactical search results for every chain and every point in the pattern (you mentioned the need for ladder break information in your senseis article but that is just the start in my opinion).