Re: [Numpy-discussion] datetime64 1970 issue

2013-04-16 Thread Charles R Harris
On Tue, Apr 16, 2013 at 6:45 PM, Benjamin Root wrote: > > On Tue, Apr 16, 2013 at 7:45 PM, Ondřej Čertík wrote: > >> On Tue, Apr 16, 2013 at 4:55 PM, Bob Nnamtrop >> wrote: >> > I am curious if others have noticed an issue with datetime64 at the >> > beginning of 1970. First: >> > >> > In [144]:

Re: [Numpy-discussion] datetime64 1970 issue

2013-04-16 Thread Zachary Ploskey
The problem does not appear to exist on Linux with numpy version 1.6.2. In [1]: import numpy as np In [2]: np.datetime64('1970-01-01') - np.datetime64('1969-12-31') Out[2]: 1 day, 0:00:00 In [3]: np.datetime64('1970-01-01 00') - np.datetime64('1969-12-31 00') Out[3]: 1 day, 0:00:00 In [4]: np._

Re: [Numpy-discussion] datetime64 1970 issue

2013-04-16 Thread Benjamin Root
On Tue, Apr 16, 2013 at 7:45 PM, Ondřej Čertík wrote: > On Tue, Apr 16, 2013 at 4:55 PM, Bob Nnamtrop > wrote: > > I am curious if others have noticed an issue with datetime64 at the > > beginning of 1970. First: > > > > In [144]: (np.datetime64('1970-01-01') - np.datetime64('1969-12-31')) > > Ou

Re: [Numpy-discussion] datetime64 1970 issue

2013-04-16 Thread Ondřej Čertík
On Tue, Apr 16, 2013 at 4:55 PM, Bob Nnamtrop wrote: > I am curious if others have noticed an issue with datetime64 at the > beginning of 1970. First: > > In [144]: (np.datetime64('1970-01-01') - np.datetime64('1969-12-31')) > Out[144]: numpy.timedelta64(1,'D') > > OK this look fine, they are one

[Numpy-discussion] datetime64 1970 issue

2013-04-16 Thread Bob Nnamtrop
I am curious if others have noticed an issue with datetime64 at the beginning of 1970. First: In [144]: (np.datetime64('1970-01-01') - np.datetime64('1969-12-31')) Out[144]: numpy.timedelta64(1,'D') OK this look fine, they are one day apart. But look at this: In [145]: (np.datetime64('1970-01-01

Re: [Numpy-discussion] Raveling, reshape order keyword unnecessarily confuses index and memory ordering

2013-04-16 Thread srean
As one lurker to another, thanks for calling it out. Over-argumentative, and personality centric threads like these have actually led me to distance myself from the numpy community. I do not know how common it is now because I do not follow it closely anymore. It used to be quite common at one poi

Re: [Numpy-discussion] taking a 2D uneven surface slice

2013-04-16 Thread Bradley M. Froehle
Hi Bryan: On Tue, Apr 16, 2013 at 1:21 PM, Bryan Woods wrote: > I'm trying to do something that at first glance I think should be simple > but I can't quite figure out how to do it. The problem is as follows: > > I have a 3D grid Values[Nx, Ny, Nz] > > I want to slice Values at a 2D surface in t

[Numpy-discussion] taking a 2D uneven surface slice

2013-04-16 Thread Bryan Woods
I'm trying to do something that at first glance I think should be simple but I can't quite figure out how to do it. The problem is as follows: I have a 3D grid Values[Nx, Ny, Nz] I want to slice Values at a 2D surface in the Z dimension specified by Z_index[Nx, Ny] and return a 2D slice[Nx, N

Re: [Numpy-discussion] MapIter api

2013-04-16 Thread Nathaniel Smith
On Mon, Apr 15, 2013 at 5:29 PM, Sebastian Berg wrote: > Hey, > > the MapIter API has only been made public in master right? So it is no > problem at all to change at least the mapiter struct, right? > > I got annoyed at all those special cases that make things difficult to > get an idea where to

Re: [Numpy-discussion] MapIter api

2013-04-16 Thread Sebastian Berg
On Mon, 2013-04-15 at 13:36 -0600, Charles R Harris wrote: > > > On Mon, Apr 15, 2013 at 1:27 PM, Sebastian Berg > wrote: > On Mon, 2013-04-15 at 11:16 -0600, Charles R Harris wrote: > > > > > > On Mon, Apr 15, 2013 at 10:29 AM, Sebastian Berg > > wrote: