-
Notifications
You must be signed in to change notification settings - Fork 27
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
Input inconsistent with MKL Pardiso and example in README.md #73
Comments
It seems loading MKLSparse breaks things. My guess is that https://github.com/JuliaSparse/MKLSparse.jl/blob/6060cd08a2586b275c95aac650c379ff48130ef7/src/MKLSparse.jl#L6 sets MKL in 64 bit mode but Pardiso.jl assumes that integers should be passed to MKL as 32 bits (unless Lines 29 to 30 in 81c8391
|
Perfect! Indeed without loading |
Well, not perfect :P. We should figure out a way to make the two packages collaborate. |
It is indeed surprising that pardiso still uses 32-bit integers. |
For your information, on my system const MklInt = (Base.USE_BLAS64 ? Int64 : Int32)
# or simply?
const MklInt = LinearAlgebra.BlasInt |
The problem is that SparseMatrices in Julia has It's just kinda hard how to do this properly because the MKL Interface state is global and packages use it like it is their own local setting to play with. |
Any work around for using both Pardiso and MKLSparse? Using SparseMatrices with Ti=Int32 only? |
I just tried to run the example in the README.md with
MKLPardisoSolver
.I use MKLSparse v1.1.0 and Pardiso v0.5.1 in Julia 1.5.1. MKL is installed automatically by MKLSparse.
Does somebody have any idea what could be the issue? The input matrix sizes seem to be correct.
Thank you for this nice package!
Example script:
Error message:
Environment:
The text was updated successfully, but these errors were encountered: