Re: [Numpy-discussion] 3D interpolation of large array

On 13-Sep-09, at 8:51 PM, brechmos wrote: > > I have a large dataset (e.g., 70 x 500 x 500) and want to > interpolate points > (for example to double the size). What it seems I want is: > > []: newx,newy,newz=mgrid[1:70:0.5,1:500:0.5,1:500:0.5] > []: coords = array([newz, newy, newx]) > []: dou

[Numpy-discussion] 3D interpolation of large array

I have a large dataset (e.g., 70 x 500 x 500) and want to interpolate points (for example to double the size). What it seems I want is: []: newx,newy,newz=mgrid[1:70:0.5,1:500:0.5,1:500:0.5] []: coords = array([newz, newy, newx]) []: dout = np.map_coordinates(d, coords) The problem is that mgri

Re: [Numpy-discussion] Scientific Computing with Python, September 18, 2009

a...@ajackson.org wrote: >>On Fri, Sep 11, 2009 at 7:26 PM, Robert Ferrell >>wrote: >>> >>> >>> On Sep 11, 2009, at 5:07 PM, Neal Becker wrote: >>> I'd love to participate in these webinars. Problem is, AFAICT, gotomeeting only supports windows. >>> >>> I'm not certain that is cor

Re: [Numpy-discussion] Scientific Computing with Python, September 18, 2009

a...@ajackson.org wrote: >>On Fri, Sep 11, 2009 at 7:26 PM, Robert Ferrell >>wrote: >>> >>> >>> On Sep 11, 2009, at 5:07 PM, Neal Becker wrote: >>> I'd love to participate in these webinars. Problem is, AFAICT, gotomeeting only supports windows. >>> >>> I'm not certain that is cor

Re: [Numpy-discussion] Scientific Computing with Python, September 18, 2009

>On Fri, Sep 11, 2009 at 7:26 PM, Robert Ferrell wrote: >> >> >> On Sep 11, 2009, at 5:07 PM, Neal Becker wrote: >> >>> I'd love to participate in these webinars.  Problem is, AFAICT, >>> gotomeeting >>> only supports windows. >> >> I'm not certain that is correct.  I've participated in some of th

Re: [Numpy-discussion] `missing` argument in genfromtxt only a string?

On Sun, Sep 13, 2009 at 1:29 PM, Skipper Seabold wrote: > Is there a reason that the missing argument in genfromtxt only takes a string? > > For instance, I have a dataset that in most columns has a zero for > some observations but in others it was just left blank, which is the > equivalent of zer

Re: [Numpy-discussion] Why is the truth value of ndarray not simply size>0 ?

On Sun, Sep 13, 2009 at 05:30, Robert wrote: > Neil Martinsen-Burrell wrote: >> On 2009-09-07 07:11 , Robert wrote: >>> Is there a reason why ndarray truth tests (except scalars) >>> deviates from the convention of other Python iterables >>> list,array.array,str,dict,... ? >>> >>> Furthermore ther

[Numpy-discussion] `missing` argument in genfromtxt only a string?

Is there a reason that the missing argument in genfromtxt only takes a string? For instance, I have a dataset that in most columns has a zero for some observations but in others it was just left blank, which is the equivalent of zero. I would like to set all of the missing to 0 (it defaults to -1

Re: [Numpy-discussion] suggestion for generalizing numpy functions

On Sat, Jul 25, 2009 at 8:33 PM, Darren Dale wrote: > On Thu, Jul 23, 2009 at 12:54 PM, Darren Dale wrote: >> On Tue, Jul 21, 2009 at 10:11 AM, Darren Dale wrote: >>> On Tue, Jul 21, 2009 at 7:44 AM, Darren Dale wrote: 2009/7/20 Stéfan van der Walt : > Hi Chuck > > 2009/7/17 Charl

Re: [Numpy-discussion] Why is the truth value of ndarray not simply size>0 ?

On Sun, Sep 13, 2009 at 9:05 AM, Alan G Isaac wrote: > On 9/13/2009 7:46 AM, Robert wrote: >> 2 ways seem to be consistently Pythonic and logical: "size> >> 0"; or "any(a)" (*); and the later option may be more 'numerical'. > > Well, *there's* the problem. > > As a user I have felt more than once

Re: [Numpy-discussion] 64-bit Fedora 9 a=numpy.zeros(0x80000000, dtype='b1')

2009/9/13 Nadav Horesh > > Could it be a problem of python version? I get no error with python2.6.2 > (on amd64 gentoo) > > Nadav > > -הודעה מקורית- > מאת: numpy-discussion-boun...@scipy.org בשם David Cournapeau > נשלח: א 13-ספטמבר-09 09:48 > אל: Discussion of Numerical Python > נושא: Re

Re: [Numpy-discussion] Why is the truth value of ndarray not simply size>0 ?

On 9/13/2009 7:46 AM, Robert wrote: > 2 ways seem to be consistently Pythonic and logical: "size> > 0"; or "any(a)" (*); and the later option may be more 'numerical'. Well, *there's* the problem. As a user I have felt more than once that a length based test, like other containers, would be natura

Re: [Numpy-discussion] Why is the truth value of ndarray not simply size>0 ?

Robert wrote: > Neil Martinsen-Burrell wrote: >> On 2009-09-07 07:11 , Robert wrote: >>> Is there a reason why ndarray truth tests (except scalars) >>> deviates from the convention of other Python iterables >>> list,array.array,str,dict,... ? >>> >>> Furthermore there is a surprising strange except

Re: [Numpy-discussion] 64-bit Fedora 9 a=numpy.zeros(0x80000000, dtype='b1')

Could it be a problem of python version? I get no error with python2.6.2 (on amd64 gentoo) Nadav -הודעה מקורית- מאת: numpy-discussion-boun...@scipy.org בשם David Cournapeau נשלח: א 13-ספטמבר-09 09:48 אל: Discussion of Numerical Python נושא: Re: [Numpy-discussion] 64-bit Fedora 9 a=num

Re: [Numpy-discussion] Why is the truth value of ndarray not simply size>0 ?

Neil Martinsen-Burrell wrote: > On 2009-09-07 07:11 , Robert wrote: >> Is there a reason why ndarray truth tests (except scalars) >> deviates from the convention of other Python iterables >> list,array.array,str,dict,... ? >> >> Furthermore there is a surprising strange exception for arrays >> with

Re: [Numpy-discussion] 64-bit Fedora 9 a=numpy.zeros(0x80000000, dtype='b1')

Charles R Harris wrote: > > > On Sat, Sep 12, 2009 at 9:03 AM, Citi, Luca > wrote: > > I just realized that Sebastian posted its 'uname -a' and he has a > 64bit machine. > In this case it should work as mine (the 64bit one) does. > Maybe during the compila