<?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 PARDISO with METIS re-ordering in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PARDISO-with-METIS-re-ordering/m-p/959484#M15786</link>
    <description>&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Hello:&lt;/P&gt;
&lt;P&gt;I am using (INTEL_MKL) PARDISO solver in a visco-elasto-plastic Stokes flow code. It is a finite difference code which uses marker-in-cell technique and has a mixed formulation with linear velocity and constant pressure.&lt;BR /&gt;&lt;BR /&gt;During the reordering and symbolic factorization (METIS) I keep getting SEG-faults (and occasionally a SIGBUS) at random moments, where it will probably runs through the next time. This occurs both when using METIS = 3 or 2, however it runs fine without re-ordering.&lt;/P&gt;
&lt;P&gt;I have checked the physics, matrix conditioning etc. but the fact that solver only has a problem with longer runs, whereas it runs fine with the restart file, suggests that there is some algorithmic/compiler specific issue. I have traced the memory utilization and it is far less than the RAM.&lt;/P&gt;
&lt;P&gt;This seems to be the problem with the INTEL_MKL version of Pardiso only.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Rooh&lt;/P&gt;</description>
    <pubDate>Sun, 03 Mar 2013 09:07:27 GMT</pubDate>
    <dc:creator>Rooh</dc:creator>
    <dc:date>2013-03-03T09:07:27Z</dc:date>
    <item>
      <title>PARDISO with METIS re-ordering</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PARDISO-with-METIS-re-ordering/m-p/959484#M15786</link>
      <description>&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Hello:&lt;/P&gt;
&lt;P&gt;I am using (INTEL_MKL) PARDISO solver in a visco-elasto-plastic Stokes flow code. It is a finite difference code which uses marker-in-cell technique and has a mixed formulation with linear velocity and constant pressure.&lt;BR /&gt;&lt;BR /&gt;During the reordering and symbolic factorization (METIS) I keep getting SEG-faults (and occasionally a SIGBUS) at random moments, where it will probably runs through the next time. This occurs both when using METIS = 3 or 2, however it runs fine without re-ordering.&lt;/P&gt;
&lt;P&gt;I have checked the physics, matrix conditioning etc. but the fact that solver only has a problem with longer runs, whereas it runs fine with the restart file, suggests that there is some algorithmic/compiler specific issue. I have traced the memory utilization and it is far less than the RAM.&lt;/P&gt;
&lt;P&gt;This seems to be the problem with the INTEL_MKL version of Pardiso only.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Rooh&lt;/P&gt;</description>
      <pubDate>Sun, 03 Mar 2013 09:07:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PARDISO-with-METIS-re-ordering/m-p/959484#M15786</guid>
      <dc:creator>Rooh</dc:creator>
      <dc:date>2013-03-03T09:07:27Z</dc:date>
    </item>
    <item>
      <title>Hello Rooh. </title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PARDISO-with-METIS-re-ordering/m-p/959485#M15787</link>
      <description>&lt;P&gt;Hello Rooh.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What would happens if you will use the minimum degree algorithm?&lt;/P&gt;</description>
      <pubDate>Sun, 03 Mar 2013 13:31:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PARDISO-with-METIS-re-ordering/m-p/959485#M15787</guid>
      <dc:creator>Gennady_F_Intel</dc:creator>
      <dc:date>2013-03-03T13:31:16Z</dc:date>
    </item>
    <item>
      <title>Hi Gennady,</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PARDISO-with-METIS-re-ordering/m-p/959486#M15788</link>
      <description>&lt;P&gt;Hi Gennady,&lt;/P&gt;
&lt;P&gt;It works fine with&amp;nbsp;minimum degree algorithm (iparm[1] = 0), but much slower than iparm[1] = 2 or 3&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Rooh&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2013 13:57:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PARDISO-with-METIS-re-ordering/m-p/959486#M15788</guid>
      <dc:creator>Rooh</dc:creator>
      <dc:date>2013-03-04T13:57:16Z</dc:date>
    </item>
    <item>
      <title>Hi Rooh,</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PARDISO-with-METIS-re-ordering/m-p/959487#M15789</link>
      <description>&lt;P&gt;Hi Rooh,&lt;/P&gt;
&lt;P&gt;We had the problem with metis reodering in the past. what version of mkl you are using? in the case of the latest ( v.11.0 update 2), then please give us the reproducer of this problem.&lt;/P&gt;
&lt;P&gt;--Gennady&lt;/P&gt;</description>
      <pubDate>Mon, 04 Mar 2013 15:07:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/PARDISO-with-METIS-re-ordering/m-p/959487#M15789</guid>
      <dc:creator>Gennady_F_Intel</dc:creator>
      <dc:date>2013-03-04T15:07:02Z</dc:date>
    </item>
  </channel>
</rss>

