-
Notifications
You must be signed in to change notification settings - Fork 230
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] Interface sparse Cholesky and QR factorizations #2121
[CUSOLVER] Interface sparse Cholesky and QR factorizations #2121
Conversation
49845d5
to
df27892
Compare
df27892
to
e93e744
Compare
1340b3f
to
76e0504
Compare
As seen on CI: https://buildkite.com/julialang/cuda-dot-jl/builds/4483#018b7ff0-eaf5-41cb-8e60-a5f7e112a3cc
|
Ah, I guess CI didn't fully run on here because you marked it as 'ready' only after pushing. I'll push a fix. |
Very nice! One comment that I have is that the functions use British English (as opposed to American English) spelling for words such as analyze/analyse and factorize/factorise. This is sure to spark a heated debate, though I am not sure what currently the default is in Julia. Maybe it would be better to stay away from words that have these differences in function names. |
Would it be possible to support the type of |
@shakedregev @ytdHuang |
@amontoison |
I suggest to try a Krylov solver with an incomplete ILU(0) preconditioner in that case. You can also solve |
@amontoison |
What is the problem that you want to solve? |
Kinda hard to explain ... |
Why is this not for example overloading |
CUSOLVER has sparse Cholesky and QR factorizations but the API is not documented...
Performing these factorizations on GPU is something that many Julia users want.