<?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 Anaconda MKL and threading on macOS in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Anaconda-MKL-and-threading-on-macOS/m-p/1169990#M28503</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am not sure if this is the correct forum for this, so bear with me!&lt;/P&gt;&lt;P&gt;I am using MKL (2019.1) installed via Miniconda (4.6.8) on macOS (10.14.2). The open source code I develop (gprMax -&amp;nbsp;&lt;A href="https://github.com/gprMax/gprMax"&gt;https://github.com/gprMax/gprMax&lt;/A&gt;) is written in Python, uses NumPy, and has modules that are Cythonized and use OpenMP. The conda environment that I use is relatively simple -&amp;nbsp;&lt;A href="https://github.com/gprMax/gprMax/blob/master/conda_env.yml"&gt;https://github.com/gprMax/gprMax/blob/master/conda_env.yml&lt;/A&gt;&amp;nbsp;On Linux and Windows the simulation software behaves normally, however, on macOS the simulations become unstable. This has only started happening recently when I updated the conda environment. Interestingly, if I set the simulation to use a single thread on macOS it behaves normally and is stable. Also if I use OpenBLAS instead of MKL, by specifying&amp;nbsp;blas=*=openblas&amp;nbsp;in my conda environment file, I have no problems with stability and using multiple threads.&lt;/P&gt;&lt;P&gt;I am interested to know if anyone else has experience similar problems, and also how I might further debug the issue.&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;</description>
    <pubDate>Thu, 14 Mar 2019 17:29:21 GMT</pubDate>
    <dc:creator>Craig_Warren</dc:creator>
    <dc:date>2019-03-14T17:29:21Z</dc:date>
    <item>
      <title>Anaconda MKL and threading on macOS</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Anaconda-MKL-and-threading-on-macOS/m-p/1169990#M28503</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am not sure if this is the correct forum for this, so bear with me!&lt;/P&gt;&lt;P&gt;I am using MKL (2019.1) installed via Miniconda (4.6.8) on macOS (10.14.2). The open source code I develop (gprMax -&amp;nbsp;&lt;A href="https://github.com/gprMax/gprMax"&gt;https://github.com/gprMax/gprMax&lt;/A&gt;) is written in Python, uses NumPy, and has modules that are Cythonized and use OpenMP. The conda environment that I use is relatively simple -&amp;nbsp;&lt;A href="https://github.com/gprMax/gprMax/blob/master/conda_env.yml"&gt;https://github.com/gprMax/gprMax/blob/master/conda_env.yml&lt;/A&gt;&amp;nbsp;On Linux and Windows the simulation software behaves normally, however, on macOS the simulations become unstable. This has only started happening recently when I updated the conda environment. Interestingly, if I set the simulation to use a single thread on macOS it behaves normally and is stable. Also if I use OpenBLAS instead of MKL, by specifying&amp;nbsp;blas=*=openblas&amp;nbsp;in my conda environment file, I have no problems with stability and using multiple threads.&lt;/P&gt;&lt;P&gt;I am interested to know if anyone else has experience similar problems, and also how I might further debug the issue.&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;</description>
      <pubDate>Thu, 14 Mar 2019 17:29:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Anaconda-MKL-and-threading-on-macOS/m-p/1169990#M28503</guid>
      <dc:creator>Craig_Warren</dc:creator>
      <dc:date>2019-03-14T17:29:21Z</dc:date>
    </item>
    <item>
      <title>So a workaround seems to be</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Anaconda-MKL-and-threading-on-macOS/m-p/1169991#M28504</link>
      <description>&lt;P&gt;So a workaround seems to be setting&amp;nbsp;MKL_THREADING_LAYER=sequential before launching Python. Setting it within the Python application does not work, as I assume it is only being applied to child processes, and whatever module is using MKL has already been loaded.&lt;/P&gt;&lt;P&gt;Craig&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2019 09:55:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Anaconda-MKL-and-threading-on-macOS/m-p/1169991#M28504</guid>
      <dc:creator>Craig_Warren</dc:creator>
      <dc:date>2019-03-15T09:55:32Z</dc:date>
    </item>
  </channel>
</rss>

