Re: [Numpy-discussion] Numpy 1.12.x branched

My change about numpy.mean in float16 aren't in the doc. Should I make a PR again numpy master or maintenance/1.12.x? Fred On Mon, Nov 7, 2016 at 2:59 PM, Charles R Harris wrote: > > > On Mon, Nov 7, 2016 at 11:32 AM, Matti Picus > wrote: >

[Numpy-discussion] Announcing Theano 0.8.0

Announcing Theano 0.8.0 This is a release for a major version, with lots of new features, bug fixes, and some interface changes (deprecated or potentially misleading features were removed). The upgrade is recommended for everybody. For those

Re: [Numpy-discussion] ANN: NumPy 1.8.2 release candidate

All Theano tests work. thanks! Fred On Tue, Aug 5, 2014 at 8:46 PM, Matthew Brett matthew.br...@gmail.com wrote: Hi, On Tue, Aug 5, 2014 at 2:27 PM, Matthew Brett matthew.br...@gmail.com wrote: Hi, On Tue, Aug 5, 2014 at 1:57 PM, Julian Taylor jtaylor.deb...@googlemail.com wrote:

Re: [Numpy-discussion] numpy.mean still broken for large float32 arrays

On Thu, Jul 24, 2014 at 12:59 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Thu, Jul 24, 2014 at 8:27 AM, Jaime Fernández del Río jaime.f...@gmail.com wrote: On Thu, Jul 24, 2014 at 4:56 AM, Julian Taylor jtaylor.deb...@googlemail.com wrote: In practice one of the better

Re: [Numpy-discussion] Reporting a bug to Apple.

. Frédéric Bastien On Mon, Jun 9, 2014 at 7:29 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, Julian has tracked down a bug in the Accelerate library in Maverick, details here https://github.com/numpy/numpy/issues/4007#issuecomment-45541678. Is there a registered Apple Developer

Re: [Numpy-discussion] IDL vs Python parallel computing

Just a quick question/possibility. What about just parallelizing ufunc with only 1 inputs that is c or fortran contiguous like trigonometric function? Is there a fast path in the ufunc mechanism when the input is fortran/c contig? If that is the case, it would be relatively easy to add an openmp

Re: [Numpy-discussion] GSoC project: draft of proposal

Just a comment, supporting a library that is bsd 3 clauses could help to higly reduce the compilation problem like what we have with blas. We could just include it in numpy/download it automatically or whatever to make the install trivial and then we could suppose all users have it. Deadling with

Re: [Numpy-discussion] It looks like Py 3.5 will include a dedicated infix matrix multiply operator

This is great news. Excellent work Nathaniel and all others! Frédéric On Fri, Mar 14, 2014 at 8:57 PM, Aron Ahmadia a...@ahmadia.net wrote: That's the best news I've had all week. Thanks for all your work on this Nathan. -A On Fri, Mar 14, 2014 at 8:51 PM, Nathaniel Smith n...@pobox.com

Re: [Numpy-discussion] 1.8.1 release

Hi, I have a PR that fix way too much printing to stdout when finding the blas linking information: https://github.com/numpy/numpy/pull/4081 This was created by change in NumPy. I was requested as a comment to put the removed information in the dict that we return to the user. I won't have the

Re: [Numpy-discussion] 1.8.1 release

Hi, Arnaud finished that in a different way then we had discussed in the PR. https://github.com/numpy/numpy/pull/4081 Fred On Wed, Feb 26, 2014 at 10:07 AM, Frédéric Bastien no...@nouiz.org wrote: Hi, I have a PR that fix way too much printing to stdout when finding the blas linking

[Numpy-discussion] Suggestion: Port Theano RNG implementation to NumPy

Hi, In a ticket I did a coment and Charles suggested that I post it here: In Theano we have an C implementation of a faster RNG: MRG31k3p. It is faster on CPU, and we have a GPU implementation. It would be relatively easy to parallize on the CPU with OpenMP. If someone is interested to port

Re: [Numpy-discussion] Suggestion: Port Theano RNG implementation to NumPy

of choice for numerical work. And when we are doing stochastic simulations in Python, the speed of the PRNG is unlikely to be the bottleneck. Sturla Frédéric Bastien no...@nouiz.org wrote: Hi, In a ticket I did a coment and Charles suggested that I post it here: In Theano we have an C

Re: [Numpy-discussion] MKL and OpenBLAS

On Fri, Feb 7, 2014 at 4:31 AM, Robert Kern robert.k...@gmail.com wrote: On Thu, Feb 6, 2014 at 9:45 PM, Matthieu Brucher matthieu.bruc...@gmail.com wrote: According to the discussions on the ML, they switched from GPL to MPL to enable the kind of distribution numpy/scipy is looking for. They

