-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Match threshold #4
Comments
hey @danyal i'll look into this ASAP |
hey @danyal we're trying out a similar feature in #3
you get 2 scores for every record (because sometimes pair distance aka dice's coefficient can't tell things apart)
it returns all scores, so you can do the threshold yourself:
is this sufficient for your needs? if so, i'll put it in a new gem release |
Hi Seamus, Yup that would serve my purpose though I think it would be cleaner if find Thanks, On Wed, Jan 9, 2013 at 7:40 AM, Seamus Abshere notifications@github.comwrote:
|
Looks great! Thanks so much. On Wed, Jan 9, 2013 at 6:29 PM, Seamus Abshere notifications@github.comwrote:
|
@danyal can you use this as a github branch? if not, i can rush a gem release. |
I can use the branch, no need to rush. On Wed, Jan 9, 2013 at 7:47 PM, Seamus Abshere notifications@github.comwrote:
|
fixed since version 1.4.1 i believe (c2e6f3e) |
Could you add an optional parameter to find that allows you to set a match threshold? I am looking for matches that are only really close vs. getting matches that are .2 or .3 in similarity. By setting the threshold I could eliminate anything that isn't almost exactly a match.
The text was updated successfully, but these errors were encountered: