-
Notifications
You must be signed in to change notification settings - Fork 631
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
ULMAT/UGLMAT not working for indefinite matrices with latest oneAPI 2025 MKL #13784
Comments
I ran the test case with the latest ifx (2025.0.1) and MKL (2025.0.1) on Windows, and the results are the same. It still does not work. |
Ok, turns out the issue is related to small matrices. If you switch the size of the grid to 18,16,16 is should run fine. |
This is a standalone code to reproduce the issue. The issue was posted in the intel MKL Forum here: |
From the response from Fengrui in the Intel forum, seems a change in default parameter took place when moving from mkl 2024.2 to 2025. I changed the code accordingly in PR #13810. I also changed the startup file of firebot in spark to load mkl/latest. We'll see tonight if this issue is sorted. |
closing this, the verification tests are working correctly. |
In spark load the latest compiler, mpi and mkl modules, compile the impi_intel_linux_db target and run this case:
The Poisson matrix for this problem is symmetric indefinite. Both with ULMAT and UGLMAT we are getting H=0 as solution regardless of what the Poisson RHS is.
Now unload mkl/latest and load mkl/2024.2, recompile the impi_intel_linux_db target and run the case. The solution for H is correct.
Interfaces to PARDISO or SPARSE_CLUSTER_SOLVER have not changed, and VERBOSE metrics for matrix factorization are identical.
I opened a thread in the Intel MKL forum asking about any parameter changes that might be related to this (https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Change-in-behavior-of-Pardiso-and-Sparse-Cluster-Solver-for/m-p/1644570#M36659).
Next I'll setup a standalone test of the solver.
The text was updated successfully, but these errors were encountered: