Re: [Numpy-discussion] Runtime error in numpy.polyfit

On Wed, May 19, 2010 at 3:50 PM, William Carithers wrote: > Hi David and Josef, > > OK, I updated to numpy-1.4.1 and scipy-0.7.2 and this problem went away. > Thanks for your help. > > BTW, trying to upgrade using the .dmg files from Sourceforge didn't work. > It &g

Re: [Numpy-discussion] Extending documentation to c code

On Mon, May 24, 2010 at 11:01 AM, Charles R Harris < charlesr.har...@gmail.com> wrote: > Hi All, > > I'm wondering if we could extend the current documentation format to the c > source code. The string blocks would be implemented something like > > /**NpyDoc > """The Answer. > > Answer the Ultimat

Re: [Numpy-discussion] Extending documentation to c code

On Mon, May 24, 2010 at 4:59 PM, Charles R Harris wrote: > > > On Mon, May 24, 2010 at 2:11 PM, David Goldsmith > wrote: > >> On Mon, May 24, 2010 at 11:01 AM, Charles R Harris < >> charlesr.har...@gmail.com> wrote: >> >>> Hi All, >

Re: [Numpy-discussion] Extending documentation to c code

signature would be enough, and writing this should not take too much time (Sebastien B wrote something which could be a start, to autogenerate cython code from header:http://bitbucket.org/binet/cylon). David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Extending documentation to c code

On Mon, May 24, 2010 at 8:06 PM, David Cournapeau wrote: > On Tue, May 25, 2010 at 3:01 AM, Charles R Harris > wrote: > > Hi All, > > > > I'm wondering if we could extend the current documentation format to the > c > > source code. The string bloc

Re: [Numpy-discussion] Extending documentation to c code

On Tue, May 25, 2010 at 2:09 PM, David Goldsmith wrote: > > This does sound promising/a good first step.  But it doesn't really answer > Charles' question about a standard (which would be useful to have to help > guide doc editor design). it does - I looked into synopsi

Re: [Numpy-discussion] Extending documentation to c code

On Tue, May 25, 2010 at 4:04 PM, Sebastien Binet wrote: > Excerpts from David Cournapeau's message of 2010-05-25 05:06:09 +0200: >> On Tue, May 25, 2010 at 3:01 AM, Charles R Harris > [snip] >> Maybe as a first step, something that could extract function signature >>

Re: [Numpy-discussion] Introduction to Scott, Jason, and (possibly) others from Enthought

sulting code would be layered, i.e., what is the design for this >> re-factoring. Simply having a design would be a major step forward. >> >> >> The problem with doing it in 2.1 is that this re-factoring will require >> extensions to be re-built. The visible interface t

Re: [Numpy-discussion] Extending documentation to c code

ng that is similar, ideally integrated into sphinx. It also generates rather ugly doc by default, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Introduction to Scott, Jason, and (possibly) others from Enthought

contain all the breaking changes. I am really worried about breaking things once now and once in a few months (or even a year). David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Introduction to Scott, Jason, and (possibly) others from Enthought

embedding within other languages, and the stack may be one solution for abstracting the reference counting (only the API around the stack and its implementation would need to be aware of a particular implementation of memory management). David > > While we have specific goals for the re-factorin

Re: [Numpy-discussion] Introduction to Scott, Jason, and (possibly) others from Enthought

On Tue, May 25, 2010 at 9:22 PM, Travis Oliphant wrote: > > On May 25, 2010, at 4:49 PM, David Goldsmith wrote: > > Travis: do you already have a place on the NumPy Development > Wiki<http://wiki.numpy.org/>where you're (b)logging your design decisions? > Seems li

Re: [Numpy-discussion] numpy and the Google App Engine

On Wed, May 26, 2010 at 10:37 AM, Christopher Hanley wrote: > On Wed, May 26, 2010 at 12:49 PM, Dag Sverre Seljebotn > wrote: > > Christopher Hanley wrote: > >> Greetings, > >> > >> Google provides a product called App Engine. The description from > >> their site follows, > >> > >> "Google App E

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

first column, then last column, first, etc. Happy debugging ! David H. On Fri, May 21, 2010 at 9:22 PM, David Warde-Farley wrote: > Confirmed in NumPy 1.4.1, Py 2.6.5. > > David > > On Fri, 21 May 2010, James Bergstra wrote: > >> Hi all, I'm wondering if this is a bug..

Re: [Numpy-discussion] Introduction to Scott, Jason, and (possibly) others from Enthought

about the authentification issues if any). Trac and buildbot could use a svn mirror as provided by github for the time being, although there seems to be an issue with the numpy repo ATM (maybe my fault: http://support.github.com/discussions/repos/3155-svn-checkout-error-200-ok-error) David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] curious about how people would feel about moving to github

e that branch...). Yet I do understand that any release candidate > can be pulled from any tree (as happens with the Linux kernel) and > that this should be more of guide than a fixed rule. The whole point of DVCS is that it is trivial to set up an official repo where the releases are done from, without preventing people to work as they see fit. cheers, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Help Convolution with binaural filters(HRTFs)

ing part, filtering in the time domain is way too consuming, because HRTF impulse responses are quite long, so you should use FFT (with windowing of course, using overlap add methods) David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Help Convolution with binaural filters(HRTFs)

igned 16 bits int range (~ [-32768, 32768]), but when you want to do processing in floating point (as does numpy), you want the values normalized (in the [-1, 1] range). 2 * 15 gives you the normalization factor. But audiolab does this for you automaticall

Re: [Numpy-discussion] Introduction to Scott, Jason, and (possibly) others from Enthought

On Thu, May 27, 2010 at 8:51 PM, Ralf Gommers wrote: > > > On Wed, May 26, 2010 at 12:23 PM, Travis Oliphant > wrote: >> >> On May 25, 2010, at 5:06 PM, David Cournapeau wrote: >> >> > On Wed, May 26, 2010 at 6:19 AM, Charles R Harris >> > wrote

Re: [Numpy-discussion] Extending documentation to c code

On Thu, May 27, 2010 at 9:18 AM, Charles R Harris wrote: > > On Wed, May 26, 2010 at 8:14 AM, Pauli Virtanen wrote: > >> Wed, 26 May 2010 07:15:08 -0600, Charles R Harris wrote: >> > On Wed, May 26, 2010 at 2:59 AM, Pauli Virtanen wrote: >> > >> &g

Re: [Numpy-discussion] Help Convolution with binaural filters(HRTFs)

x-i686.egg/audiolab/soundio/play.py:48: > UserWarning: Could not import alsa backend; most probably, you did not have > alsa headers when building audiolab How did you install it ? Your installation looks bogus (if you build it by yourself, please give the *exa

Re: [Numpy-discussion] Finding Star Images on a Photo (Video chip) Plate?

On Fri, May 28, 2010 at 8:31 PM, Anne Archibald wrote: > On 28 May 2010 23:59, Wayne Watson wrote: > > That opened a few avenues. After reading this, I went on a merry search > with > > Google. I hit upon one interesting book, Handbook of CCD astronomy (Steve > B. > > Howell), that discusses PSFs

Re: [Numpy-discussion] Introduction to Scott, Jason, and (possibly) others from Enthought

7;s not too much to merge, most of the changes ( > http://docs.scipy.org/numpy/patch/) don't apply cleanly or at all. The > latter because they're docs for constants, lists, etc. > > The biggest chuck of recent changes is for the polynomial and chebyshev > docs, can you g

[Numpy-discussion] Technicalities of the SVN -> GIT transition

ut from svn. The master branch (the "trunk" in git) has ~ 6500 commits. cheers, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Technicalities of the SVN -> GIT transition

hu ptvirtan rc rgommers rkern sasha skip stefan test tim_hochberg timl travis travo wfspotz (for wfspotz and matthew.brett, I removed the email suffix). I guess rkern and kern are the same person, as well as travo/oliphant. cheers, David ___ NumPy-Disc

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

ees, there aren't that many versions to compute beforehand. David On Thu, Jun 3, 2010 at 6:49 AM, arthur de conihout < arthurdeconih...@gmail.com> wrote: > Hello everybody > > i m fighting with a dynamic binaural synthesis(can give more hints on it if > necessary). > > i

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

n issue. To do convolution quickly, you need to use FFT, which is a bit tricky if you want to do things in real-time, as you need to partition the impulse response. Using "partitioned impulse answer" as keywords should give you plenty of references

Re: [Numpy-discussion] C vs. Fortran order -- misleading documentation?

On Mon, Jun 7, 2010 at 4:52 AM, Pavel Bazant wrote: > Correct me if I am wrong, but the paragraph > > Note to those used to IDL or Fortran memory order as it relates to > indexing. Numpy uses C-order indexing. That means that the last index > usually (see xxx for exceptions) represents the most r

Re: [Numpy-discussion] Is there really a moderator that reviews posts?

On Tue, Jun 8, 2010 at 12:10 AM, Sebastian Haase wrote: > I don't want to complain > But what is wrong with a limit of 40kB ? There are enough places where > one could upload larger files for everyone interested... > Not everyone knows about 'em, though - can you list some here, please. Than

Re: [Numpy-discussion] C vs. Fortran order -- misleading documentation?

On Tue, Jun 8, 2010 at 8:27 AM, Pavel Bazant wrote: > > > > Correct me if I am wrong, but the paragraph > > > > > > Note to those used to IDL or Fortran memory order as it relates to > > > indexing. Numpy uses C-order indexing. That means that the last index > > > usually (see xxx for exceptions)

Re: [Numpy-discussion] Is there really a moderator that reviews posts?

On Tue, Jun 8, 2010 at 8:43 AM, John Hunter wrote: > On Tue, Jun 8, 2010 at 10:33 AM, Sebastian Haase > wrote: > > On Tue, Jun 8, 2010 at 5:23 PM, David Goldsmith > wrote: > >> On Tue, Jun 8, 2010 at 12:10 AM, Sebastian Haase > >> wrote: > >>>

Re: [Numpy-discussion] C vs. Fortran order -- misleading documentation?

On Tue, Jun 8, 2010 at 12:05 PM, Anne Archibald wrote: > On 8 June 2010 14:16, Eric Firing wrote: > > On 06/08/2010 05:50 AM, Charles R Harris wrote: > >> > >> > >> On Tue, Jun 8, 2010 at 9:39 AM, David Goldsmith < > d.l.goldsm...@gmail.com &g

Re: [Numpy-discussion] C vs. Fortran order -- misleading documentation?

On Tue, Jun 8, 2010 at 1:56 PM, Benjamin Root wrote: > > On Tue, Jun 8, 2010 at 1:36 PM, Eric Firing wrote: > >> On 06/08/2010 08:16 AM, Eric Firing wrote: >> > On 06/08/2010 05:50 AM, Charles R Harris wrote: >> >> >> >> On Tue, Jun 8,

Re: [Numpy-discussion] C vs. Fortran order -- misleading documentation?

On Tue, Jun 8, 2010 at 3:49 PM, Friedrich Romstedt < friedrichromst...@gmail.com> wrot > 2010/6/8 Anne Archibald : > > Numpy arrays can have any configuration of memory strides, including > > some that are zero; C and Fortran contiguous arrays are simply those > > that have special arrangements of

Re: [Numpy-discussion] C vs. Fortran order -- misleading documentation?

ime, although I'd say that Fortran is a bit older). Fortran is the oldest language I am aware of - certainly the oldest still widely in use. it is even older than Lisp, the first version is from 1956-57, and was proposed by Backus to IBM in 53 according to wikipedia. It w

Re: [Numpy-discussion] C vs. Fortran order -- misleading documentation?

On Thu, Jun 10, 2010 at 12:09 AM, Benjamin Root wrote: >> I think that arrays are just syntax on pointer is indeed the key >> reason for how C works here. Since a[b] really means a + b (which is >> why 5[a] and a[5] are the same), I don't see how to do it differently. > > Holy crap!  You can do th

Re: [Numpy-discussion] C vs. Fortran order -- misleading documentation?

On Wed, Jun 9, 2010 at 9:00 AM, David Cournapeau wrote: > On Thu, Jun 10, 2010 at 12:09 AM, Benjamin Root wrote: > >> I think that arrays are just syntax on pointer is indeed the key > >> reason for how C works here. Since a[b] really means a + b (which is > >>

Re: [Numpy-discussion] yet another scipy Install problem

On Thu, Jun 10, 2010 at 1:16 PM, Bino Oetomo wrote: > Dear All .. > I tried to install numpy and scipy ... basicaly I want to use OMPC You need at least numpy 1.4 to build scipy from current svn, David ___ NumPy-Discussion mailing list

Re: [Numpy-discussion] NumPy re-factoring project

d when reimplementing lfilter was "copy-in copy-out" > for strided arrays. What is copy-in copy out ? I am not familiar with this term ? David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] NumPy re-factoring project

rk as python (very dynamic ala smalltalk) and uses a GC, which means the allocation strategy used in basekit is viable for VM which do not depend on reference counting. David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] NumPy re-factoring project

On Fri, Jun 11, 2010 at 7:25 AM, Sturla Molden wrote: > Den 10.06.2010 22:07, skrev Travis Oliphant: >> >>> 2. The core should be a plain DLL, loadable with ctypes. (I know David >>> Cournapeau and Robert Kern is going to hate this.) But if Python can have a >>&

Re: [Numpy-discussion] NumPy re-factoring project

reason I see for C++ is the possibility to use meta programming which > is very ill-designed. I'd rather like to see some simple code > preprocessing on C code than > C++ template meta programming. I don't think anyone is seriously considering changing languages. Especially if interoperation is desired, C is miles ahead of C++ anyway. David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] NumPy re-factoring project

On Sun, Jun 13, 2010 at 2:00 AM, Sturla Molden wrote: > Den 12.06.2010 15:57, skrev David Cournapeau: >> Anything non trivial will require memory allocation and object >> ownership conventions. If the goal is interoperation with other >> languages and vm, you may want to us

Re: [Numpy-discussion] NumPy re-factoring project

sting buffering without allocating in the library ? I don't see how that's possible. Before calling things stupid, you better have a solution to those issues, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Tensor contraction

Is this not what core.numeric.tensordotdoes? DG On Sun, Jun 13, 2010 at 12:37 PM, Friedrich Romstedt < friedrichromst...@gmail.com> wrote: > 2010/6/13 Alan Bromborsky : > > I am writing symbolic tensor package for general relativity

Re: [Numpy-discussion] Installing numpy on py 3.1.2 , osx

e.py", line 142 > print "%s version %s" % (os.path.basename(sys.argv[0]), __version__) > You need to install a nose version compatible with python 3 David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Error while upgrading to numpy 1.4.1

gfortran and libatlas-base-dev. I would also strongly discourage you to use easy_install on 10.04. The version in ubuntu 10.04 uses distribute which is buggier than setuptools at this point (sic), cheers, David ___ NumPy-Discussion mailing list NumP

[Numpy-discussion] SciPy docs marathon

wrong in the process. If you can help, please, now is the time to step forward. Thanks! On behalf of Joe and myself, David Goldsmith Olympia, WA ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Ufunc memory access optimization

he iterator overhead could be important: I unfortunately don't have much time to look into the code ATM, but tests should be run with different CPU. When I implemented the neighborhood iterator, I observed significant (somtimes several tens of %) differences - the gcc version also matte

[Numpy-discussion] SciPy docs marathon: a little more info

On Mon, Jun 14, 2010 at 2:05 AM, David Goldsmith wrote: > Hi, all! The scipy doc marathon has gotten off to a very slow start this > summer. We are producing less than 1000 words a week, perhaps because > many universities are still finishing up spring classes. So, this is > a seco

Re: [Numpy-discussion] ImportError: /usr/lib/python2.6/dist-packages/numpy/core/multiarray.so: undefined symbol: NPY_COPY_PYOBJECT_PTR

ian splits the numpy package and installed the headers in /usr/include, which breaks the build of pretty much every python extension out there (as it causes a change in header inclusion). The missing symbol is a macro defined in our public header, and is relat

[Numpy-discussion] SciPy docs marathon: a little more info

On Mon, Jun 14, 2010 at 2:05 AM, David Goldsmith wrote: > Hi, all! The scipy doc marathon has gotten off to a very slow start this > summer. We are producing less than 1000 words a week, perhaps because > many universities are still finishing up spring classes. So, this is > a seco

