-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Unpredictable ZeroDivisionErrors in direct_confirmation_measure #2181
Comments
Hi @alexeyev, thanks for the report, please provide minimal code example with data that reproduce your issue. |
Non-reproducible (not enough information) |
I am getting this using version 3.4.0 (conda 3.4.0-py36h14c3975_0) when running |
Hi @johann-petrak please provide the code example for reproducing your issue (including a data that you used for training) |
Sadly it is a dataset of dozens of gigabytes of size and the license does not allow me to share the data. If this is the code producing the error |
@johann-petrak this will be really nice, please do 👍 |
As I expected, this happens because |
@johann-petrak so, can you try to run your code with the debugger and see step by step how this attribute changed? |
I also have a same problem. I found that This problem is caused by learning LDA, not CoherenceModel. |
@hallelujahdrive hello, please give us a minimal reproducible example (code + data that produce current issue) |
Is the method |
I reproduced the problem with the following code.
|
Could somebody in the know please explain what the intended use of this function is (see my previous comment) i.e. is it supposed to work for a corpus that is not absolutely identical to the training corpus? As pointed out, this seems to happen whenever a corpus word present in the topics does not exist in the corpus passed to the method. Why I also find very confusing is that the function returns a list of pairs (topicrepresentation, coherence) where the first element is the actual word distribution for the topic. Why does it not return the index of that topic instead? Is it the case that the topics returned here are supposed to be identical to the ones stored with the trained LDA model and accessible through |
BTW should be fixed by #2259 |
Hello.
Thank you for your great work!
It seems that the problem #1064 is back. I get a lot of this
when I use the version 3.5.0 installed from pypi.
Thanks in advance.
What other info should I provide?
The text was updated successfully, but these errors were encountered: