-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
UnexpecTEDIntentPolicy
predictions fix
#9079
Merged
Merged
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
b7192d4
Draft _collect_action_executed_predictions
alwx e9d428f
Update to correctly run predictions when using `rasa test`
alwx d5a4ed9
action_executed_eval_store.add_to_store
alwx 44fb424
Updated format for stories
alwx cca2e1c
Reformatting and bugifx
alwx 4f5dc96
Merge branch 'intent-ted' into intent-ted-wrong-prediction
dakshvar22 82b2023
formatter
dakshvar22 f28b660
fix some tests. 1 remaining
dakshvar22 0114da1
more tests
dakshvar22 5fd3ade
fix remaining test
dakshvar22 6f39c42
restructure it a bit
dakshvar22 8aa3327
formatting and hardcoded strings removed
dakshvar22 4f0bc50
WarningPredictedAction
alwx a4840cd
Code style fix
alwx ea4fe86
Code style updates
alwx acf2a44
Fixes and `test_action_unlikely_intent_fail_on_prediction_errors`
alwx 5c95855
Formatting
alwx 2caf15a
Code style & test updates
alwx 6924b20
fix tests and code formatting
dakshvar22 73a9282
Merge branch 'intent-ted-wrong-prediction' of github.com:RasaHQ/rasa …
dakshvar22 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we have an predict
action_unlikely_intent
but it's not in the story, and the following action is correct, won't be now end up with twoWronglyPredictedAction
in the tracker?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we predict
action_unlikely_intent
then we ask for another prediction, and only add thisWronglyPredictedAction
if there is a mismatch in expected/predicted. This is the only case when twoWronglyPredictedAction
s will be added but that's perfectly fine because we filter outaction_unlikely_intent
s from logs.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok but if
predicted_action_unlikely_intent and predicted_action != expected_action
on line 584 isFalse
, thenpredicted_action
is not changed because we don't re-run so we nopredicted_action_unlikely_intent and predicted_action != expected_action
on line 609 will also always beFalse
. And if line 584 isTrue
then we know the next action can't be anotheraction_unlikely_intents
right? So can we change 609 to justif action_executed_eval_store.has_prediction_target_mismatch()
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's correct. Changed that.