hidden text to trigger early load of fonts ПродукцияПродукцияПродукцияПродукция Các sản phẩmCác sản phẩmCác sản phẩmCác sản phẩm المنتجاتالمنتجاتالمنتجاتالمنتجات מוצריםמוצריםמוצריםמוצרים
Intel® oneAPI Math Kernel Library
Ask questions and share information with other developers who use Intel® Math Kernel Library.
7154 Discussions

Pardiso bunch-kaufman pivoting option 3 different in MKL 2025.0.1

StefanV1
Beginner
498 Views
When using PARDISO with iparm[20]=3, behavior has changed between MKL 2024.2 and 2025.0. It seems that it does not perform the solve step anymore. With 2024.2, the log said ``` Times: ====== Time spent in direct solver at solve step (solve) : 0.000027 s Time spent in additional calculations : 0.000005 s Total time spent : 0.000032 s ``` Now the line "Time spent in direct solver at solve step (solve)" disappeared and the returned solution is different. (https://github.com/coin-or/Ipopt/issues/799) Is this a know issue? Is this a feature or bug?
0 Kudos
1 Solution
Ruqiu_C_Intel
Moderator
352 Views

Thanks to Stefan for letting us know that this is not a serious issue.

We will fix it in a future release.


View solution in original post

0 Kudos
3 Replies
Ruqiu_C_Intel
Moderator
444 Views

Hi Stefan,


Thank you for posting the issue.

We can reproduce it on our side. If you set iparm[20]=0 or 1, the disappeared message will reappear.

May I ask what is the typical value of max_iterref_steps in your application? Also could you tell us how important is this issue to your project? Does this issue hinder your work? 


Best regards,

Ruqiu




0 Kudos
StefanV1
Beginner
418 Views

iparm[7] (max_iterref_steps) is currently set to 1 by default. Having iparm[20]=3 and iparm[7]=2 (the default) or iparm[7]=10 does not work. But setting iparm[20]=3 and iparm[7]=0 seems to work.

 

Since we have workarounds (iparm[20]=0 or 1, iparm[7]=0, or using an older MKL), this issue is not a serious blocker.

0 Kudos
Ruqiu_C_Intel
Moderator
353 Views

Thanks to Stefan for letting us know that this is not a serious issue.

We will fix it in a future release.


0 Kudos
Reply