-
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
clean up duplicated errors during training #3900
Comments
check if this is still the case |
I havent been able to get the earlier warning because it only happens after you remove an action from everywhere. However for example in 1.7.0, if you remove a categorical slot that is in your stories from your domain and then try to train (scroll to the right):
|
|
@erohmensing @wochinge this sounds super low priority to me. How bothering is this? Are the warnings valid? |
The warnings are valid, it just throws every time it sees the slot/intent which is kind of annoying. I agree that it's very low, definitely a "nice to have". We can put it on the "help wanted" project instead if you like. |
ok 👍 added the labels. Thanks @erohmensing ! |
I removed it from the project board and the priority label because there's a separate board for contributors, does that make sense? |
ahhhh, I thought the label |
taking a look at this now. They seem to be different kinds of warnings:
|
There are certain errors while training that get processed per line, and the repeat a ton when the error shows up a lot:
It would be good if we, for example in this case, stored a set of actions for which this error occurs, and then after training dumped all of the warnings (but only one for each action). This also applies to other warnings like "tried to set non-existent slot XXX"
The text was updated successfully, but these errors were encountered: