Skip to content
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

Umlauts within phrase are causing odd intent matches #886

Open
Corasonn opened this issue Aug 20, 2020 · 1 comment
Open

Umlauts within phrase are causing odd intent matches #886

Corasonn opened this issue Aug 20, 2020 · 1 comment
Labels

Comments

@Corasonn
Copy link

Corasonn commented Aug 20, 2020

Some of my entity values contain umlauts. When I want to recognize them with a specific intent, snips matches it so any other intent that also contains this entity. But the right intent would fit 100%. With any other value without an umlaut, snips will match the right intent with 1.0 score.

Expected:
Intents with entities with umlauts are matched correctly.

Environment:

  • OS: OSX 10.15.5
  • python version: 2.7
  • snips-nlu version: 0.20.1
@Corasonn Corasonn added the bug label Aug 20, 2020
@Corasonn
Copy link
Author

I found the problem. When I have more than 10000 entity values, snips doesn't build some entity variations due to a better building performance.
PR was: #804

Unfortunately, it seems to break umlauts when the "case" variation is missing. I forked the project and changed it hardcoded (https://github.com/Corasonn/snips-nlu).
I'm not a python developer, so if someone knows how to set it via flag, it would be great!

@Corasonn Corasonn reopened this Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant