Handle threshold_match_probablity 0 in predict() #2420 #2425
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated predict_from_comparison_vectors_sqls_using_settings function to handle threshold_match_probability 0 as None. Modified the logic in lines 100-117, this is to prevent maths errors when doing log2.
Type of PR
Is your Pull Request linked to an existing Issue or Pull Request?
Existing Issue #2420
Give a brief description for the solution you have provided
Whenever this predict function is called it will first check for 0 and assign threshold_match_probability to None.
Then when it is later passed into log2 it won't return a math error.
As its a minor change I haven't changed documentation or changelog.
PR Checklist