-
Notifications
You must be signed in to change notification settings - Fork 4
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
cuSOLVER fails to compute eigenvalues for RMT #86
Comments
You got a warning from cuSOLVER: RMT can now offload the eigenvalue computation to the GPU using cuSOLVER, or it can use openblas which is multi-CPU. Try running RMT with the CPU implementation:
If the CPU implementation doesn't show this error then there's probably just a bug with the GPU code. |
Yes, that fixed the problem. I suppose we should leave this open if this is a potential bug in the GPU code. |
@bentsherman I'm still getting this error on huge chunks of correlation values... say from 0.92 to 9.71. When I turn off the cuda setting I see a similar issue but just get -1 values. Here's the output file:
Thoughts? |
So at those thresholds the prune matrix has 1 unique eigenvalue... that could also just be an artifact of the LAPACKE solver failing, but LAPACKE and cuSOLVER are both configured to print a warning if they fail. I think we'll have to look at the prune matrix at these thresholds to see if something looks unusual. Something is going wrong with the eigenvalue computation. |
This issue is almost a year old, but it is still a problem and needs fixing for folks who want to use RMT, so I'm going to leave it open. |
When I run RMT I see what seems like odd behavior. I start thresholding around 0.95. It ticks down the values and always reports that
unique egenvlues: 1
, but the matrix size, in the example below is 1360. That seems odd that the matrix would be that big and only have one unique eigenvalue, especially considering that the next level (0.900) suddenly has 1398 eigenvalues (the size of the pruned matrix).I think there may be a bug....
The text was updated successfully, but these errors were encountered: