Skip to content
This repository has been archived by the owner on Aug 31, 2021. It is now read-only.

Near misses for min_distance thresholds #4

Closed
spencebeecher opened this issue May 15, 2016 · 1 comment
Closed

Near misses for min_distance thresholds #4

spencebeecher opened this issue May 15, 2016 · 1 comment

Comments

@spencebeecher
Copy link
Contributor

From README:

Note on min_distance thresholds - Each document is assigned to the closest candidate cluster. When we set min_distance we will filter out clusters that dont meet that requirement without going into the individual clusters looking for matches. This means that we are likely to miss some good matches along the way since we wont investigate clusters that just miss the cutoff. A (planned) patch for this behavior would be to also search clusters that 'just' miss this cutoff.

@spencebeecher
Copy link
Contributor Author

Removed min_distance in commit - a24cd4c

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant