Re: [Numpy-discussion] NumPy-Discussion OpenBLAS and dotblas
Hi. I am working on numpy in pypy. It would be much more challenging for me if you merged more code into the core of numpy, that means even more must be duplicated when using a different underlying ndarray implementation. If you are thinking of touching linalg/lapack_lite/blas_lite, I would prefer a simpler model that uses ndarray as a simple storage container, does not use cpython-specifc capi extentions with reference counting, and interfaces with python via cffi[0]. Matti [0] https://pypi.python.org/pypi/cffi/ On 8/08/2014 8:00 PM, numpy-discussion-request@scipy.org wrote:
Message: 1 Date: Thu, 7 Aug 2014 20:32:21 -0600 From: Charles R Harris <charlesr.harris@gmail.com> Subject: [Numpy-discussion] OpenBLAS and dotblas To: numpy-discussion <numpy-discussion@scipy.org> Message-ID: <CAB6mnxJOON2tn2-YP8wsBwyqRhNOQEe715Tek6rGGOVTuazyFw@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
Hi All,
It looks like numpy dot only uses BLAS if ATLAS is present, see numpy/core/setup.py. Has anyone done the mods needed to use OpenBLAS? What is the current status of using OpenBLAS with numpy?
Also, I'm thinking of moving linalg/lapack_lite/blas_lite.c down into the core. Thoughts?
Chuck
On Sat, Aug 9, 2014 at 8:35 PM, Matti Picus <matti.picus@gmail.com> wrote:
Hi. I am working on numpy in pypy. It would be much more challenging for me if you merged more code into the core of numpy,
Hi Matti, I can definitely see how numpy changes cause trouble for you, and sympathize. But, can you elaborate on what kind of changes would make your life easier *that also* help make numpy proper better in their own right? Because unfortunately, I don't see how we can reasonably pass up on improvements to numpy if the only justification is to make numpypy's life easier. (I'd also love to see pypy become usable for general numerical work, but not only is it not there now, I don't see how numpypy will ultimately get us there even if we do help it along -- almost none of the ecosystem can get by numpy's python-level APIs alone.) But obviously if there are changes that are mutually beneficial, well then, that's a lot easier to justify :-) -n -- Nathaniel J. Smith Postdoctoral researcher - Informatics - University of Edinburgh http://vorpus.org
On Sat, Aug 9, 2014 at 1:35 PM, Matti Picus <matti.picus@gmail.com> wrote:
Hi. I am working on numpy in pypy. It would be much more challenging for me if you merged more code into the core of numpy, that means even more must be duplicated when using a different underlying ndarray implementation. If you are thinking of touching linalg/lapack_lite/blas_lite, I would prefer a simpler model that uses ndarray as a simple storage container, does not use cpython-specifc capi extentions with reference counting, and interfaces with python via cffi[0]. Matti
Could you be more specific? Numpy is pretty tightly bound to the cpython interface, changing that would require a fundamental rethink/redesign/redo <snip> Chuck
participants (3)
-
Charles R Harris -
Matti Picus -
Nathaniel Smith