<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Pardiso regression in 2025.1.0 in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-regression-in-2025-1-0/m-p/1688173#M37125</link>
    <description>&lt;P&gt;Thanks for the update, that's great to hear! Looking forward to the next release.&lt;/P&gt;</description>
    <pubDate>Wed, 07 May 2025 15:06:20 GMT</pubDate>
    <dc:creator>urob</dc:creator>
    <dc:date>2025-05-07T15:06:20Z</dc:date>
    <item>
      <title>Pardiso regression in 2025.1.0</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-regression-in-2025-1-0/m-p/1685490#M37091</link>
      <description>&lt;P&gt;After upgrading MKL from 2024.2.2 to 2025.1.0 the Pardiso solver produces incorrect results for a variety of problems.&lt;/P&gt;&lt;P&gt;I am attaching a reproducer matrix &lt;FONT face="courier new,courier"&gt;A.txt&lt;/FONT&gt; and vector &lt;FONT face="courier new,courier"&gt;b.txt&lt;/FONT&gt;. Solving the system with default &lt;FONT face="courier new,courier"&gt;iparms&lt;/FONT&gt; in 2024.2.2 produces a solution &lt;FONT face="courier new,courier"&gt;&lt;STRONG&gt;x&lt;/STRONG&gt;&lt;/FONT&gt; such that &lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;Ax - b&lt;/FONT&gt;&lt;/STRONG&gt; is indeed numerically zero.&lt;/P&gt;&lt;P&gt;Solving the same system in 2025.1.0 produces solutions for which &lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;Ax - b&lt;/FONT&gt;&lt;/STRONG&gt; is clearly non-zero (with values ranging into the thousands). This is true for the default &lt;FONT face="courier new,courier"&gt;iparms&lt;/FONT&gt; and any alternative I tried.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 25 Apr 2025 15:55:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-regression-in-2025-1-0/m-p/1685490#M37091</guid>
      <dc:creator>urob</dc:creator>
      <dc:date>2025-04-25T15:55:05Z</dc:date>
    </item>
    <item>
      <title>Re: Pardiso regression in 2025.1.0</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-regression-in-2025-1-0/m-p/1685975#M37094</link>
      <description>&lt;P&gt;&lt;FONT size="3"&gt;Hi,&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;Thank you for reporting this bug. We have successfully reproduced it and are currently working to identify the root cause. In the meantime, we have two workarounds:&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;1) Use the new factorization algorithm, i.e.,&amp;nbsp; set iparm[23]=1. Additionally, ensure that matching and scaling are disabled by setting iparm[10]=0 and iparm[12]=0.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;2) Use default factorization algorithm, i.e., set iparm[23]=0, and execute phase 1 in a serial manner using only one thread.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;Attached, you will find a reproducer and the two workarounds mentioned above. Please let us know if these solutions are effective for you.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;We will provide updates as soon as we identify the issue and have a confirmed date for the bug fix.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;Thank you once again for reporting.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;Kind Regards,&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;Chris&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Apr 2025 12:10:52 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-regression-in-2025-1-0/m-p/1685975#M37094</guid>
      <dc:creator>c_sim</dc:creator>
      <dc:date>2025-04-28T12:10:52Z</dc:date>
    </item>
    <item>
      <title>Re: Pardiso regression in 2025.1.0</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-regression-in-2025-1-0/m-p/1686016#M37095</link>
      <description>&lt;P&gt;Thanks Chris for reproducing and providing the workarounds! I can confirm that both workarounds are effective. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One minor observation about workaround 1: While the solutions are numerically correct, they are a few orders of magnitude less accurate than the default options under 2024.2.2 (residuals of the order 1e-8 as opposed to 1e-19). Setting &lt;FONT face="courier new,courier"&gt;iparms[12] = 1&lt;/FONT&gt; as suggested in the code comment does not help, because that induces Pardiso to use the classic factorization algorithm regardless of the value chosen for &lt;FONT face="courier new,courier"&gt;iparms[23]&lt;/FONT&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks again for looking into this&lt;/P&gt;</description>
      <pubDate>Mon, 28 Apr 2025 15:01:09 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-regression-in-2025-1-0/m-p/1686016#M37095</guid>
      <dc:creator>urob</dc:creator>
      <dc:date>2025-04-28T15:01:09Z</dc:date>
    </item>
    <item>
      <title>Re: Pardiso regression in 2025.1.0</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-regression-in-2025-1-0/m-p/1688110#M37121</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have identified the issue, and a fix will be included in the next release of Intel oneMKL.&lt;/P&gt;&lt;P&gt;To answer your previous question: As you noted, enabling scaling or matching (iparm[10]=1 and/or iparm[12]=1) will make PARDISO to select the classic factorization path, where this bug is present. Therefore, if you need to enable these features, currently only workaround 2 would be the option.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for bringing this up.&lt;/P&gt;&lt;P&gt;Kind Regards,&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;</description>
      <pubDate>Wed, 07 May 2025 09:30:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-regression-in-2025-1-0/m-p/1688110#M37121</guid>
      <dc:creator>c_sim</dc:creator>
      <dc:date>2025-05-07T09:30:32Z</dc:date>
    </item>
    <item>
      <title>Re: Pardiso regression in 2025.1.0</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-regression-in-2025-1-0/m-p/1688173#M37125</link>
      <description>&lt;P&gt;Thanks for the update, that's great to hear! Looking forward to the next release.&lt;/P&gt;</description>
      <pubDate>Wed, 07 May 2025 15:06:20 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Pardiso-regression-in-2025-1-0/m-p/1688173#M37125</guid>
      <dc:creator>urob</dc:creator>
      <dc:date>2025-05-07T15:06:20Z</dc:date>
    </item>
  </channel>
</rss>

