Improve handling of ambiguous utterances in DeterministicIntentParser #773
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ClemDoum
approved these changes
Mar 22, 2019
Codecov Report
@@ Coverage Diff @@
## develop #773 +/- ##
===========================================
+ Coverage 88.02% 88.08% +0.06%
===========================================
Files 76 76
Lines 4491 4497 +6
Branches 853 855 +2
===========================================
+ Hits 3953 3961 +8
+ Misses 402 401 -1
+ Partials 136 135 -1 |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
This PR affects two APIs of the
DeterministicIntentParser:parse: when a match is found for several intents, then theNoneintent is returned as there is ambiguityget_intents: when a match is found for several intents, then the probability is set to1/len(intents)for each of the matching intentsChecklist: