-
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
Using Pardiso64 in Pardiso.jl for Large Sparse Matrices #110
Comments
I don't have any experience with this, but maybe I could have a look. Do you have a MWE? In either case the line |
Sorry for the delay. Below is a MWE for testing. It runs perfectly as long as the number of nonzero elements is less than 2^{32} . However, if the count exceeds 2^{32} , an error occurs: “ERROR: InexactError: trunc(Int32, 2147483649)”
|
I am trying to use Pardiso for sparse matrix diagonalization, but my matrix has more non-zero elements than Int32 can handle. To resolve this, I need to use Pardiso64. However, when I set the solver parameter ps.iparm[35] = 1, I still get an error related to the number of non-zero elements exceeding Int32.
I have confirmed that I am calling the 64-bit MKL version.
LinearAlgebra.BlasInt = Int64, but MklInt remains Int32.
The issue seems to come from Pardiso.jl, where the following condition is checked:
if LinearAlgebra.BLAS.vendor() === :mkl && LinearAlgebra.BlasInt == Int64
However, due to a version change, LinearAlgebra.BLAS.vendor() is now returning :lbt instead of :mkl, even though I am using MKL with 64-bit support.
Attempted Fixes:
I tried manually overriding this by commenting out the above check in Pardiso.jl and defining:
const MklInt = Int64
const PARDISO_FUNC = :pardiso_64
Unfortunately, I still encountered the following error:
[2362860] signal (11.1): Segmentation fault
Request for Help
Is there a correct way to enforce Pardiso64 in Pardiso.jl?
How should I properly handle MklInt to ensure compatibility with large sparse matrices?
Could the segmentation fault be caused by incorrect linking, memory issues, or an internal bug in Pardiso.jl?
Any guidance or suggestions would be greatly appreciated!
The text was updated successfully, but these errors were encountered: