Rather than keeping the number of threads MKL uses to 1, it is better to use
MKL_THREADING_LAYER=SEQUENTIAL
https://software.intel.com/en-us/node/528380
--Sasha
From: NumPy-Discussion
[mailto:numpy-discussion-bounces+oleksandr.pavlyk=intel@python.org] On
Behalf Of Neal Becker
Sent: Friday
On 03/23/2017 02:16 PM, Kirill Balunov wrote:
> It was the first time I tried to create a structured array in numpy.
> Usually I use pandas for heterogeneous arrays, but it is one more
> dependency to my project.
>
> It took me some time (really, much more than some), to understand the
> problem w
Hi Kirill,
T
he idea is that each tuple assigns a name to the field and a data type.
There are a variety of ways to create structured arrays but they all
involve giving both a name and data type to each field (I think). See
https://docs.scipy.org/doc/numpy/user/basics.rec.html
Jon
On Fri, M
Ah, that probably explains it!
On Fri, Mar 24, 2017 at 7:37 AM Daπid wrote:
> On 24 March 2017 at 12:30, Neal Becker wrote:
> > Using os.environ doesn't
> > work. I don't understand why.
>
> It should, I do that for other variables. Are you setting the
> variables before importing other librar
On 24 March 2017 at 12:30, Neal Becker wrote:
> Using os.environ doesn't
> work. I don't understand why.
It should, I do that for other variables. Are you setting the
variables before importing other libraries? They may only get read at
import time.
__
I don't want my python code to run multi-thread. So I can do:
MKL_NUM_THREAD=1 NUMEXPR_NUM_THREADS=1 OMP_NUM_THREADS=1 my_program...
But I don't seem to be able to achieve this effect without setting env
variables on the command line; within my_program. Using os.environ doesn't
work. I don't u
Hi all,
This mailing list moved, it's now numpy-discussion@python.org.
Please update the stored address in the contacts list of your email client
- messages sent to @scipy.org will not arrive anymore.
Cheers,
Ralf
___
NumPy-Discussion mailing list
NumP
