<?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_64 with extended eigensolver in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/pardiso-64-with-extended-eigensolver/m-p/1115948#M24643</link>
    <description>&lt;P&gt;Can you use pardiso_64 with the extended eigensolver?&lt;/P&gt;</description>
    <pubDate>Sun, 20 Dec 2015 20:48:33 GMT</pubDate>
    <dc:creator>rick_l_</dc:creator>
    <dc:date>2015-12-20T20:48:33Z</dc:date>
    <item>
      <title>pardiso_64 with extended eigensolver</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/pardiso-64-with-extended-eigensolver/m-p/1115948#M24643</link>
      <description>&lt;P&gt;Can you use pardiso_64 with the extended eigensolver?&lt;/P&gt;</description>
      <pubDate>Sun, 20 Dec 2015 20:48:33 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/pardiso-64-with-extended-eigensolver/m-p/1115948#M24643</guid>
      <dc:creator>rick_l_</dc:creator>
      <dc:date>2015-12-20T20:48:33Z</dc:date>
    </item>
    <item>
      <title>Hi Rick, </title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/pardiso-64-with-extended-eigensolver/m-p/1115949#M24644</link>
      <description>&lt;P&gt;Hi Rick,&amp;nbsp;&lt;/P&gt;

&lt;P&gt;The Extended Eigensolver functionality in Intel Math Kernel Library (Intel MKL) is based on the FEAST&amp;nbsp;Eigenvalue Solver 2.0. And it can use&amp;nbsp;the Intel&amp;nbsp;MKL PARDISO solver internally or together. &amp;nbsp;&lt;SPAN style="font-size: 13.008px; line-height: 19.512px;"&gt;pardiso_64 is 64 bit integer version of pardiso , so you can usr pardiso_64. &amp;nbsp;is there some background info for your question?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 13.008px; line-height: 19.512px;"&gt;some explanation in MKL manual for your reference:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;How you achieve parallelism in Extended Eigensolver routines depends on which interface you use.&lt;BR /&gt;
	Parallelism (via shared memory programming) is not explicitlyimplemented in Extended Eigensolver routines&lt;BR /&gt;
	within one node: the inner linear systems are currently solved one after another.&lt;/P&gt;

&lt;P&gt;Using the predefined Extended Eigensolver interfaces, parallelism can be implicitly obtained within the&lt;BR /&gt;
	shared memory version of BLAS, LAPACK or Intel MKL PARDISO. The shell variable MKL_NUM_THREADScan&lt;BR /&gt;
	be used for automatically setting the number of OpenMP threads (cores) for BLAS, LAPACK, and Intel MKL&lt;BR /&gt;
	PARDISO.&lt;/P&gt;

&lt;P&gt;And t&lt;SPAN style="font-size: 13.008px; line-height: 19.512px;"&gt;here is example code in MKL install directory,&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;&lt;SPAN style="font-size: 13.008px; line-height: 19.512px;"&gt;for example, windows:&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN style="font-size: 1em; line-height: 1.5;"&gt;C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2016.1.146\windows\mkl\examples&lt;/SPAN&gt;&lt;/P&gt;

&lt;P&gt;MKLexample\solvers_eec\source\dexample_sparse_rci_c.c&lt;/P&gt;

&lt;P&gt;Best Regards,&lt;/P&gt;

&lt;P&gt;Ying&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2015 01:24:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/pardiso-64-with-extended-eigensolver/m-p/1115949#M24644</guid>
      <dc:creator>Ying_H_Intel</dc:creator>
      <dc:date>2015-12-21T01:24:16Z</dc:date>
    </item>
    <item>
      <title>My problem would be the</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/pardiso-64-with-extended-eigensolver/m-p/1115950#M24645</link>
      <description>&lt;P&gt;My problem would be the solution of large eigenproblems (&amp;gt; 32 bit limit), where 8 byte integers are necessary.&amp;nbsp; The calls to the extended eigensolver would have to include 8 byte integers.&amp;nbsp; This would mean that pardiso_64 would have to be used.&amp;nbsp; Would this be done through the RCI's&lt;/P&gt;

&lt;P&gt;Rick.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Dec 2015 13:22:51 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/pardiso-64-with-extended-eigensolver/m-p/1115950#M24645</guid>
      <dc:creator>rick_l_</dc:creator>
      <dc:date>2015-12-21T13:22:51Z</dc:date>
    </item>
    <item>
      <title>Hi Rick,</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/pardiso-64-with-extended-eigensolver/m-p/1115951#M24646</link>
      <description>&lt;P&gt;Hi Rick,&lt;/P&gt;
&lt;P&gt;Yes, you can use the pardiso_64 instead of pardiso.(just please make sure all long long related input paramters is 64bit).&lt;/P&gt;
&lt;P&gt;Actually, MKL support LP64 and ILP64 for all routines (including pardiso and extend eign solver). When you have large array, you can link ILP64, which support 64bit integer directly.&lt;/P&gt;
&lt;P&gt;The pardiso_64&amp;nbsp;was used in speical case while&amp;nbsp;you have to &amp;nbsp;link LP64 library (it support 32bit integer), as the same time, hope to use 64bit integer as pardiso&amp;nbsp;input.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Ying&lt;/P&gt;</description>
      <pubDate>Wed, 23 Dec 2015 02:52:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/pardiso-64-with-extended-eigensolver/m-p/1115951#M24646</guid>
      <dc:creator>Ying_H_Intel</dc:creator>
      <dc:date>2015-12-23T02:52:00Z</dc:date>
    </item>
  </channel>
</rss>