Re: [Numpy-discussion] windows and C99 math

Just a guess as I don't make those binaries, but I think they are done with Visual Studio and it only support C89... We need to back port some of our c code for windows for GPU as nvcc use VS and it don't support C99. Fred On Mon, Jan 27, 2014 at 3:04 PM, Julian Taylor

Re: [Numpy-discussion] Memory allocation cleanup

On Fri, Jan 10, 2014 at 4:18 AM, Julian Taylor jtaylor.deb...@googlemail.com wrote: On Fri, Jan 10, 2014 at 3:48 AM, Nathaniel Smith n...@pobox.com wrote: On Thu, Jan 9, 2014 at 11:21 PM, Charles R Harris charlesr.har...@gmail.com wrote: [...] After a bit more research, some further points

Re: [Numpy-discussion] adding fused multiply and add to numpy

Hi, It happen frequently that NumPy isn't compiled with all instruction that is available where it run. For example in distro. So if the decision is made to use the fast version when we don't use the newer instruction, the user need a way to know that. So the library need a function/attribute to

Re: [Numpy-discussion] Memory allocation cleanup

This shouldn't affect Theano. So I have no objection. Making thing faster and more tracktable is always good. So I think it seam a good idea. Fred On Thu, Jan 9, 2014 at 6:21 PM, Charles R Harris charlesr.har...@gmail.com wrote: Apropos Julian's changes to use the PyObject_* allocation suite

Re: [Numpy-discussion] adding fused multiply and add to numpy

parameter? Fred On Thu, Jan 9, 2014 at 12:07 PM, Nathaniel Smith n...@pobox.com wrote: On Thu, Jan 9, 2014 at 3:30 PM, Julian Taylor jtaylor.deb...@googlemail.com wrote: On Thu, Jan 9, 2014 at 3:50 PM, Frédéric Bastien no...@nouiz.org wrote: How hard would it be to provide the choise

Re: [Numpy-discussion] Speedup by avoiding memory alloc twice in scalar array

from doing that anyway I think. Do we need to wait until we completly remove the old interface for this? Fred On Wed, Jan 8, 2014 at 1:13 PM, Julian Taylor jtaylor.deb...@googlemail.com wrote: On 18.07.2013 15:36, Nathaniel Smith wrote: On Wed, Jul 17, 2013 at 5:57 PM, Frédéric Bastien

Re: [Numpy-discussion] Speedup by avoiding memory alloc twice in scalar array

On Wed, Jan 8, 2014 at 3:40 PM, Nathaniel Smith n...@pobox.com wrote: On Wed, Jan 8, 2014 at 12:13 PM, Julian Taylor jtaylor.deb...@googlemail.com wrote: On 18.07.2013 15:36, Nathaniel Smith wrote: On Wed, Jul 17, 2013 at 5:57 PM, Frédéric Bastien no...@nouiz.org wrote: On the usefulness

[Numpy-discussion] Theano 0.6 released

What's New -- We recommend that everybody update to this version. Highlights (since 0.6rc5): * Last release with support for Python 2.4 and 2.5. * We will try to release more frequently. * Fix crash/installation problems. * Use less memory for conv3d2d. 0.6rc4 skipped for a

Re: [Numpy-discussion] nasty bug in 1.8.0??

It is the NPY_RELAXED_STRIDES_CHECKING=1 flag that caused this. Fred On Mon, Dec 2, 2013 at 2:18 PM, Neal Becker ndbeck...@gmail.com wrote: I built using: CFLAGS='-march=native -O3' NPY_RELAXED_STRIDES_CHECKING=1 python3 setup.py install --user aπid wrote: I get: In [4]: x.strides

Re: [Numpy-discussion] nasty bug in 1.8.0??

There is a way to compile NumPy to use strange strides for dimension with shape of 1. This is done to help developer test their code to don't rely on this. There was never a warranty to the value of strides in that cases. Most of the time, it was the same, but in some cases, it was different.

Re: [Numpy-discussion] nasty bug in 1.8.0??

for it. But this help test your software to don't depend of the strides when shapes is 1. On Mon, Dec 2, 2013 at 2:35 PM, Neal Becker ndbeck...@gmail.com wrote: I don't think that behavior is acceptable. Frédéric Bastien wrote: It is the NPY_RELAXED_STRIDES_CHECKING=1 flag that caused this. Fred On Mon

Re: [Numpy-discussion] Silencing NumPy output

/lib64/atlas'] language = f77 define_macros = [('ATLAS_INFO', '\\3.8.3\\')] include_dirs = ['/usr/include'] Frédéric On Fri, Nov 22, 2013 at 4:26 PM, Frédéric Bastien no...@nouiz.org wrote: I didn't forgot this, but I got side tracked. Here is the Theano code I would like to try

Re: [Numpy-discussion] MKL + CPU, GPU + cuBLAS comparison

We have such benchmark in Theano: https://github.com/Theano/Theano/blob/master/theano/misc/check_blas.py#L177 HTH Fred On Tue, Nov 26, 2013 at 7:10 AM, Dinesh Vadhia dineshbvad...@hotmail.com wrote: Jerome, Thanks for the swift response and tests. Crikey, that is a significant difference at

Re: [Numpy-discussion] Silencing NumPy output

I didn't forgot this, but I got side tracked. Here is the Theano code I would like to try to use to replace os.system: https://github.com/Theano/Theano/blob/master/theano/misc/windows.py But I won't be able to try this before next week. Fred On Fri, Nov 15, 2013 at 5:49 PM, David Cournapeau

[Numpy-discussion] Silencing NumPy output

Hi, NumPy 1.8 removed the private NumPy interface numpy.distutils.__config__. So a Theano user make a PR to make Theano use the official interface: numpy.distutils.system_info.get_info(blas_opt) But this output many stuff to the output. I can silence part of it by silencing warnings, but I'm

Re: [Numpy-discussion] Silencing NumPy output

charlesr.har...@gmail.com wrote: On Fri, Nov 15, 2013 at 8:12 AM, Frédéric Bastien no...@nouiz.org wrote: Hi, NumPy 1.8 removed the private NumPy interface numpy.distutils.__config__. So a Theano user make a PR to make Theano use the official interface

Re: [Numpy-discussion] Silencing NumPy output

The first line isn't yet removed in my local tests, so maybe more is needed. On Fri, Nov 15, 2013 at 2:28 PM, David Cournapeau courn...@gmail.com wrote: On Fri, Nov 15, 2013 at 6:21 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Fri, Nov 15, 2013 at 11:05 AM, Frédéric Bastien

[Numpy-discussion] How we support new and old NumPy C API.

Hi, With recent version of NumPy, when we compile c code, by default it raise a deprecation warning. To remore it, we must of only the new NumPy C API and define a macro. The new API only exist for NumPy 1.6 and later, so if we want to support older NumPy we need to do more work. As Theano

Re: [Numpy-discussion] Numpy 1.8.0 release

Hi, This is to tell that all Theano tests pass with the branch 1.8.x with the commit 397fdec2a2c thanks Frédéric On Sun, Oct 20, 2013 at 1:35 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, I'm planning on releasing Numpy 1.8.0 next weekend. There have been a few minor fixes

Re: [Numpy-discussion] ANN: 1.8.0b2 release.

charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 11:09 AM, Frédéric Bastien no...@nouiz.orgwrote: I don't have CFLAGS defined. But I have iothers env variable that point to other python stuff like CPATH. But even in that case, I don't understand how other people could have compiled

Re: [Numpy-discussion] ANN: 1.8.0b2 release.

Hi, I checkout the dev version of numpy and it fail to compile with this error: creating build/temp.linux-x86_64-2.7/build/src.linux-x86_64-2.7/numpy/core/src/multiarray compile options: '-DHAVE_NPY_CONFIG_H=1 -Inumpy/core/include -Ibuild/src.linux-x86_64-2.7/numpy/core/include/numpy

Re: [Numpy-discussion] ANN: 1.8.0b2 release.

, but not in the .h file. thanks Fred On Mon, Sep 9, 2013 at 11:44 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 9:33 AM, Frédéric Bastien no...@nouiz.org wrote: I tried it and retried and it still fail. This is in an virtualenv $git show commit

Re: [Numpy-discussion] ANN: 1.8.0b2 release.

charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 8:51 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Mon, Sep 9, 2013 at 7:46 AM, Frédéric Bastien no...@nouiz.org wrote: Hi, I checkout the dev version of numpy and it fail to compile with this error: creating build

Re: [Numpy-discussion] Minimal NumPy for distribution

in practice, but it definitely happens. You don't need .py files if you have .pyc files, and those can be compressed (python can import directly from .zip files). -n On 4 Sep 2013 18:52, Frédéric Bastien no...@nouiz.org wrote: Hi, I have done some exploratory work with Theano to generate a shared

[Numpy-discussion] Minimal NumPy for distribution

Hi, I have done some exploratory work with Theano to generate a shared library from a Theano function. This link with numpy c api. If we want to distribute this library and call it from C and/or python, what is the minimal installed part of NumPy needed? I suppose that only the c api is needed.

Re: [Numpy-discussion] Correct way to query NumPy for linktime BLAS and LAPACK

Hi, In Theano, we use the information in this dictionnary: numpy.distutils.__config__.blas_opt_info. We do this for a few years already, so I don't know how much future proof it is, but I would expect that they aren't going to change this shortly. We use this dict for the default configuration,

Re: [Numpy-discussion] Allow == and != to raise errors

On Thu, Jul 25, 2013 at 7:48 AM, Nathaniel Smith n...@pobox.com wrote: On Tue, Jul 23, 2013 at 4:10 PM, Frédéric Bastien no...@nouiz.org wrote: I'm mixed, because I see the good value, but I'm not able to guess the consequence of the interface change. So doing your FutureWarning would

Re: [Numpy-discussion] Allow == and != to raise errors

I'm mixed, because I see the good value, but I'm not able to guess the consequence of the interface change. So doing your FutureWarning would allow to gatter some data about this, and if it seam to cause too much problem, we could cancel the change. Also, in the case there is a few software that

Re: [Numpy-discussion] Speedup by avoiding memory alloc twice in scalar array

On Wed, Jul 17, 2013 at 10:39 AM, Nathaniel Smith n...@pobox.com wrote: On Tue, Jul 16, 2013 at 7:53 PM, Frédéric Bastien no...@nouiz.org wrote: Hi, On Tue, Jul 16, 2013 at 11:55 AM, Nathaniel Smith n...@pobox.com wrote: On Tue, Jul 16, 2013 at 2:34 PM, Arink Verma arinkve

Re: [Numpy-discussion] Speedup by avoiding memory alloc twice in scalar array

Hi, On Tue, Jul 16, 2013 at 11:55 AM, Nathaniel Smith n...@pobox.com wrote: On Tue, Jul 16, 2013 at 2:34 PM, Arink Verma arinkve...@gmail.com wrote: Each ndarray does two mallocs, for the obj and buffer. These could be combined into 1 - just allocate the total size and do some pointer

Re: [Numpy-discussion] Allow == and != to raise errors

Just a question, should == behave like a ufunc or like python == for tuple? I think that all ndarray comparision (==, !=, =, ...) should behave the same. If they don't (like it was said), making them consistent is good. What is the minimal change to have them behave the same? From my

Re: [Numpy-discussion] Allow == and != to raise errors

I also don't like that idea, but I'm not able to come to a good reasoning like Benjamin. I don't see advantage to this change and the reason isn't good enough to justify breaking the interface I think. But I don't think we rely on this, so if the change goes in, it probably won't break stuff or

Re: [Numpy-discussion] Equality not working as expected with ndarray sub-class

Hi, __array__priority wasn't checked for ==, !=, , =, , = operation. I added it in the development version and someone else back-ported it to the 1.7.X branch. So this will work with the next release of numpy. I don't know of a workaround until the next release. Fred On Thu, Jul 4, 2013 at

Re: [Numpy-discussion] Equality not working as expected with ndarray sub-class

On Thu, Jul 4, 2013 at 9:12 AM, sebastian sebast...@sipsolutions.netwrote: On 2013-07-04 15:06, Thomas Robitaille wrote: Hi everyone, The following example: import numpy as np class SimpleArray(np.ndarray): __array_priority__ = 1 def __new__(cls,

Re: [Numpy-discussion] low level optimization in NumPy and minivect

On Wed, Jun 26, 2013 at 7:30 AM, mark florisson markflorisso...@gmail.comwrote: On 26 June 2013 09:05, Dag Sverre Seljebotn d.s.seljeb...@astro.uio.no wrote: On 06/25/2013 04:21 PM, Frédéric Bastien wrote: Hi, I wasn't able to attend this year Scipy Conference. My tutorial proposal

Re: [Numpy-discussion] low level optimization in NumPy and minivect

...@gmail.com wrote: On Wed, Jun 19, 2013 at 7:48 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Wed, Jun 19, 2013 at 5:45 AM, Matthew Brett matthew.br...@gmail.comwrote: Hi, On Wed, Jun 19, 2013 at 1:43 AM, Frédéric Bastien no...@nouiz.org wrote: Hi, On Mon, Jun 17, 2013

Re: [Numpy-discussion] low level optimization in NumPy and minivect

wrote: On Wed, Jun 19, 2013 at 5:45 AM, Matthew Brett matthew.br...@gmail.comwrote: Hi, On Wed, Jun 19, 2013 at 1:43 AM, Frédéric Bastien no...@nouiz.org wrote: Hi, On Mon, Jun 17, 2013 at 5:03 PM, Julian Taylor jtaylor.deb...@googlemail.com wrote: On 17.06.2013 17:11, Frédéric

Re: [Numpy-discussion] low level optimization in NumPy and minivect

Hi, On Mon, Jun 17, 2013 at 5:03 PM, Julian Taylor jtaylor.deb...@googlemail.com wrote: On 17.06.2013 17:11, Frédéric Bastien wrote: Hi, I saw that recently Julian Taylor is doing many low level optimization like using SSE instruction. I think it is great. Last year, Mark

[Numpy-discussion] low level optimization in NumPy and minivect

Hi, I saw that recently Julian Taylor is doing many low level optimization like using SSE instruction. I think it is great. Last year, Mark Florisson released the minivect[1] project that he worked on during is master thesis. minivect is a compiler for element-wise expression that do some of the

Re: [Numpy-discussion] __array_priority__ ignored if __array__ is present

:58, Frédéric Bastien no...@nouiz.org wrote: I looked yesterday rapidly in the code and didn't find the reason (I don't know it well, that is probably why). But last night I think of one possible cause. I found this code 2 times in the file core/src/umath/ufunc_object.c: if (nin

Re: [Numpy-discussion] __array_priority__ don't work for gt, lt, ... operator

/3164 Any ideas? Cheers, Tom On 10 May 2013 18:34, Charles R Harris charlesr.har...@gmail.com wrote: On Fri, May 10, 2013 at 10:08 AM, Frédéric Bastien no...@nouiz.org wrote: Hi, it popped again on the Theano mailing list that this don't work: np.arange(10) = a_theano_vector

Re: [Numpy-discussion] slight MapIter change

Hi, this is used in Theano. What is the consequence of not doing this? There is people that use it, the question is how many. Is there a way to detect witch version need to be used? thanks Fred On Sat, May 11, 2013 at 11:41 AM, Sebastian Berg sebast...@sipsolutions.net wrote: Hey, (this

Re: [Numpy-discussion] slight MapIter change

ok, thanks for the associated PR. Fred On Mon, May 13, 2013 at 10:19 AM, Sebastian Berg sebast...@sipsolutions.net wrote: On Mon, 2013-05-13 at 09:58 -0400, Frédéric Bastien wrote: Hi, this is used in Theano. What is the consequence of not doing this? There is people that use

[Numpy-discussion] __array_priority__ don't work for gt, lt, ... operator

Hi, it popped again on the Theano mailing list that this don't work: np.arange(10) = a_theano_vector. The reason is that __array_priority__ isn't respected for that class of operation. This page explain the problem and give a work around:

Re: [Numpy-discussion] __array_priority__ don't work for gt, lt, ... operator

at 10:08 AM, Frédéric Bastien no...@nouiz.orgwrote: Hi, it popped again on the Theano mailing list that this don't work: np.arange(10) = a_theano_vector. The reason is that __array_priority__ isn't respected for that class of operation. This page explain the problem and give a work around

Re: [Numpy-discussion] __array_priority__ don't work for gt, lt, ... operator

thanks, I'll look at it. I made a PR: https://github.com/numpy/numpy/pull/3324 Where should I put the tests about this? thanks Fred On Fri, May 10, 2013 at 4:03 PM, Sebastian Berg sebast...@sipsolutions.netwrote: On Fri, 2013-05-10 at 15:35 -0400, Frédéric Bastien wrote: I'm trying to do

Re: [Numpy-discussion] ANN: NumPy 1.7.1 release

, Frédéric Bastien no...@nouiz.org wrote: Hi, A big thanks for that release. I also think it would be useful to do a release candidate about this. This release changed the behavior releated to python long and broke a test in Theano. Nothing important, but we could have fixed this before

Re: [Numpy-discussion] ANN: NumPy 1.7.1 release

Hi, A big thanks for that release. I also think it would be useful to do a release candidate about this. This release changed the behavior releated to python long and broke a test in Theano. Nothing important, but we could have fixed this before the release. The numpy change is that a python

Re: [Numpy-discussion] MapIter api

Hi, this is currently used in Theano! In fact, it is a John S. that implemented it in NumPy to allow fast gradient of the advanced indexing in Theano. It allow code like: matrix1[vector1, vector2] += matrix2 where there is duplicate indices in the vector In looking at the code, I saw it use at

Re: [Numpy-discussion] Please stop bottom posting!!

On Thu, Apr 4, 2013 at 6:01 PM, Chris Barker - NOAA Federal chris.bar...@noaa.gov wrote: [...] Which is why I advocate interspersed posting. It comes down to: please take some thought to compose your post in a way that is suited to the thread and what you are writing, rather than simply use

Re: [Numpy-discussion] Execution time difference between 2.7 and 3.2 using numpy

Hi, win32 do not mean it is a 32 bits windows. sys.platform always return win32 on 32bits and 64 bits windows even for python 64 bits. But that is a good question, is your python 32 or 64 bits? Fred On Wed, Mar 20, 2013 at 10:14 AM, Daπid davidmen...@gmail.com wrote: Without much detailed

Re: [Numpy-discussion] Execution time difference between 2.7 and 3.2 using numpy

On Wed, Mar 20, 2013 at 11:01 AM, Colin J. Williams cjwilliam...@gmail.com wrote: On 20/03/2013 10:30 AM, Frédéric Bastien wrote: Hi, win32 do not mean it is a 32 bits windows. sys.platform always return win32 on 32bits and 64 bits windows even for python 64 bits. But that is a good

Re: [Numpy-discussion] aligned / unaligned structured dtype behavior

On Fri, Mar 8, 2013 at 5:22 AM, Francesc Alted franc...@continuum.io wrote: On 3/7/13 7:26 PM, Frédéric Bastien wrote: I'm surprised that Theano worked with the unaligned input. I added some check to make this raise an error, as we do not support that! Francesc, can you check if Theano give

Re: [Numpy-discussion] aligned / unaligned structured dtype behavior

I agree that documenting this better would be useful to many people. So if someone what to summarize this and put it in the doc, I think many people will appreciate this. Fred On Thu, Mar 7, 2013 at 10:28 PM, Kurt Smith kwmsm...@gmail.com wrote: On Thu, Mar 7, 2013 at 12:26 PM, Frédéric

Re: [Numpy-discussion] aligned / unaligned structured dtype behavior

Hi, It is normal that unaligned access are slower. The hardware have been optimized for aligned access. So this is a user choice space vs speed. We can't go around that. We can only minimize the cost of unaligned access in some cases, but not all and those optimization depend of the CPU. But

Re: [Numpy-discussion] Numpy deprecation schedule

That sound good. To be sure, the now mean the first release that include the deprecation, in that case NumPy 1.7? Fred On Wed, Mar 6, 2013 at 3:09 PM, Nathaniel Smith n...@pobox.com wrote: A number of items on the 1.8 todo list are reminders to remove things that we deprecated in 1.7, and said

Re: [Numpy-discussion] Adding .abs() method to the array object

On Sat, Feb 23, 2013 at 9:34 PM, Benjamin Root ben.r...@ou.edu wrote: My issue is having to remember which ones are methods and which ones are functions. There doesn't seem to be a rhyme or reason for the choices, and I would rather like to see that a line is drawn, but I am not picky as to

Re: [Numpy-discussion] Windows, blas, atlas and dlls

I just read a web page on how to embed python in an application[1]. They explain that we can keep the symbol exported event if we statically link the BLAS library in scipy. This make me think we could just change how we compile the lib that link with BLAS and we will be able to reuse it for other

Re: [Numpy-discussion] Windows, blas, atlas and dlls

Hi, We also have the same problem for Theano. Having one reusable blas on windows would be useful to many project. Also, if possible try to make it accesible from C,C++ too. Not just cython. Fred On Feb 20, 2013 5:15 AM, Dag Sverre Seljebotn d.s.seljeb...@astro.uio.no wrote: On 02/20/2013

Re: [Numpy-discussion] ANN: NumPy 1.7.0rc2 release

Hi, As expected all Theano's tests passed. thanks Fred On Wed, Feb 6, 2013 at 10:10 PM, Ondřej Čertík ondrej.cer...@gmail.comwrote: Hi, I'm pleased to announce the availability of the second release candidate of NumPy 1.7.0rc2. Sources and binary installers can be found at

Re: [Numpy-discussion] Modern Fortran vs NumPy syntax

Hi, I just read a paper[1] that compare python with numpy or pypy vs c++ and fortran from a code, memory and speed point of view. The python code was still better as you can't have list of ndarray in fortran and some other stuff was harder to do. The fastest was fortran, then C++, but pypy around

Re: [Numpy-discussion] Travis failures with no errors

Hi, go to the site tracis-ci(the the next.travis-ci.org part): https://next.travis-ci.org/numpy/numpy/jobs/4118113 When you go that way, in a drop-down menu in the screen, when you are autorized, you can ask travis-ci to rerun the tests. You can do it in the particular test or in the commit

Re: [Numpy-discussion] New numpy functions: filled, filled_like

Why not optimize NumPy to detect a mul of an ndarray by a scalar to call fill? That way, np.empty * 2 will be as fast as x=np.empty; x.fill(2)? Fred On Mon, Jan 14, 2013 at 9:57 AM, Benjamin Root ben.r...@ou.edu wrote: On Mon, Jan 14, 2013 at 7:38 AM, Pierre Haessig pierre.haes...@crans.org

Re: [Numpy-discussion] 1.8 release

Hi, I don't volontear for the next release manager, but +1 for shorter releases. I heard just good comments from that. Also, I'm not sure it would ask more from the release manager. Do someone have an idea? The most work I do as a release manager for theano is the preparation/tests/release notes

Re: [Numpy-discussion] Remove support for numeric and numarray in 1.8

Hi, Just to note, as they plan to remove there dependency on it this year, is it bad that they can't use 1.8 for a few mounts until they finish the conversion? They already have a working version. They can continue to use it for as long they want. The only advantage for them if the compat layers

Re: [Numpy-discussion] ANN: NumPy 1.7.0rc1 release

Hi, Congratulation for the release and a big thanks for the hard work. I tested it with our software and all work fine. thanks! Frédéric On Sun, Dec 30, 2012 at 7:17 PM, Sandro Tosi mo...@debian.org wrote: Hi Ondrej al, On Sat, Dec 29, 2012 at 1:02 AM, Ondřej Čertík

Re: [Numpy-discussion] Howto bisect old commits correctly

Hi, I had many error when tring to the checkedout version and recompile. the problem I had is that I didn't erased the build directory each time. This cause some problem as not all is recompiled correctly in that case. Just deleting this directory manually fixed my problem. HTH Fred On Fri,

Re: [Numpy-discussion] required nose version.

This is fine for us. Frédéric On Sun, Dec 16, 2012 at 5:36 PM, Charles R Harris charlesr.har...@gmail.com wrote: Hi All, Looking at INSTALL.txt with an eye to updating it since we have dropped Python 2.4 -2.5 support, it looks like we could update the nose version also. The first version of

Re: [Numpy-discussion] Status of the 1.7 release

Hi, I added a new issue that is a regression about numpy.ndindex() that we already talked. But it was a duplicate[1], so I closed it. I think it got lost as the ticket wasn't marked for 1.7 milestone. Ccan someone do it? I don't have the right. This regression break something in Theano. We

Re: [Numpy-discussion] Status of the 1.7 release

While we are at it, back-porting https://github.com/numpy/numpy/pull/2730 Would give a good speed up for an LTS. I made a new PR that do this back-port: https://github.com/numpy/numpy/pull/2847 Fred On Mon, Dec 17, 2012 at 11:46 AM, David Warde-Farley d.warde.far...@gmail.com wrote: A bit

Re: [Numpy-discussion] Use OpenBLAS for the binary releases?

Hi, it was mainly developed by one person and he left for Intel. They relicensed GotoBLAS to BSD 3 clauses and some Chinese people forked it to OpenBLAS. There was another fork, but I didn't got news of it. Maybe I just missed the news. Fred On Mon, Nov 19, 2012 at 12:20 PM, Daniele Nicolodi

Re: [Numpy-discussion] Scipy dot

On Fri, Nov 9, 2012 at 3:32 AM, Nathaniel Smith n...@pobox.com wrote: On Fri, Nov 9, 2012 at 6:18 AM, Nicolas SCHEFFER scheffer.nico...@gmail.com wrote: Fred, Thanks for the advice. The code will only affect the part in _dotblas.c where gemm is called. There's tons of check before

Re: [Numpy-discussion] Scipy dot

On Fri, Nov 9, 2012 at 10:20 AM, Nathaniel Smith n...@pobox.com wrote: On Fri, Nov 9, 2012 at 2:45 PM, Frédéric Bastien no...@nouiz.org wrote: On Fri, Nov 9, 2012 at 3:32 AM, Nathaniel Smith n...@pobox.com wrote: On Fri, Nov 9, 2012 at 6:18 AM, Nicolas SCHEFFER scheffer.nico

Re: [Numpy-discussion] Scipy dot

Hi, I also think it should go into numpy.dot and that the output order should not be changed. A new point, what about the additional overhead for small ndarray? To remove this, I would suggest to put this code into the C function that do the actual work (at least, from memory it is a c function,

Re: [Numpy-discussion] Scipy dot

me know how you'd like to proceed, Thanks! FIXMEs: - Fix for ndim != 2 - Fix for dtype == np.complex* - Fix order of output array On Thu, Nov 8, 2012 at 9:42 AM, Frédéric Bastien no...@nouiz.org wrote: Hi, I also think it should go into numpy.dot

Re: [Numpy-discussion] 1.7.0 release

Hi, I updated the numpy master and recompiled it. I still have the compilation error I got from Theano. I'll pop up that email thread again to have the history and I made a PR for this. Also, I think I said that numpy.ndindex changed its interface, in the past numpy.ndindex() was valid, not this

Re: [Numpy-discussion] np 1.7b2 PyArray_BYTES(obj)=ptr fail

Hi, I made a PR with my fix: https://github.com/numpy/numpy/pull/2709 Frédéric On Tue, Oct 2, 2012 at 6:18 PM, Charles R Harris charlesr.har...@gmail.comwrote: On Tue, Oct 2, 2012 at 1:44 PM, Frédéric Bastien no...@nouiz.org wrote: With numpy 1.6.2, it is working. So

Re: [Numpy-discussion] NumPy to CPU+GPU compiler, looking for tests

On Tue, Oct 23, 2012 at 11:48 AM, Henry Gomersall h...@cantab.net wrote: On Tue, 2012-10-23 at 11:41 -0400, Frédéric Bastien wrote: Did you saw the gpu nd array project? We try to do something similar but only for the GPU. Out of interest, is there a reason why the backend for Numpy could

Re: [Numpy-discussion] NumPy to CPU+GPU compiler, looking for tests

, Oct 29, 2012 at 11:26 AM, Henry Gomersall h...@cantab.net wrote: On Mon, 2012-10-29 at 11:11 -0400, Frédéric Bastien wrote: Assuming of course all the relevant backends are up to scratch. Is there a fundamental reason why targetting a CPU through OpenCL is worse than doing it exclusively

Re: [Numpy-discussion] NumPy to CPU+GPU compiler, looking for tests

On Mon, Oct 29, 2012 at 11:53 AM, Henry Gomersall h...@cantab.net wrote: On Mon, 2012-10-29 at 11:49 -0400, Frédéric Bastien wrote: That is possible. Great! Just to be clear, I mean this is possible to make it work. We do not do that for now. Also, sharing the memory on the CPU and GPU

Re: [Numpy-discussion] NumPy to CPU+GPU compiler, looking for tests

Did you saw the gpu nd array project? We try to do something similar but only for the GPU. https://github.com/inducer/compyte/wiki Fred On Sun, Oct 21, 2012 at 2:57 PM, Rahul Garg rahulgar...@gmail.com wrote: Thanks! I need to add support for eig and inv (will do this week, at least for CPU)

Re: [Numpy-discussion] Is there a way to reset an accumulate function?

Hi, Why not start conting from the end of the vector until you find a nan? Your problem do not need to check the full vector. Fred On Tue, Oct 23, 2012 at 1:11 PM, Cera, Tim t...@cerazone.net wrote: I have an array that is peppered throughout in random spots with 'nan'. I would like to use

[Numpy-discussion] np 1.7b2 PyArray_BYTES(obj)=ptr fail

Hi, I don't know if that was raised or not, but in np1.7b2 doing this fail with this error message: PyArray_BYTES(obj)=ptr file:lne_number:offset: error: lvalue required as left operatnd of assignment. I tried with PyArray_DATA(obj)=ptr and this also fail. Do you want to remove this feature

Re: [Numpy-discussion] np 1.7b2 PyArray_BYTES(obj)=ptr fail

a Theano release candidate and I really would like the final version to work with the next release of NumPy. thanks. Fred On Tue, Oct 2, 2012 at 11:33 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Tue, Oct 2, 2012 at 8:34 AM, Frédéric Bastien no...@nouiz.org wrote: Hi, I don't

Re: [Numpy-discussion] np 1.7b2 PyArray_BYTES(obj)=ptr fail

On Tue, Oct 2, 2012 at 1:18 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Tue, Oct 2, 2012 at 9:45 AM, Frédéric Bastien no...@nouiz.org wrote: We implement our own subtensor(x[...], where ... can be index or slice) c code due to the way Theano work. I can probably change

Re: [Numpy-discussion] np 1.7b2 PyArray_BYTES(obj)=ptr fail

something here, do someone know? Fred On Tue, Oct 2, 2012 at 1:47 PM, Charles R Harris charlesr.har...@gmail.com wrote: On Tue, Oct 2, 2012 at 11:43 AM, Charles R Harris charlesr.har...@gmail.com wrote: On Tue, Oct 2, 2012 at 11:30 AM, Frédéric Bastien no...@nouiz.org wrote: On Tue

Re: [Numpy-discussion] Memory order of array copies

As always, I think it is better to don't change the default behaviour. There is many people that don't update frequently and 2 releases is not enough. This will lead to many hard to find bug. This will also give the impression what we can't rely on numpy default behaviour and numpy is not stable.

  1   2   >