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
Intermittent ZeroDivisionError: division by zero #34
Comments
Thanks for detailed bug report! This may be the same as issue #33. I believe the latest master version should have fixed this, but I haven't put out a release on pip yet (waiting to roll a few more bug fixes and features together). If you have time to clone the master branch from github and install it (after removing the old pip version) and try that instead I would appreciate it. I believe it should fix the issue you are seeing, and if it doesn't then I clearly have a little more work to do. |
@lmcinnes thanks for your quick response. It seems the problem has been resolved on master. I've run several dozen runs since reinstalling and haven't hit the division by zero error, so I think it should be safe to close this issue. Thanks again for this great work! |
Thanks for checking that out so fast. |
I am running to zero division errors every couple of runs, I am using CentOS, and spyder (py 3.6).
|
@100518832 did you git clone from master then run |
@duhaime, I do not recall running the python setup.py install; however, I will try this. Also, I have noticed that I only get a zero division error with the following three argument parameters.
Here are all the parameters I am currently testing through
|
@100518832 I'd try installing from the repo's |
I'm now getting this error with the Code:
Traceback:
At first I thought it was related to #33 because I can get the error to go away by setting Additional info:
|
This is somewhat disconcerting, and it is non-obvious to me where exactly this could be occurring. One thing you could try, presuming the compute isn't too expensive, is turning of the numba compilation of the inverse transform related functions and running again -- that way we can get a stack trace to the exact location of the error. |
So the actual error is coming from here, in Traceback is kinda weird-looking since I ran it through the Pycharm debugger, but here it is:
|
I think the problem is that that should be |
That did it! And that makes sense based on how |
Can I assume that this will arrive with your upcoming PR, or should I fix it and push it myself? |
I changed it on my fork, so it'll get included in my PR. I'm ready to submit that today btw -- just want to confirm about what I commented on #367 |
Excellent -- I'm looking forward to it. Thanks for all your hard work on this! |
Any update on this? I have a dataset that seems to be throwing it when the size of the data is large. |
This is a fantastic library, thanks very much for your great work. Periodically though, I'm getting a
ZeroDivisionError: division by zero
while building a UMAP projection. My data doesn't change, nor does the way I call the UMAP constructor:Once in a while (maybe 5% of runs) this throws the following trace (umap version 0.1.5):
I took a quick look at the
make_tree
function but that didn't show much--the real problem seems to be swallowed in the stacktrace by the recursion. Do you have an idea what might cause this? I'll upgrade to the latest master and see if the problem continues.The text was updated successfully, but these errors were encountered: