Re: [Numpy-discussion] A Cython apply_along_axis function

On 12/02/2010 08:17 AM, Robert Bradshaw wrote: > On Wed, Dec 1, 2010 at 6:09 PM, John Salvatier > wrote: > >> On Wed, Dec 1, 2010 at 6:07 PM, Keith Goodman wrote: >> >>> On Wed, Dec 1, 2010 at 5:53 PM, David wrote: >>> >>> On 12/02/2010 04:47 AM, Keith Goodman wrote:

Re: [Numpy-discussion] broadcasting with numpy.interp

2010/12/1 greg whittier : > On Wed, Nov 24, 2010 at 3:16 PM, Friedrich Romstedt > wrote: >> I assume you just need *some* interpolation, not that specific one? >> In that case, I'd suggest the following: >> >> 1)  Use a 2d interpolation, taking into account all nearest neighbours. >> 2)  For this,

[Numpy-discussion] Threshold

Hi all, I' m developing a medical software named InVesalius [1], it is a free software. It uses numpy arrays to store the medical images (CT and MRI) and the mask, the mask is used to mark the region of interest and to create 3D surfaces. Those array generally have 512x512 elements. The mask is cr

Re: [Numpy-discussion] Threshold

> mask = numpy.zeros(medical_image.shape, dtype="uint16") > mask[ numpy.logical_and( medical_image >= lower, medical_image <= > upper)] = 255 > > Where lower and upper are the threshold bounds. Here I' m marking the > array positions where medical_image is between the threshold bounds > with 255,

Re: [Numpy-discussion] Threshold

On Thu, Dec 2, 2010 at 11:14 AM, Zachary Pincus wrote: >> mask = numpy.zeros(medical_image.shape, dtype="uint16") >> mask[ numpy.logical_and( medical_image >= lower, medical_image <= >> upper)] = 255 >> >> Where lower and upper are the threshold bounds. Here I' m marking the >> array positions whe

Re: [Numpy-discussion] printoption to allow hexified floats?

Thanks for the replies. Robert is right; many numerical operations, particularly complex ones, generate different values across platforms, and we deal with these by storing the values from some platform as a reference and using allclose(), which requires extra work. But many basic operations

[Numpy-discussion] Float16 and PEP 3118

Hi Folks, Now that the float16 type is in I was wondering if we should do anything to support it in the PEP 3118 buffer interface. This would probably affect the Cython folks as well as the people working on fixing up the structure module for Python 3.x. There is

Re: [Numpy-discussion] printoption to allow hexified floats?

On Thu, Dec 2, 2010 at 11:17 AM, Ken Basye wrote: > Thanks for the replies. > > Robert is right; many numerical operations, particularly complex ones, > generate different values across platforms, and we deal with these by > storing the values from some platform as a reference and using > allclos

Re: [Numpy-discussion] Float16 and PEP 3118

Thu, 02 Dec 2010 10:20:27 -0700, Charles R Harris wrote: > Now that the float16 type is in I was wondering if we should do anything > to support it in the PEP 3118 buffer interface. This would probably > affect the Cython folks as well as the people working on fixing up the > structure module

[Numpy-discussion] Pushing changes to numpy git repo problem

Hi, I have followed Development workflow instructions in http://docs.scipy.org/doc/numpy/dev/gitwash/ but I am having a problem with the last step: $ git push upstream ticket1679:master fatal: remote error: You can't push to git://github.com/numpy/numpy.git Use g...@github.com:numpy/numpy

Re: [Numpy-discussion] Pushing changes to numpy git repo problem

On Thu, Dec 2, 2010 at 12:52 PM, Pearu Peterson wrote: > > What I am doing wrong? > > Here's some additional info: > $ git remote -v show > origin  ...@github.com:pearu/numpy.git (fetch) > origin  ...@github.com:pearu/numpy.git (push) > upstream        git://github.com/numpy/numpy.git (fetch) > up

Re: [Numpy-discussion] Pushing changes to numpy git repo problem

On Thu, Dec 2, 2010 at 1:52 PM, Pearu Peterson wrote: > Hi, > > I have followed Development workflow instructions in > > http://docs.scipy.org/doc/numpy/dev/gitwash/ > > but I am having a problem with the last step: > > $ git push upstream ticket1679:master > fatal: remote error: > You can't pus

Re: [Numpy-discussion] Pushing changes to numpy git repo problem

Thanks! Pearu On Thu, Dec 2, 2010 at 11:08 PM, Charles R Harris wrote: > > > On Thu, Dec 2, 2010 at 1:52 PM, Pearu Peterson > wrote: >> >> Hi, >> >> I have followed Development workflow instructions in >> >>  http://docs.scipy.org/doc/numpy/dev/gitwash/ >> >> but I am having a problem with the l

[Numpy-discussion] numpy.test() Program received signal SIGABRT, Aborted.

Hi all, I have installed the latest version of numpy. >>> numpy.__version__ '2.0.0.dev-6aacc2d' numpy.test(verbose=2) received signal SIGABRT. test_cdouble_2 (test_linalg.TestEig) ... ok test_csingle (test_linalg.TestEig) ... FAIL *** glibc detected *** /data/home/nwagner/local/bin/python: fre

Re: [Numpy-discussion] numpy.test() Program received signal SIGABRT, Aborted.

On Fri, Dec 3, 2010 at 12:29 AM, Nils Wagner wrote: > Hi all, > > I have installed the latest version of numpy. > > >>> numpy.__version__ > '2.0.0.dev-6aacc2d' > > I don't see that here or on the buildbots. There was a problem with segfaults that was fixed in commit c0e1cf27b55dfd5a

Re: [Numpy-discussion] numpy.test() Program received signal SIGABRT, Aborted.

On Fri, 3 Dec 2010 00:42:16 -0700 Charles R Harris wrote: > On Fri, Dec 3, 2010 at 12:29 AM, Nils Wagner > wrote: > >> Hi all, >> >> I have installed the latest version of numpy. >> >> >>> numpy.__version__ >> '2.0.0.dev-6aacc2d' >> >> > > I don't see that here or on the buildbots. There was a

Re: [Numpy-discussion] numpy.test() Program received signal SIGABRT, Aborted.

On Fri, 03 Dec 2010 08:47:32 +0100 "Nils Wagner" wrote: > On Fri, 3 Dec 2010 00:42:16 -0700 > Charles R Harris wrote: >> On Fri, Dec 3, 2010 at 12:29 AM, Nils Wagner >> wrote: >> >>> Hi all, >>> >>> I have installed the latest version of numpy. >>> >>> >>> numpy.__version__ >>> '2.0.0.dev-6aa