[Numpy-discussion] life expectancy of scipy.stats nan statistics

I'm just looking at http://projects.scipy.org/scipy/ticket/1200 I agree with Ralf that the bias keyword should be changed to ddof as in the numpy functions. For functions in scipy.stats, and statistics in general, I prefer the usual axis=0 default. However, I think these functions, like scipy.sta

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 3:05 PM, Mark Wiebe wrote: > On Fri, Aug 19, 2011 at 11:44 AM, Charles R Harris > wrote: >> >> >> On Fri, Aug 19, 2011 at 12:37 PM, Bruce Southey >> wrote: >>> >>> Hi, >>> Just some immediate minor observations that are really about trying to >>> be consistent: >>> >>> 1)

[Numpy-discussion] ImportError: dynamic module does not define init function (initmultiarray)

Dear list, I'm embedding Python inside a C program to pull functions from user-supplied Python modules. All is well except when the user-supplied module imports numpy. Requesting a stack trace when an exception occurs reveals the following: --- Traceback (most recent call last): File "/Users/dp

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Thu, Aug 18, 2011 at 2:43 PM, Mark Wiebe wrote: > It's taken a lot of changes to get the NA mask support to its current > point, but the code ready for some testing now. You can read the > work-in-progress release notes here: > > > https://github.com/m-paradox/numpy/blob/missingdata/doc/releas

Re: [Numpy-discussion] numpy segfaults with ctypes

Hi, On Fri, Aug 19, 2011 at 1:04 PM, Angus McMorland wrote: > Hi all, > > I'm giving this email a new subject, in case that helps it catch the > attention of someone who can fix my problem. I currently cannot > upgrade numpy from git to any date more recent than 10 July. Git > commit feb8079070b8

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 11:44 AM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Fri, Aug 19, 2011 at 12:37 PM, Bruce Southey wrote: > >> Hi, >> Just some immediate minor observations that are really about trying to >> be consistent: >> >> 1) Could you keep the display of the NA dty

[Numpy-discussion] numpy segfaults with ctypes

Hi all, I'm giving this email a new subject, in case that helps it catch the attention of someone who can fix my problem. I currently cannot upgrade numpy from git to any date more recent than 10 July. Git commit feb8079070b8a659d7ee is the first that causes the problem (according to github, the c

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 9:15 PM, Mark Wiebe wrote: > On Fri, Aug 19, 2011 at 11:37 AM, Bruce Southey wrote: > >> Hi, >> Just some immediate minor observations that are really about trying to >> be consistent: >> >> 1) Could you keep the display of the NA dtype be the same as the array? >> For exa

Re: [Numpy-discussion] Statistical distributions on samples

I have applied the update to the documentation (although that function needs a general rewrite - later...) >On Mon, Aug 15, 2011 at 8:53 AM, Andrea Gavana wrote: > >> Hi Chris and All, >> >> On 12 August 2011 16:53, Christopher Jordan-Squire wrote: >> > Hi Andrea--An easy way to get something like

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 11:37 AM, Bruce Southey wrote: > Hi, > Just some immediate minor observations that are really about trying to > be consistent: > > 1) Could you keep the display of the NA dtype be the same as the array? > For example, NA dtype is displayed as ' 'float64' as that is the arr

Re: [Numpy-discussion] Reconstruct multidimensional array from buffer without shape

On 19. aug. 2011, at 19.57, Ian wrote: > Right. I'm new to NumPy so I figured I'd check if there was some nifty way of > preserving the shape without storing it in the database that I hadn't > discovered yet. No worries, I'll store the shape alongside the array. Thanks > for the reply. > I lo

Re: [Numpy-discussion] Reconstruct multidimensional array from buffer without shape

Right. I'm new to NumPy so I figured I'd check if there was some nifty way of preserving the shape without storing it in the database that I hadn't discovered yet. No worries, I'll store the shape alongside the array. Thanks for the reply. Ian > >From: Olivie

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 12:37 PM, Bruce Southey wrote: > Hi, > Just some immediate minor observations that are really about trying to > be consistent: > > 1) Could you keep the display of the NA dtype be the same as the array? > For example, NA dtype is displayed as ' 'float64' as that is the arr

Re: [Numpy-discussion] Reconstruct multidimensional array from buffer without shape

How could it be possible? If you only have the buffer data, there could be many different valid shapes associated to this data. -=- Olivier 2011/8/19 Ian > Hello list, > > I am storing a multidimensional array as binary in a Postgres 9.04 > database. For retrieval of this array from the databas

[Numpy-discussion] Reconstruct multidimensional array from buffer without shape

Hello list, I am storing a multidimensional array as binary in a Postgres 9.04 database. For retrieval of this array from the database I thought frombuffer() was my solution, however I see that this constructs a one-dimensional array. I read in the documentation about the buffer parameter in th

Re: [Numpy-discussion] NA masks for NumPy are ready to test

Hi, Just some immediate minor observations that are really about trying to be consistent: 1) Could you keep the display of the NA dtype be the same as the array? For example, NA dtype is displayed as '>> a=np.array([[1,2,3,np.NA], [3,4,np.nan,5]]) >>> a array([[ 1., 2., 3., NA], [ 3.,

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 11:07 AM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Fri, Aug 19, 2011 at 11:55 AM, Bruce Southey wrote: > >> On Fri, Aug 19, 2011 at 10:48 AM, Mark Wiebe wrote: >> > On Fri, Aug 19, 2011 at 7:15 AM, Bruce Southey >> wrote: >> >> >> >> On 08/18/2011 04:

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 11:55 AM, Bruce Southey wrote: > On Fri, Aug 19, 2011 at 10:48 AM, Mark Wiebe wrote: > > On Fri, Aug 19, 2011 at 7:15 AM, Bruce Southey > wrote: > >> > >> On 08/18/2011 04:43 PM, Mark Wiebe wrote: > >> > >> It's taken a lot of changes to get the NA mask support to its cu

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 10:27 AM, Ralf Gommers wrote: > > > On Fri, Aug 19, 2011 at 5:23 PM, Bruce Southey wrote: >> >> On 08/19/2011 10:04 AM, Ralf Gommers wrote: >> >> On Fri, Aug 19, 2011 at 4:55 PM, Bruce Southey wrote: >>> >>> Hi, >>> I had to rebuild my Python2.6 as a 'normal' version. >>>

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 10:48 AM, Mark Wiebe wrote: > On Fri, Aug 19, 2011 at 7:15 AM, Bruce Southey wrote: >> >> On 08/18/2011 04:43 PM, Mark Wiebe wrote: >> >> It's taken a lot of changes to get the NA mask support to its current >> point, but the code ready for some testing now. You can read t

Re: [Numpy-discussion] summing an array

On 19/08/11 15:49, Chris Withers wrote: > On 18/08/2011 07:58, Bob Dowling wrote: >> >> >>> numpy.add.accumulate(a) >> array([ 0, 1, 3, 6, 10]) >> >> >>> numpy.add.accumulate(a, out=a) >> array([ 0, 1, 3, 6, 10]) > > What's the difference between numpy.cumsum and numpy.add.accumulate? I think the

[Numpy-discussion] Can't mix np.newaxis with boolean indexing

I could have sworn that this use to work: import numpy as np a = np.random.random((100,)) b = (a > 0.5) print a[b, np.newaxis] But instead, I get this error on the latest master: Traceback (most recent call last): File "", line 1, in TypeError: long() argument must be a string or a number, no

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 7:15 AM, Bruce Southey wrote: > ** > On 08/18/2011 04:43 PM, Mark Wiebe wrote: > > It's taken a lot of changes to get the NA mask support to its current > point, but the code ready for some testing now. You can read the > work-in-progress release notes here: > > > https://

Re: [Numpy-discussion] longlong format error with Python <= 2.6 in scalartypes.c

On Thu, Aug 18, 2011 at 9:01 PM, Mark Wiebe wrote: > On Thu, Aug 4, 2011 at 4:08 PM, Derek Homeier > wrote: >> >> Hi, >> >> commits c15a807e and c135371e (thus most immediately addressed to Mark, >> but I am sending this to the list hoping for more insight on the issue) >> introduce a test failur

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 5:23 PM, Bruce Southey wrote: > ** > On 08/19/2011 10:04 AM, Ralf Gommers wrote: > > > > On Fri, Aug 19, 2011 at 4:55 PM, Bruce Southey wrote: > >> Hi, >> I had to rebuild my Python2.6 as a 'normal' version. >> >> Anyhow, Python2.4, 2.5, 2.6 and 2.7 all build and pass t

Re: [Numpy-discussion] How to start at line # x when using numpy.memmap

On Fri, Aug 19, 2011 at 9:23 AM, Warren Weckesser wrote: > > > On Fri, Aug 19, 2011 at 10:09 AM, Jeremy Conlin wrote: >> >> On Fri, Aug 19, 2011 at 8:01 AM, Brent Pedersen >> wrote: >> > On Fri, Aug 19, 2011 at 7:29 AM, Jeremy Conlin >> > wrote: >> >> On Fri, Aug 19, 2011 at 7:19 AM, Pauli Virt

Re: [Numpy-discussion] How to start at line # x when using numpy.memmap

On Fri, Aug 19, 2011 at 10:09 AM, Jeremy Conlin wrote: > On Fri, Aug 19, 2011 at 8:01 AM, Brent Pedersen > wrote: > > On Fri, Aug 19, 2011 at 7:29 AM, Jeremy Conlin > wrote: > >> On Fri, Aug 19, 2011 at 7:19 AM, Pauli Virtanen wrote: > >>> Fri, 19 Aug 2011 07:00:31 -0600, Jeremy Conlin wrote:

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On 08/19/2011 10:04 AM, Ralf Gommers wrote: On Fri, Aug 19, 2011 at 4:55 PM, Bruce Southey > wrote: Hi, I had to rebuild my Python2.6 as a 'normal' version. Anyhow, Python2.4, 2.5, 2.6 and 2.7 all build and pass the numpy tests. Curiously, only

Re: [Numpy-discussion] How to start at line # x when using numpy.memmap

On Fri, Aug 19, 2011 at 9:09 AM, Jeremy Conlin wrote: > On Fri, Aug 19, 2011 at 8:01 AM, Brent Pedersen wrote: >> On Fri, Aug 19, 2011 at 7:29 AM, Jeremy Conlin wrote: >>> On Fri, Aug 19, 2011 at 7:19 AM, Pauli Virtanen wrote: Fri, 19 Aug 2011 07:00:31 -0600, Jeremy Conlin wrote: > I w

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 7:55 AM, Bruce Southey wrote: > ** > On 08/18/2011 04:43 PM, Mark Wiebe wrote: > > It's taken a lot of changes to get the NA mask support to its current > point, but the code ready for some testing now. You can read the > work-in-progress release notes here: > > > https://

Re: [Numpy-discussion] How to start at line # x when using numpy.memmap

On Fri, Aug 19, 2011 at 8:01 AM, Brent Pedersen wrote: > On Fri, Aug 19, 2011 at 7:29 AM, Jeremy Conlin wrote: >> On Fri, Aug 19, 2011 at 7:19 AM, Pauli Virtanen wrote: >>> Fri, 19 Aug 2011 07:00:31 -0600, Jeremy Conlin wrote: I would like to use numpy's memmap on some data files I have. Th

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On Fri, Aug 19, 2011 at 4:55 PM, Bruce Southey wrote: > ** > > Hi, > I had to rebuild my Python2.6 as a 'normal' version. > > Anyhow, Python2.4, 2.5, 2.6 and 2.7 all build and pass the numpy tests. > > Curiously, only tests in Python2.7 give almost no warnings but all the > other Python2.x give

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On 08/18/2011 04:43 PM, Mark Wiebe wrote: It's taken a lot of changes to get the NA mask support to its current point, but the code ready for some testing now. You can read the work-in-progress release notes here: https://github.com/m-paradox/numpy/blob/missingdata/doc/release/2.0.0-notes.rst

Re: [Numpy-discussion] summing an array

On 18/08/2011 07:58, Bob Dowling wrote: > > >>> numpy.add.accumulate(a) > array([ 0, 1, 3, 6, 10]) > > >>> numpy.add.accumulate(a, out=a) > array([ 0, 1, 3, 6, 10]) What's the difference between numpy.cumsum and numpy.add.accumulate? Where can I find the reference docs for these? che

Re: [Numpy-discussion] NA masks for NumPy are ready to test

On 08/18/2011 04:43 PM, Mark Wiebe wrote: It's taken a lot of changes to get the NA mask support to its current point, but the code ready for some testing now. You can read the work-in-progress release notes here: https://github.com/m-paradox/numpy/blob/missingdata/doc/release/2.0.0-notes.rst

Re: [Numpy-discussion] How to start at line # x when using numpy.memmap

On 08/19/2011 05:01 PM, Brent Pedersen wrote: > On Fri, Aug 19, 2011 at 7:29 AM, Jeremy Conlin wrote: >> On Fri, Aug 19, 2011 at 7:19 AM, Pauli Virtanen wrote: >>> Fri, 19 Aug 2011 07:00:31 -0600, Jeremy Conlin wrote: I would like to use numpy's memmap on some data files I have. The first

Re: [Numpy-discussion] How to start at line # x when using numpy.memmap

On Fri, Aug 19, 2011 at 7:29 AM, Jeremy Conlin wrote: > On Fri, Aug 19, 2011 at 7:19 AM, Pauli Virtanen wrote: >> Fri, 19 Aug 2011 07:00:31 -0600, Jeremy Conlin wrote: >>> I would like to use numpy's memmap on some data files I have. The first >>> 12 or so lines of the files contain text (header

Re: [Numpy-discussion] [SciPy-User] disabling SVN (was: Trouble installing scipy after upgrading to Mac OS X 10.7 aka Lion)

On Fri, Aug 19, 2011 at 2:48 PM, Pauli Virtanen wrote: > Fri, 19 Aug 2011 12:48:29 +0200, Ralf Gommers wrote: > [clip] > > Hi Ognen, > > > > Could you please disable http access to numpy and scipy svn? > > Turns out also I had enough permissions to disable this. Now: > > $ svn co http://svn.scipy

Re: [Numpy-discussion] How to start at line # x when using numpy.memmap

On Fri, Aug 19, 2011 at 7:19 AM, Pauli Virtanen wrote: > Fri, 19 Aug 2011 07:00:31 -0600, Jeremy Conlin wrote: >> I would like to use numpy's memmap on some data files I have. The first >> 12 or so lines of the files contain text (header information) and the >> remainder has the numerical data. Is

Re: [Numpy-discussion] How to start at line # x when using numpy.memmap

Fri, 19 Aug 2011 07:00:31 -0600, Jeremy Conlin wrote: > I would like to use numpy's memmap on some data files I have. The first > 12 or so lines of the files contain text (header information) and the > remainder has the numerical data. Is there a way I can tell memmap to > skip a specified number o

[Numpy-discussion] How to start at line # x when using numpy.memmap

I would like to use numpy's memmap on some data files I have. The first 12 or so lines of the files contain text (header information) and the remainder has the numerical data. Is there a way I can tell memmap to skip a specified number of lines instead of a number of bytes? Thanks, Jeremy

Re: [Numpy-discussion] Build of current Git HEAD for NumPy fails

Hi Paeru, 2011/8/19 Pearu Peterson : > > > On 08/19/2011 02:26 PM, Dirk Ullrich wrote: >> Hi, >> >> when trying to build current Git HAED of NumPy with - both for >> $PYTHON=python2 or $PYTHON=python3: >> >> $PYTHON setup.py config_fc --fcompiler=gnu95 install --prefix=$WHATEVER >> >> I get the fo

Re: [Numpy-discussion] [SciPy-User] disabling SVN (was: Trouble installing scipy after upgrading to Mac OS X 10.7 aka Lion)

Fri, 19 Aug 2011 12:48:29 +0200, Ralf Gommers wrote: [clip] > Hi Ognen, > > Could you please disable http access to numpy and scipy svn? Turns out also I had enough permissions to disable this. Now: $ svn co http://svn.scipy.org/svn/numpy/trunk numpy svn: Repository moved permanently to 'http://

Re: [Numpy-discussion] Build of current Git HEAD for NumPy fails

On 08/19/2011 02:26 PM, Dirk Ullrich wrote: > Hi, > > when trying to build current Git HAED of NumPy with - both for > $PYTHON=python2 or $PYTHON=python3: > > $PYTHON setup.py config_fc --fcompiler=gnu95 install --prefix=$WHATEVER > > I get the following error - here for PYTHON=python3.2 The com

[Numpy-discussion] Build of current Git HEAD for NumPy fails

Hi, when trying to build current Git HAED of NumPy with - both for $PYTHON=python2 or $PYTHON=python3: $PYTHON setup.py config_fc --fcompiler=gnu95 install --prefix=$WHATEVER I get the following error - here for PYTHON=python3.2 running build_clib customize UnixCCompiler customize UnixCCompiler

Re: [Numpy-discussion] [SciPy-User] disabling SVN (was: Trouble installing scipy after upgrading to Mac OS X 10.7 aka Lion)

On Tue, Aug 16, 2011 at 3:01 PM, Pauli Virtanen wrote: > Sat, 13 Aug 2011 22:00:33 -0400, josef.pktd wrote: > [clip] > > Does Trac require svn access to dig out old information? for example > > links to old changesets, annotate/blame, ... ? > > It does not require HTTP access to SVN, as it looks