Re: [Numpy-discussion] Numpy.linalg.eig oddity

Is it not possible to update your versions to see if that solves the problem? DG On Wed, Jun 23, 2010 at 11:25 AM, Salim, Fadhley (CA-CIB) < fadhley.sa...@ca-cib.com> wrote: > I've been investigating a truly bizarre bug related to the use of > numpy.linalg.eig. > > I have two classes which both

Re: [Numpy-discussion] Numpy.linalg.eig oddity

On Wed, Jun 23, 2010 at 2:17 PM, Robert Kern wrote: > On Wed, Jun 23, 2010 at 13:25, Salim, Fadhley (CA-CIB) > wrote: > > I've been investigating a truly bizarre bug related to the use of > > numpy.linalg.eig. > > > > I have two classes which both use numpy.linalg.eig. These classes are > > used

Re: [Numpy-discussion] Documentation error in numpy.random.logseries

On Sat, Jun 26, 2010 at 1:41 PM, Vincent Davis wrote: > numpy.random.logseries(p, size=None) > > but the parameters section, > Parameters: > loc : float > scale : float > 0. > size : {tuple, int} > Output shape. If the given shape is, e.g., (m, n, k), then m * n * k > samples are drawn. > > Notice

Re: [Numpy-discussion] numpy.random.poisson docs missing "Returns"

Something is systematically wrong if there are this many problems in the numpy.stats docstrings: numpy is supposed to be (was) almost completely ready for review; please focus on scipy unless/until the reason why there are now so many problems in numpy.stats can be determined (I suspect the numpy.s

Re: [Numpy-discussion] numpy.random.poisson docs missing "Returns"

On Sat, Jun 26, 2010 at 3:03 PM, wrote: > On Sat, Jun 26, 2010 at 5:56 PM, David Goldsmith > wrote: > > Something is systematically wrong if there are this many problems in the > > numpy.stats docstrings: numpy is supposed to be (was) almost completely > > ready for

Re: [Numpy-discussion] numpy.random.poisson docs missing "Returns"

On Sat, Jun 26, 2010 at 3:28 PM, Vincent Davis wrote: > On Sat, Jun 26, 2010 at 4:22 PM, wrote: > > On Sat, Jun 26, 2010 at 6:11 PM, David Goldsmith > > wrote: > >> On Sat, Jun 26, 2010 at 3:03 PM, wrote: > >>> > >>> On Sat, Jun 2

Re: [Numpy-discussion] numpy.random.poisson docs missing "Returns"

On Sat, Jun 26, 2010 at 3:22 PM, wrote: > On Sat, Jun 26, 2010 at 6:11 PM, David Goldsmith > wrote: > > On Sat, Jun 26, 2010 at 3:03 PM, wrote: > >> > >> On Sat, Jun 26, 2010 at 5:56 PM, David Goldsmith > >> wrote: > >> > Something is syst

[Numpy-discussion] Strange behavior of np.sinc

Hi! The docstring for numpy.lib.function_base.sinc indicates that the parameter has to be an ndarray, and that it will return the limiting value 1 for sinc(0). Checking to see if it should actually say array_like, I found the following (Python 2.6): >>> np.sinc(np.array((0,0.5))) array([ 1.

Re: [Numpy-discussion] Strange behavior of np.sinc

On Sat, Jun 26, 2010 at 9:39 PM, Robert Kern wrote: > On Sat, Jun 26, 2010 at 23:33, David Goldsmith > wrote: > > Hi! The docstring for numpy.lib.function_base.sinc indicates that the > > parameter has to be an ndarray, and that it will return the limiting > value 1 >

Re: [Numpy-discussion] Strange behavior of np.sinc

On Sat, Jun 26, 2010 at 10:00 PM, David Goldsmith wrote: > On Sat, Jun 26, 2010 at 9:39 PM, Robert Kern wrote: > >> On Sat, Jun 26, 2010 at 23:33, David Goldsmith >> wrote: >> > Hi! The docstring for numpy.lib.function_base.sinc indicates that the >> > para

Re: [Numpy-discussion] arr.copy(order='F') doesn't agree with docstring: what is intended behavior?

On Sun, Jun 27, 2010 at 10:38 AM, Kurt Smith wrote: > On Sat, Jun 26, 2010 at 7:34 PM, Warren Weckesser > wrote: > > Kurt Smith wrote: > >> I'd really like arr.copy(order='F') to work -- is it supposed to as > >> its docstring says, or is it supposed to raise a TypeError as it does > >> now? > >

Re: [Numpy-discussion] numpy.random.poisson docs missing "Returns"

On Sun, Jun 27, 2010 at 3:44 AM, Pauli Virtanen wrote: > Sat, 26 Jun 2010 17:37:22 -0700, David Goldsmith wrote: > > On Sat, Jun 26, 2010 at 3:22 PM, wrote: > [clip] > >> Is there a chance that some changes got lost? > > > > (Almost) anything's possible...

Re: [Numpy-discussion] Is numpy ignoring CFLAGS?

On Mon, Jun 28, 2010 at 6:56 PM, Dr. David Kirkby wrote: > On 06/28/10 09:38 AM, Dag Sverre Seljebotn wrote: >> Dr. David Kirkby wrote: >>> On some 64-bit platforms, which include, but is not limited to: >>> >>>    * Some version of OS X (I don't know what

Re: [Numpy-discussion] Is numpy ignoring CFLAGS?

On Mon, Jun 28, 2010 at 9:28 PM, Dr. David Kirkby wrote: > On 06/28/10 11:28 AM, David Cournapeau wrote: >> On Mon, Jun 28, 2010 at 6:56 PM, Dr. David Kirkby > >>> Many other parts of Sage seem to inherit the flags ok from Python, but not >>> numpy. >> >

[Numpy-discussion] Ticket #1223...

...concerns the behavior of numpy.random.multivariate_normal; if that's of interest to you, I urge you to take a look at the comments (esp. mine :-) ); otherwise, please ignore the noise. Thanks! DG ___ NumPy-Discussion mailing list NumPy-Discussion@sci

Re: [Numpy-discussion] Ticket #1223...

On Tue, Jun 29, 2010 at 3:56 PM, wrote: > On Tue, Jun 29, 2010 at 6:37 PM, David Goldsmith > wrote: > > ...concerns the behavior of numpy.random.multivariate_normal; if that's > of > > interest to you, I urge you to take a look at the comments (esp. mine :-) > );

[Numpy-discussion] numpy.all docstring reality check

Hi, folks. Under Parameters, the docstring for numpy.core.fromnumeric.all says: "out : ndarray, optionalAlternative output array in which to place the result. It must have the same shape as the expected output and *the type is preserved*." [emphasis added].I assume this is a copy-and-paste-from-a

Re: [Numpy-discussion] numpy.all docstring reality check

OK, now I understand: dtype(out) is preserved, whatever that happens to be, not dtype(a) (which is what I thought it meant) - I better clarify. Thanks! DG On Tue, Jun 29, 2010 at 7:28 PM, Skipper Seabold wrote: > On Tue, Jun 29, 2010 at 8:50 PM, David Goldsmith > wrote: > > Hi, f

Re: [Numpy-discussion] Ticket #1223...

On Tue, Jun 29, 2010 at 8:16 PM, Bruce Southey wrote: > On Tue, Jun 29, 2010 at 6:03 PM, David Goldsmith > wrote: > > On Tue, Jun 29, 2010 at 3:56 PM, wrote: > >> > >> On Tue, Jun 29, 2010 at 6:37 PM, David Goldsmith > >> wr

Re: [Numpy-discussion] Ticket #1223...

On Thu, Jul 1, 2010 at 9:11 AM, Charles R Harris wrote: > > On Thu, Jul 1, 2010 at 8:40 AM, Bruce Southey wrote: > >> On 06/29/2010 11:38 PM, David Goldsmith wrote: >> >> On Tue, Jun 29, 2010 at 8:16 PM, Bruce Southey wrote: >> >>> On Tue, Jun 29, 2

[Numpy-discussion] where support full broadcasting, right?

Hi. The docstring (in the wiki) for where states: x, y : array_like, optionalValues from which to choose. *x* and *y* need to have the same shape as *condition*.But: >>> x = np.eye(2) >>> np.where(x,2,3) array([[2, 3], [3, 2]]) So apparently where supports broadcasting of scalars at least

Re: [Numpy-discussion] [ANN] Bento (ex-toydist) 0.0.3

as likely to be trademarked. But IANAL... cheers, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] OT: request help building pymex win64

cent, it is actually quite likely to be compiled with VS 2005, which means you should use python 2.5 instead (or built python2.6 with VS 2005, but I am not sure it is even possible without herculean efforts). David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] OT: request help building pymex win64

On Sat, Jul 3, 2010 at 1:58 AM, Robin wrote: > On Fri, Jul 2, 2010 at 5:47 PM, David Cournapeau wrote: >> >> The problem may be that matlab is built with one runtime, and Python >> with another Unless your matlab is very recent, it is actually >> quite likely

Re: [Numpy-discussion] numpy on windows 64 bit

www.lfd.uci.edu/~gohlke/pythonlibs/ > > I noticed that on windows sys.maxint is the 32bit value (2147483647 This is not surprising: sys.maxint gives you the max value of a long, which is 32 bits even on 64 bits on windows. David ___ NumPy-Discussion

Re: [Numpy-discussion] OT? Distutils extension with shared libs

;, '-pedantic', '-g', '-v']) > > it builds a _im7.pyd file that ctypes is not able to load as it > expects a _im7.dll file with > ctypes.cdll.loadlibrary('_im7')... You cannot build a library loadable with ctypes with distutils nor numpy.distut

[Numpy-discussion] effect of shape=None (the default) in format.open_memmap

Hi, I'm trying to wrap my brain around the affect of leaving shape=None (the default) in format.open_memmap. First, I get that it's only even seen if the file is opened in write mode. Then, write_array_header_1_0 is called with dict d as second parameter, w/, as near as I can see, d['shape'] stil

[Numpy-discussion] finfo.eps v. finfo.epsneg

>>> np.finfo('float64').eps # returns a scalar 2.2204460492503131e-16 >>> np.finfo('float64').epsneg # returns an array array(1.1102230246251565e-16) Bug or feature? DG ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/m

Re: [Numpy-discussion] TypeError when using double , longdouble in numpy.dot

e('longdouble').dtype.num > 13 >>>> numpy.array([1.0]).astype('longdouble').dtype.num > 12 This is unexpected. There maybe some untested/buggy codepaths for the windows case (where sizeof(double) == sizeof(long double)). I will try to look into it, but please p

[Numpy-discussion] Fwd: effect of shape=None (the default) in format.open_memmap

No reply? -- Forwarded message -- From: David Goldsmith Date: Tue, Jul 6, 2010 at 7:03 PM Subject: effect of shape=None (the default) in format.open_memmap To: numpy-discussion@scipy.org Hi, I'm trying to wrap my brain around the affect of leaving shape=None (the defaul

[Numpy-discussion] "Nyquist frequency" in numpy.fft docstring

Hi! I'm a little confused: in the docstring for numpy.fft we find the following: "For an even number of input points, A[n/2] represents both positive and negative Nyquist frequency..." but according to http://en.wikipedia.org/wiki/Nyquist_frequency (I know, I know, I've bad mouthed Wikipedia in

[Numpy-discussion] Another reality check

In numpy.fft we find the following: "Then A[1:n/2] contains the positive-frequency terms, and A[n/2+1:] contains the negative-frequency terms, in order of decreasingly negative frequency." Just want to confirm that "decreasingly negative frequency" means ..., A[n-2] = A_(-2), A[n-1] = A_(-1), as

Re: [Numpy-discussion] Another reality check

On Sun, Jul 11, 2010 at 6:18 PM, David Goldsmith wrote: > In numpy.fft we find the following: > > "Then A[1:n/2] contains the positive-frequency terms, and A[n/2+1:]contains > the negative-frequency terms, in order of decreasingly negative > frequency." >

Re: [Numpy-discussion] Another reality check

Thanks, both. On Mon, Jul 12, 2010 at 5:39 AM, Fabrice Silva wrote: > Le lundi 12 juillet 2010 à 18:14 +1000, Jochen Schröder a écrit : > > On 07/12/2010 12:36 PM, David Goldsmith wrote: > > > On Sun, Jul 11, 2010 at 6:18 PM, David Goldsmith > > > mailto:d.l.

[Numpy-discussion] numpy.fft, yet again

>From the docstring: "A[0] contains the zero-frequency term (the mean of the signal)" And yet, consistent w/ the definition given in the docstring (and included w/ an earlier email), the code gives, e.g.: >>> import numpy as np >>> x = np.ones((16,)); x array([ 1., 1., 1., 1., 1., 1., 1.,

Re: [Numpy-discussion] numpy.fft, yet again

On Mon, Jul 12, 2010 at 3:04 PM, Eric Firing wrote: > On 07/12/2010 11:43 AM, David Goldsmith wrote: > > >From the docstring: > > > > "A[0] contains the zero-frequency term (the mean of the signal)" > > > > And yet, consistent w/ the definition

[Numpy-discussion] Here's what I've done to numpy.fft

In light of my various questions and the responses thereto, here's what I've done (but not yet committed) to numpy.fft. There are many ways to define the DFT, varying in the sign of the exponent, normalization, etc. In this implementation, the DFT is defined as .. math:: A_k = \sum_{m=0}^{n-

Re: [Numpy-discussion] Here's what I've done to numpy.fft

On Mon, Jul 12, 2010 at 6:33 PM, Travis Oliphant wrote: > > On Jul 12, 2010, at 5:47 PM, David Goldsmith wrote: > > > In light of my various questions and the responses thereto, here's what > I've done (but not yet committed) to numpy.fft. > > > > There are

Re: [Numpy-discussion] numpy.fft, yet again

2010/7/12 Jochen Schröder > On 13/07/10 08:04, Eric Firing wrote: > > On 07/12/2010 11:43 AM, David Goldsmith wrote: > >> > From the docstring: > >> > >> "A[0] contains the zero-frequency term (the mean of the signal)" > >> > >>

Re: [Numpy-discussion] Here's what I've done to numpy.fft

2010/7/12 Jochen Schröder > On 13/07/10 08:47, David Goldsmith wrote: > > In light of my various questions and the responses thereto, here's what > > I've done (but not yet committed) to numpy.fft. > > > > There are many ways to define the DFT, va

Re: [Numpy-discussion] HOWTO build NumPy without external math libs

, even if > they are detected ? Are there any undocumented options I can pass to > setup.py ? (`setup.py build --help` didn't report anything.) BLAS=None LAPACK=None ATLAS=None python setup.py build David ___ NumPy-Discussion mailing list

Re: [Numpy-discussion] numpy.fft, yet again

On Mon, Jul 12, 2010 at 8:26 PM, David Goldsmith wrote: > 2010/7/12 Jochen Schröder > >> On 13/07/10 08:04, Eric Firing wrote: >> > On 07/12/2010 11:43 AM, David Goldsmith wrote: >> >> > From the docstring: >> >> >> >> &q

Re: [Numpy-discussion] numpy.fft, yet again

On Thu, Jul 15, 2010 at 3:20 AM, Martin Raspaud wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > David Goldsmith skrev: > > > > > > Interesting comment: it made me run down the fftpack tutorial > > <http://docs.scipy.org/sci

Re: [Numpy-discussion] Python 2.7 MSI installer for NumPy

son who would like this - it was discussed > here just 9 days ago, thread title "A release for python 2.7?", and > the conclusion was we'd have to wait for Numpy 1.5, probably in > August. It seems that building from the 1.4.x branch works out of the

Re: [Numpy-discussion] numpy for Python 3?

1436.html > > I'm afraid I need some help with that page. I'm interested in if you are not comfortable with svn, I would advise you to just wait for binaries. Building numpy on windows is not so easy, David ___ NumPy-Discussion mailing l

Re: [Numpy-discussion] Numpy 1.4.1 fails to build on (Debian) alpha and powepc

tage. Do you have shell access to the machines ? It would makes the work much easier for me to fix those issues, David ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] numpy for Python 3?

7;t mine having this limited version of >>>> 2008. >>> >>> You need Visual Studio 2008 Express Edition. Visual Basic 2008 Express >>> Edition is just a component of Visual Studio and does not have the C >>> compil

<    5   6   7   8   9   10   11   12   13   14   >