score_cutoff ? #209
|
The output should not be None in case 1 as the score_cutoff matches the fuzz.ratio. Why is it returning None in case1 but not in case2? |
Answered by
maxbachmann
Apr 13, 2022
Replies: 1 comment 2 replies
|
Yes the output should not be None in this case. The reason for this issue is that I perform some calculations using the score_cutoff internally to figure out thresholds to quit execution early. I currently do not take into account the imprecision caused by floating point math. I still need to think about how to address this in an optimal way. For now a workaround would be to select a slightly lower value like |
2 replies
Answer selected by
maxbachmann
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes the output should not be None in this case. The reason for this issue is that I perform some calculations using the score_cutoff internally to figure out thresholds to quit execution early. I currently do not take into account the imprecision caused by floating point math. I still need to think about how to address this in an optimal way.
For now a workaround would be to select a slightly lower value like
79.99, which is not affected by this small imprecision. However this should definitely be fixed in RapidFuzz going forward.