Re: [Numpy-discussion] Fortran 90 Library and .mod files numpy.distutils

include in their code to >> recreate the modules. Yet another way is to use submodules, but that >> feature is not available in Fortran 90. >> > > > ___ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/listin

Re: [Numpy-discussion] need a better way to fill a grid

Hi John, Since you have a regular grid, you should be able to find the x and y indices without np.where, ie something like I = (lon-grid.outlon0 / grid.dx).astype(int) J = (lat-grid.outlat0 / grid.dy).astype(int) for i, j, e in zip(I, J, emissions): Z[i,j] += e David On Mon, Jan 24, 2011

Re: [Numpy-discussion] read ascii file from complex fortran format() -- genfromtxt

Have you tried http://code.google.com/p/python-fortranformat/ It's not officially released yet but it's probably worth a try. David H. On Tue, Sep 21, 2010 at 8:25 AM, Andrew Jaffe wrote: > Hi all, > > I've got an ascii file with a relatively complicated structure, > originally written by for

Re: [Numpy-discussion] numpy histogram normed=True (bug / confusing behavior)

On Tue, Aug 31, 2010 at 7:02 AM, Ralf Gommers wrote: > > > On Tue, Aug 31, 2010 at 3:44 AM, David Huard wrote: > >> >> I just added a warning alerting concerned users (r8674), so this takes >> care of the bug fix and Nils wish to avoid a silent change in behavior.

Re: [Numpy-discussion] numpy histogram normed=True (bug / confusing behavior)

enjamin Root wrote: > >> > > >> > On Mon, Aug 30, 2010 at 8:29 AM, David Huard > >> > wrote: > >> >> > >> >> Thanks for the feedback, > >> >> As far as I understand it, the proposition is to keep histogram as it &

Re: [Numpy-discussion] numpy histogram normed=True (bug / confusing behavior)

o include the bug fix (with a warning) in the upcoming 1.5 release. David H. On Mon, Aug 30, 2010 at 11:50 AM, wrote: > On Mon, Aug 30, 2010 at 11:39 AM, Bruce Southey > wrote: > > On 08/30/2010 09:19 AM, Benjamin Root wrote: > > > > On Mon, Aug 30, 2010 at 8:29 AM, Davi

Re: [Numpy-discussion] numpy histogram normed=True (bug / confusing behavior)

ug 27, 2010 at 2:47 PM, Robert Kern < > robert.k...@gmail.com> > >>>> ? ?wrote: > >>>> > >>>> ? ? ?On Fri, Aug 27, 2010 at 15:32, David Huard < > david.hu...@gmail.com> > >>>> ? ? ?wrote: > >>>> ? ? ?> Nils

Re: [Numpy-discussion] numpy histogram normed=True (bug / confusing behavior)

Nils and Joseph, Thanks for the bug report, this is now fixed in SVN (r8672). Ralph. is this something that you want to see backported in 1.5 ? Regards, David On Fri, Aug 6, 2010 at 7:49 PM, wrote: > On Fri, Aug 6, 2010 at 4:53 PM, Nils Becker wrote: > > Hi again, > > > > first a correctio

Re: [Numpy-discussion] "Dynamic convolution" in Numpy

base(azimuth and elevation).I would love to be able to reduce the angle > thread under 5° which triggers around 1000 files to produce.For a 3Mb > original sound file, it becomes huge. > > Indeed ! I'll be curious to see what solutions ends up working best. Keep us posted. David &g

Re: [Numpy-discussion] "Dynamic convolution" in Numpy

Hi Arthur, I've no experience whatsoever with what you are doing, but my first thought was why don't you compute all possible versions beforehand and then progressively switch from one version to another by interpolation between the different versions. If the resolution is 15 degrees, there aren't

Re: [Numpy-discussion] Bug in frompyfunc starting at 10000 elements?

And in 2.0.0.dev8437. More hints: Assume has shape (N, Da) and b has shape (N, Db) * There is a problem wben N >= 1, Db=1 and Da > 1. * There is no problem when N >= 1, Da=1 and Db > 1. * The first row is OK, but for all others, there is one error per row, appearing in first column, then

Re: [Numpy-discussion] Aggregate memmap

Hi Matt, I don't think the memmap code support this. However, you can stack memmaps just as easily as arrays, so if you define individual memmaps for each slice and stack them (numpy.vstack), the resulting array will behave as a regular 3D array. HTH, David H. On Wed, Apr 21, 2010 at 3:41 PM,

Re: [Numpy-discussion] Sea Ice Concentrations from Nimbus-7 SMMR and DMSP SSM/I Passive Microwave Data

np.int8. > > (You can always do var = var.astype(np.int) *afterwards* to convert to a > bigger integer type.) > > Dag Sverre > ___ > NumPy-Discussion mailing list > NumPy-Discussion@scipy.org > http://mail.scipy.org/mailman/

Re: [Numpy-discussion] numpy 2.0, what else to do?

In the list of things to do, I suggest deleting completely the old histogram behaviour and the `new` keyword. The `new` keyword argument has raised a deprecation warning since 1.3 and was set for removal in 1.4. David H. On Mon, Feb 15, 2010 at 9:21 AM, Robert Kern wrote: > On Mon, Feb 15, 2010

Re: [Numpy-discussion] Removing datetime support for 1.4.x series ?

On Tue, Feb 2, 2010 at 9:23 PM, Neil Martinsen-Burrell wrote: > On 2010-02-02 19:53 , David Cournapeau wrote: >> Travis Oliphant wrote: >> >>> I think we just signal the breakage in 1.4.1 and move forward.   The >>> datetime is useful as a place-holder for data.  Math on date-time arrays >>> just

Re: [Numpy-discussion] How to get the shape of an array slice without doing it

For the record, here is what I came up with. import numpy as np def expand_ellipsis(index, ndim): """Replace the ellipsis, real or implied, of an index expression by slices. Parameters -- index : tuple Indexing expression. ndim : int Number of dimensions o

Re: [Numpy-discussion] Warning on http://scipy.org/ about binary incompatibility ?

I'm a heavy user of scikits.timeseries so I am very interested in having native datetime objects in Numpy. However, when I did play with it about a week ago. I found inconsistencies between the actual code and the NEP. The "Example of use" section mostly doesn't work. I understand the need to put

Re: [Numpy-discussion] How to get the shape of an array slice without doing it

On Fri, Jan 29, 2010 at 12:10 PM, wrote: > On Fri, Jan 29, 2010 at 11:49 AM, David Huard wrote: >> Hi, >> >> I have a 4D "array" with a given shape, but the array is never >> actually created since it is large and distributed over multiple >> binary f

[Numpy-discussion] How to get the shape of an array slice without doing it

Hi, I have a 4D "array" with a given shape, but the array is never actually created since it is large and distributed over multiple binary files. Typical usage would be to take slices across the 4D array. I'd like to know what the shape of the resulting array would be if I took a slice out of it.

[Numpy-discussion] Histogram - removing the "new" keyword for 1.4

etter. I'm sorry to bring this so late in the release cycle. Cheers, David Huard ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Convert data into rectangular grid

On Mon, Sep 28, 2009 at 8:45 PM, jah wrote: > On Mon, Sep 28, 2009 at 4:48 PM, wrote: > >> On Mon, Sep 28, 2009 at 7:19 PM, jah wrote: >> > Hi, >> > >> > Suppose I have a set of x,y,c data (something useful for >> > matplotlib.pyplot.plot() ). Generally, this data is not rectangular at >> > al

Re: [Numpy-discussion] MFDatasets and NetCDF4

Hi George, On Fri, Sep 25, 2009 at 6:55 AM, George Nurser wrote: > Hi, > I hope this is the right place to ask this. > I've found the MFDataset works well in reading NetCDF3 files, but it > appears that it doesn't work at present for NetCDF4 files. > > It works on my side for netCDF4 files. What

[Numpy-discussion] Fortran reader for npy files

Hi, Has someone written a fortran reader for the "npy" binary files numpy.save creates ? Thanks, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Faulty behavior of numpy.histogram?

On Wed, Aug 12, 2009 at 3:12 AM, Danny Handoko wrote: > Dear all, > > We try to use numpy.histogram with combination of matplotlib. We are using > numpy 1.3.0, but a somewhat older matplotlib version of 0.91.2. > Matplotlib's axes.hist() function calls the numpy.histogram, passing > through the

[Numpy-discussion] vectorize problem with f2py and gfortran 4.3

Hi all, A user on the pymc user list has reported a problem with f2py wrapped fortran functions compiled with gfortran 4.3, which is the standard Ubuntu Jaunty fortran compiler. I noticed the same bug in some of my own routines. The problem, as far as I can understand, is that vectorize tries to f

Re: [Numpy-discussion] Indexing with callables (was: Yorick-like functionality)

worth adding to the numpy namespace. David On Fri, May 15, 2009 at 4:47 PM, wrote: > On Fri, May 15, 2009 at 4:09 PM, David Huard > wrote: > > Pauli and David, > > > > Can this indexing syntax do things that are otherwise awkward with the > > current synta

Re: [Numpy-discussion] Indexing with callables (was: Yorick-like functionality)

Pauli and David, Can this indexing syntax do things that are otherwise awkward with the current syntax ? Otherwise, I'm not warm to the idea of making indexing more complex than it is. getv : this is useful but it feels a bit redundant with numpy.take. Is there a reason why take could not support

Re: [Numpy-discussion] hairy optimization problem

Hi Mathew, You could use Newton's method to optimize for each vi sequentially. If you have an expression for the jacobian, it's even better. What I'd do is write a class with a method f(self, x, y) that records the result of f(x,y) each time it is called. I would then sample very coarsely the x,

Re: [Numpy-discussion] efficient 3d histogram creation

On Mon, May 4, 2009 at 4:18 PM, wrote: > On Mon, May 4, 2009 at 4:00 PM, Chris Colbert wrote: > > i'll take a look at them over the next few days and see what i can hack > out. > > > > Chris > > > > On Mon, May 4, 2009 at 3:18 PM, David Huard > wrote

Re: [Numpy-discussion] efficient 3d histogram creation

On Mon, May 4, 2009 at 7:00 AM, wrote: > On Mon, May 4, 2009 at 12:31 AM, Chris Colbert > wrote: > > this actually sort of worked. Thanks for putting me on the right track. > > > > Here is what I ended up with. > > > > this is what I ended up with: > > > > def hist3d(imgarray): > > histarray

Re: [Numpy-discussion] Changes and new workflow on Trac

Plain old firefox 3.0.6 on fedora 9. On Tue, Mar 10, 2009 at 4:11 PM, Charles R Harris wrote: > > > On Tue, Mar 10, 2009 at 2:07 PM, Stéfan van der Walt wrote: > >> 2009/3/10 David Huard : >> > but, if I try to login, I get the same error again. I tried to reset

Re: [Numpy-discussion] Changes and new workflow on Trac

On Tue, Mar 10, 2009 at 1:28 PM, David Huard wrote: > > > On Tue, Mar 10, 2009 at 9:44 AM, Stéfan van der Walt wrote: > >> Hi David >> >> 2009/3/10 David Huard : >> > Stefan, >> > >> > The SciPy site is really nice, but the NumPy si

Re: [Numpy-discussion] Changes and new workflow on Trac

On Tue, Mar 10, 2009 at 9:44 AM, Stéfan van der Walt wrote: > Hi David > > 2009/3/10 David Huard : > > Stefan, > > > > The SciPy site is really nice, but the NumPy site returns a Page Load > Error. > > Which page are you referring to? > > http://proje

Re: [Numpy-discussion] Changes and new workflow on Trac

Stefan, The SciPy site is really nice, but the NumPy site returns a Page Load Error. David On Mon, Mar 9, 2009 at 3:35 AM, Stéfan van der Walt wrote: > Hi all, > > Here is an outline of recent changes made to the Trac system. > > I have modified the ticket workflow on > projects.scipy.org/{

Re: [Numpy-discussion] GMRES internal variables

Nathan, First of all, thanks to all your work on the sparse linear algebra package, I am starting to use it and it's much appreciated. Just a thought: wouldn't it be more natural to write gmres as a class rather than a function ? That way, accessing the internal work arrays for reuse would be muc

Re: [Numpy-discussion] Bugs in histogram and matplotlib-hist

On Wed, Nov 12, 2008 at 1:27 PM, Mike Ressler <[EMAIL PROTECTED]>wrote: > On Wed, Nov 12, 2008 at 4:30 AM, Scott Sinclair <[EMAIL PROTECTED]> > wrote: > >> "Mike Ressler" <[EMAIL PROTECTED]> 11/12/08 1:19 AM > >> I did an update to a Fedora 9 workstation yesterday that included > >> updating numpy

[Numpy-discussion] Changes to histogram semantics: follow-up

DeprecationWarning. Users relying on the old behaviour are encouraged to switch to the new semantics. new=True warns users that the `new` keyword will disappear in 1.4 Regards, David Huard ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http

Re: [Numpy-discussion] Apply a vector function to each row of a matrix

On Thu, Oct 9, 2008 at 2:48 PM, Neal Becker <[EMAIL PROTECTED]> wrote: > David Huard wrote: > > > On Thu, Oct 9, 2008 at 9:40 AM, Neal Becker <[EMAIL PROTECTED]> wrote: > > > >> David Huard wrote: > >> > >> > Neal, > >>

Re: [Numpy-discussion] Apply a vector function to each row of a matrix

On Thu, Oct 9, 2008 at 9:40 AM, Neal Becker <[EMAIL PROTECTED]> wrote: > David Huard wrote: > > > Neal, > > > > Look at: apply_along_axis > > > > > I guess it'd be: > > b = empty_like(a) > for row in a.shape[0]: > b[row,:] = apply_al

Re: [Numpy-discussion] Apply a vector function to each row of a matrix

Neal, Look at: apply_along_axis David On Thu, Oct 9, 2008 at 8:04 AM, Neal Becker <[EMAIL PROTECTED]> wrote: > Suppose I have a function (I wrote in c++) that accepts a numpy 1-d vector. > What is the recommended way to apply it to each row of a matrix, returning > a new matrix result? (Assu

Re: [Numpy-discussion] Help to process a large data file

Frank, On Thu, Oct 2, 2008 at 3:20 PM, frank wang <[EMAIL PROTECTED]> wrote: > > Thans David and Chris for providing the nice solution. > > Glad it helped. > Both method works gread. I could not tell the speed difference between the > two solutions. My data size is 1048577 lines. > I'd be curi

Re: [Numpy-discussion] Help to process a large data file

Frank, How about that: x = np.loadtxt('file') z = x.sum(1) # Reduce data to an array of 0,1,2 rz = z[z>0] # Remove all 0s since you don't want to count those. loc = np.where(rz==2)[0] # The location of the (1,1)s count = np.diff(loc) - 1 # The spacing between those (1,1)s, ie, the numbe

Re: [Numpy-discussion] Upper and lower envelopes

On Tue, Sep 30, 2008 at 4:37 PM, Anne Archibald <[EMAIL PROTECTED]>wrote: > 2008/9/30 bevan <[EMAIL PROTECTED]>: > > Hello, > > > > I have some XY data. I would like to generate the equations for an upper > and > > lower envelope that excludes a percentage of the data points. > > > > I would like

Re: [Numpy-discussion] Upper and lower envelopes

Bevan, You can estimate the intercept and slope using least-squares (scipy.optimize.leastsq). Make sure though that errors in X are small compared to errors in Y, otherwise, your slope will be underestimated. Using the slope, you can write a function lower(b,a, X,Y) that will compute y=aX+b and r

Re: [Numpy-discussion] loadtxt error

Note that the fix was also backported to 1.2, for which binary builds are available: David [ copied from a recent thread ] The 1.2.0rc2 is now available: http://svn.scipy.org/svn/numpy/tags/1.2.0rc2 The source tarball is here: https://cirl.berkeley.edu/numpy/numpy-1.2.0rc2.tar.gz Here is the u

Re: [Numpy-discussion] loadtxt error

This bug has been fixed in the trunk a couple of weeks ago. Cheers, David On Mon, Sep 22, 2008 at 8:10 PM, Pierre GM <[EMAIL PROTECTED]> wrote: > On Monday 22 September 2008 19:56:47 frank wang wrote: > > This error is caused that the usecols is a tuple and it does not have > find > > command.

Re: [Numpy-discussion] Help speeding up element-wise operations for video processing

Brendan, Not sure if I understand correctly what you want, but ... Numpy vector operations are performed in C, so there will be an iteration over the array elements. For parallel operations over all pixels, you'd need a package that talks to your GPU, such as pyGPU. I've never tried it and if yo

Re: [Numpy-discussion] BUG in numpy.loadtxt?

Done in r5790. On Fri, Sep 5, 2008 at 12:36 PM, Ryan May <[EMAIL PROTECTED]> wrote: > David Huard wrote: > > Hi Ryan, > > > > I applied your patch in r5788 on the trunk. > > I noticed there was another bug occurring when both converters and > > usecols

Re: [Numpy-discussion] BUG in numpy.loadtxt?

Hi Ryan, I applied your patch in r5788 on the trunk. I noticed there was another bug occurring when both converters and usecols are provided. I've added regression tests for both bugs. Could you confirm that everything is fine on your side ? Thanks, On Thu, Sep 4, 2008 at 4:47 PM, Ryan May <[EMA

Re: [Numpy-discussion] 1.2 tasks

On Tue, Aug 5, 2008 at 1:36 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote: > On Tue, Aug 5, 2008 at 10:24 AM, Stéfan van der Walt <[EMAIL PROTECTED]> > wrote: > > Could you put in a check for new=True, and suppress those messages? A > > user that knows about the changes wouldn't want to see anythi

Re: [Numpy-discussion] 1.2 tasks

On Tue, Aug 5, 2008 at 1:18 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote: > On Tue, Aug 5, 2008 at 8:48 AM, David Huard <[EMAIL PROTECTED]> wrote: > > Thanks for the feedback. Here is what will be printed: > > > > If new=False > > > > The origi

Re: [Numpy-discussion] 1.2 tasks

On Tue, Aug 5, 2008 at 4:04 AM, Vincent Schut <[EMAIL PROTECTED]> wrote: > David Huard wrote: > > > > > > On Mon, Aug 4, 2008 at 1:45 PM, Jarrod Millman <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > > > Question:

Re: [Numpy-discussion] 1.2 tasks

On Mon, Aug 4, 2008 at 1:45 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote: > Here are the remaining tasks that I am aware of that need to be done > before tagging 1.2.0b1 on the 8th. > > Median > == > The call signature for median needs to change from > def median(a, axis=0, out=None, overwrit

Re: [Numpy-discussion] "import numpy" is slow

On Thu, Jul 31, 2008 at 1:12 PM, Christopher Barker <[EMAIL PROTECTED]>wrote: > David Cournapeau wrote: > > Christopher Barker wrote: > >> On my OS-X box (10.4.11, python2.5, numpy '1.1.1rc2'), it takes about 7 > >> seconds to import numpy! > > > > Hot or cold ? If hot, there is something horribly

Re: [Numpy-discussion] The date/time dtype and the casting issue

Hi, Silent casting is often a source of bugs and I appreciate the strict rules you want to enforce. However, I think there should be a simpler mechanism for operations between different types than creating a copy of a variable with the correct type. My suggestion is to have a dtype argument for m

Re: [Numpy-discussion] Schedule for 1.2.0

I think we should stick to what has been agreed and announced months ago. It's called honouring our commitments and the project's image depends on it. If the inconvenience of these API changes is worth the trouble, a 1.1.2 release could be considered. My two cents. David 2008/7/22 Joe Harringto

Re: [Numpy-discussion] 1.1.1rc1 to be tagged tonight

Ryan, I committed your patch to the trunk and added a test for it from your failing example. Jarrod, though I'm also wary to touch the branch so late, the patch is minor and I don't see how it could break something that was not already broken. David 2008/7/20 Ryan May <[EMAIL PROTECTED]>: > Jar

Re: [Numpy-discussion] numpy.loadtext() fails with dtype + usecols

Looks good to me. I committed the patch to the trunk and added a regression test (r5495). David 2008/7/18 Charles R Harris <[EMAIL PROTECTED]>: > > > On Fri, Jul 18, 2008 at 4:16 PM, Ryan May <[EMAIL PROTECTED]> wrote: > >> Hi, >> >> I was trying to use loadtxt() today to read in some text da

Re: [Numpy-discussion] Histogram bin definition

Hi Stefan, It's designed this way. The main reason is that the default bin edges are generated using linspace(a.min(), a.max(), bin) when bin is an integer. If we leave the rightmost edge open, then the histogram of a 100 items array will typically yield an histogram with 99 values because the

Re: [Numpy-discussion] Revised list of backport candidates for 1.1.1

The revision number for the backport of 5254 is 5419. David 2008/7/15 Charles R Harris <[EMAIL PROTECTED]>: > After the first round of backports the following remain. > > charris > r5259 > r5312 > r5322 > r5324 > r5392 > r5394 > r5399 > r5406 > r5407 > > dhuar

Re: [Numpy-discussion] RFC: A proposal for implementing some date/time types in NumPy

2008/7/14 Francesc Alted <[EMAIL PROTECTED]>: > [...] > > DateArray([14-Jan-2001 14:34:33, 16-Jan-2001 10:09:11], > > freq='S') > > That's great. However we only planned to import/export dates from the > ``datetime`` module for the time being, mainly because of efficency but > also simp

Re: [Numpy-discussion] nose changes checked in

2008/6/17 Anne Archibald <[EMAIL PROTECTED]>: > 2008/6/17 Alan McIntyre <[EMAIL PROTECTED]>: > > On Tue, Jun 17, 2008 at 9:26 AM, David Huard <[EMAIL PROTECTED]> > wrote: > >> I noticed that NumpyTest and NumpyTestCase disappeared, and now I am > >

Re: [Numpy-discussion] nose changes checked in

I noticed that NumpyTest and NumpyTestCase disappeared, and now I am wondering whether these classes part of the public interface or were they reserved for internal usage ? In the former, it might be well to deprecate them before removing them. Cheers, David 2008/6/17 David Cournapeau <[EMAIL P

Re: [Numpy-discussion] NumpyTest problem

umpyTest().test(all=False) works, but NumpyTest().test(all=True) doesn't, that is, it finds 0 test. David 2008/6/2 Charles R Harris <[EMAIL PROTECTED]>: > > > On Mon, Jun 2, 2008 at 9:20 AM, David Huard <[EMAIL PROTECTED]> wrote: > >> Hi, >> >> There

Re: [Numpy-discussion] Bug in numpy.histogram?

2008/6/9 Tommy Grav <[EMAIL PROTECTED]>: > I understand this and agree, but it still means that the API for > histogram is > broken since normed can only be used with the new=True parameter. I > though > the whole point of the future warning was to avoid this. It is not a > big deal, > just means

Re: [Numpy-discussion] NumpyTest problem

n stuff like that and make > it work properly if I can. > > Alan > > On Mon, Jun 2, 2008 at 11:20 AM, David Huard <[EMAIL PROTECTED]> > wrote: > > Hi, > > > > There are 2 problems with NumpyTest > > > > 1. It fails if the command is given the file n

Re: [Numpy-discussion] NumpyTest problem

numpy.test(level=10,all=0) seems to work fine. ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] NumpyTest problem

Hi, There are 2 problems with NumpyTest 1. It fails if the command is given the file name only (without a directory structure) E.g.: [EMAIL PROTECTED]:~/repos/numpy/numpy/tests$ python test_ctypeslib.py Traceback (most recent call last): File "test_ctypeslib.py", line 87, in NumpyTest().

Re: [Numpy-discussion] question about histogram2d

Hi Darren, If I remember correctly, the thinking under the current behavior is that it preserves similarity of results with histogramdd, where the histogram is oriented in the numpy order (columns, rows). I thought that making histogram2d(x,y) return something different than histogramdd([x,y]) was

Re: [Numpy-discussion] 1.1.0rc1 tagged

Ticket 793 has a patch, submitted by Alan McIntyre, waiting for review from someone C-API-wise. Cheers, David 2008/5/19 Neal Becker <[EMAIL PROTECTED]>: > Jarrod Millman wrote: > > > Please test the release candidate: > > svn co http://svn.scipy.org/svn/numpy/tags/1.1.0rc1 1.1.0rc1 > > > > Al

Re: [Numpy-discussion] let's use patch review

2008/5/14 David Cournapeau <[EMAIL PROTECTED]>: > On Wed, 2008-05-14 at 13:58 -1000, Eric Firing wrote: > > > > What does that mean? How does one know when there is a consensus? > > There can be a system to make this automatic. For example, the code is > never commited directly to svn, but to a g

Re: [Numpy-discussion] f2py and -D_FORTIFY_SOURCE=2 compilation flag

Works for me, Thanks David 2008/5/15 Pearu Peterson <[EMAIL PROTECTED]>: > > > Robert Kern wrote: > > On Wed, May 14, 2008 at 3:20 PM, David Huard <[EMAIL PROTECTED]> > wrote: > >> I filed a patch that seems to do the trick in ticket #792. > > >

Re: [Numpy-discussion] f2py and -D_FORTIFY_SOURCE=2 compilation flag

I filed a patch that seems to do the trick in ticket #792.<http://scipy.org/scipy/numpy/ticket/792> 2008/5/14 David Huard <[EMAIL PROTECTED]>: > Hi, > > On fedora 8, the docstrings of f2py generated extensions are strangely > missing. On Ubuntu, the same modules do

[Numpy-discussion] f2py and -D_FORTIFY_SOURCE=2 compilation flag

Hi, On fedora 8, the docstrings of f2py generated extensions are strangely missing. On Ubuntu, the same modules do have the docstrings. The problem, as reported in the f2py ML, seems to come from the -D_FORTIFY_SOURCE flag which is set to 2 instead of 1. Could this be fixed in numpy.distutils and

Re: [Numpy-discussion] numpy release

rrod Millman <[EMAIL PROTECTED]> > wrote: > > > On Fri, Apr 25, 2008 at 12:55 PM, David Huard <[EMAIL PROTECTED]> > > wrote: > > > > Done in r5085. I added a bunch of tests, but I'd appreciate if > > someone > > > could dou

Re: [Numpy-discussion] numpy release

2008/4/25 David Huard <[EMAIL PROTECTED]>: > 2008/4/24 Jarrod Millman <[EMAIL PROTECTED]>: > > > On Thu, Apr 24, 2008 at 1:22 PM, David Huard wrote: > > > Assuming we want the next version to : ignore values outside of range > > and > > > accept an

Re: [Numpy-discussion] numpy release

2008/4/24 Jarrod Millman <[EMAIL PROTECTED]>: > On Thu, Apr 24, 2008 at 1:22 PM, David Huard wrote: > > Assuming we want the next version to : ignore values outside of range > and > > accept and return the bin edges instead of the left edges, here could be > the > &

Re: [Numpy-discussion] Generating Bell Curves (was: Using normal() )

Other suggestions for bounded bell-shaped functions that reach zero on a finite interval: - Beta distribution: http://en.wikipedia.org/wiki/Beta_distribution - Cubic B-splines:http://www.ibiblio.org/e-notes/Splines/Basis.htm 2008/4/25 Bruce Southey <[EMAIL PROTECTED]>: > Rich Shepard wrote:

Re: [Numpy-discussion] numpy release

The problem I see with C is that it will break compatibility with the other histogram functions, which also use bins. So here is suggestion E: The most common use case ( I think) is the following: h, b = histogram(r, number_of_bins, normed=True/False) for which the function behaves correctly. As

Re: [Numpy-discussion] numpy release

2008/4/23, Stéfan van der Walt <[EMAIL PROTECTED]>: > > Hi Jarrod > > Of those tickets, the following are serious: > > http://projects.scipy.org/scipy/numpy/ticket/605 (a patch is > available?, David Huard) > Fixing of histogram. > I haven't found a

Re: [Numpy-discussion] packaging scipy (was Re: Simple financial functions for NumPy)

2008/4/9, Gael Varoquaux <[EMAIL PROTECTED]>: > > [snip] > > Some people do not want their scripts to scale or to last more than a day. And that's what Matlab is especially good at ! ; ) And I'll say the thing I'm dying to say since this started: If anybody other than Travis had suggested we put

Re: [Numpy-discussion] ticket #605

Hello Jarrod and co., here is my personal version of the histogram saga. The current version of histogram puts in the rightmost bin all values larger than range, but does not put in the leftmost bin all values smaller than bin, eg. In [6]: histogram([1,2,3,4,5,6], bins=3, range=[2,5]) Out[6]: (a

Re: [Numpy-discussion] Ticket #605 Incorrect behavior of numpy.histogram

2036854775808,1, 2, 3, -9223372036854775808]) In [29]: np.r_[-np.inf, asarray(dbin).astype(float), np.inf] Out[29]: array([-Inf, 1., 2., 3., Inf]) Is this a misuse of r_ or a bug ? David But I have not had time to find the error. > > Regards

Re: [Numpy-discussion] Ticket #605 Incorrect behavior of numpy.histogram

Hans, Note that the current histogram is buggy, in the sense that it assumes that all bins have the same width and computes db = bins[1]-bin[0]. This is why you get zeros everywhere. The current behavior has been heavily criticized and I think we should change it. My proposal is to have for histo

Re: [Numpy-discussion] Ticket #605 Incorrect behavior of numpy.histogram

> On Apr 7, 2008, at 4:14 PM, LB wrote: > > +1 for axis and +1 for a keyword to define what to do with values > > outside the range. > > > > For the keyword, ather than 'outliers', I would propose 'discard' or > > 'exclude', because it could be used to describe the four > > possibilities : > > - d

Re: [Numpy-discussion] packaging scipy (was Re: Simple financial functions for NumPy)

2008/4/4, Joe Harrington <[EMAIL PROTECTED]>: > > import numpy as N > import numpy.math as N.M > import numpy.trig as N.T > import numpy.stat as N.S I don't think the issue is whether to put everything in the base namespace // everything in individual namespace, but rather to find an optima

Re: [Numpy-discussion] Ticket #605 Incorrect behavior of numpy.histogram

+1 for an outlier keyword. Note, that this implies that when bins are passed explicitly, the edges are given (nbins+1), not simply the left edges (nbins). While we are refactoring histogram, I'd suggest adding an axis keyword. This is pretty straightforward to implement using the np.apply_along_ax

Re: [Numpy-discussion] loading data with gaps

Hi Tim, Look at the thread posted a couple of weeks ago named: loadtxt and missing values I'm guessing you'll find answers to your questions, if not, don't hesitate to ask. David 2008/4/3, Tim Michelsen <[EMAIL PROTECTED]>: > > Hello! > > How can I load a data file (e.g. CSV, DAT) in ASCII whi

Re: [Numpy-discussion] isnan bug?

Chris, The trac page is to place to file tickets. Note that you have to register first before you can file new tickets. David 2008/3/20, Chris Withers <[EMAIL PROTECTED]>: > > Hi All, > > I'm faily sure that: > > numpy.isnan(datetime.datetime.now()) > >

[Numpy-discussion] Proposed change to average function

he risk of unexpected results but wanted to know if anyone disagrees with the change. The proposed version is implemented in revision 4888. Regards, David Huard ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailma

Re: [Numpy-discussion] subset of array - statistics

Look at the timeseries package in scikits (only on svn i'm afraid). You'll find exactly what you're looking for. Conversion from daily to monthly or yearly time series is a breeze. Cheers, David 2008/3/13, Joris De Ridder <[EMAIL PROTECTED]>: > > > I am new to the world of Python and numpy > > >

Re: [Numpy-discussion] Help needed with numpy 10.5 release blockers

I added a test for ticket 691. Problem is, there seems to be a new bug. I don't know it its related to the change or if it was there before. Please check this out. David 2008/3/14, David Huard <[EMAIL PROTECTED]>: > > I added a test for ticket 690. > > 2008/3/13, Barry

Re: [Numpy-discussion] Help needed with numpy 10.5 release blockers

I added a test for ticket 690. 2008/3/13, Barry Wark <[EMAIL PROTECTED]>: > > I appologize that the Mac OSX buildbot has been so flakey. For some > reason it stops being able to resolve scipy.org on a regular basis > (though other processes on the same machine don't seem to have > trouble). Restar

Re: [Numpy-discussion] Transforming an array of numbers to an array of formatted strings

['S%03d'%i for i in int_data] David 2008/3/13, Alan G Isaac <[EMAIL PROTECTED]>: > > On Thu, 13 Mar 2008, Alexander Michael apparently wrote: > > I want to format an array of numbers as strings. > > > To what end? > Note that tofile has a format option. > And for 1d array ``x`` you can always do

Re: [Numpy-discussion] loadtxt broken if file does not end in newline

ne in enumerate(fh): if i: > > David Huard wrote: > > Would everyone be satisfied with a solution using regular expressions ? > > > Maybe it's because regular expressions make me itch, but I think it's > overkill for this. > > The issue here is a result

Re: [Numpy-discussion] loadtxt broken if file does not end in newline

Lisandro, When you have some time, could you check this patch solves your problem (and does not introduce new ones) ? David Index: numpy/lib/io.py === --- numpy/lib/io.py (revision 4824) +++ numpy/lib/io.py (working copy) @

Re: [Numpy-discussion] loadtxt broken if file does not end in newline

I can look at it. Would everyone be satisfied with a solution using regular expressions ? That is, looking for the following pattern: pattern = re.compile(r""" ^\s* # leading white space (.*) # Data %s? # Zero or one comment character (.*) # Comments \s*$ # Trailing white spa

Re: [Numpy-discussion] David's build_with_scons branch merged!

Jarrod and David, I am reporting a success on FC8, Xeon. Some tests don't pass, but I don't believe it is related to the build process. Well done, David 2008/2/8, Jarrod Millman <[EMAIL PROTECTED]>: > > Hello, > > In preparation for the upcoming NumPy 1.0.5 release, I just merged > David Courna

Re: [Numpy-discussion] histogramdd memory needs

2008/2/4, Lars Friedrich <[EMAIL PROTECTED]>: > > Hi, > > > 2) Is there a way to use another algorithm (at the cost of performance) > >> > that uses less memory during calculation so that I can generate > bigger > >> > histograms? > > > > > > You could work through your array block by block. Simply

Re: [Numpy-discussion] histogramdd memory needs

Hi Lars, [...] 2008/2/1, Lars Friedrich <[EMAIL PROTECTED]>: > > > 1) How can I tell histogramdd to use another dtype than float64? My bins > will be very little populated so an int16 should be sufficient. Without > normalization, a Integer dtype makes more sense to me. There is no way you'll b

  1   2   >