On Thu, Mar 18, 2010 at 10:04:49PM -0500, Peter Karman wrote: > > So, I think what we should do is clean up PhraseScorer so that it is > > clearer, > > then create ProximityScorer by cloning and modding it. It's a mild > > violation > > of DRY, but that doesn't bother me. All of us will benefit from the > > cleanup, > > and you'll walk away with a thorough understanding of the algorithm and a > > top-flight ProximityScorer. > > ok. I'll go this route, creating a new KSx::Search::ProximityScorer. I'll send > some patches along when I have something useful.
As a first step, how about I sweep through and expand the comments in PhraseScorer? It would be similar to what I'd say on the mailing list explaining the algorithm, only we'll actually make progress on the code. :) Marvin Humphrey
