2008/10/3 David Bolme <[EMAIL PROTECTED]>:
> I remember reading a paper or book that stated that for data that has
> been normalized correlation and Euclidean are equivalent and will
> produce the same knn results. To this end I spent a couple hours this
> afternoon doing the math. This document
I remember reading a paper or book that stated that for data that has
been normalized correlation and Euclidean are equivalent and will
produce the same knn results. To this end I spent a couple hours this
afternoon doing the math. This document is the result.
http://www.cs.colostate.edu/~
Fri, 03 Oct 2008 18:59:02 +0200, Gael Varoquaux wrote:
> I am doing a calculation where one call numpy.dot ends up taking 90% of
> the time (the array is huge: (61373, 500) ).
>
> Any chance I can make this faster? I would believe BLAS/ATLAS would be
> behind this, but from my quick analysis (ldd
Thank you very much for the information!
There are weird but important reasons why we are stuck with Numeric 24.2 for the
foreseeable future. It is extremely valuable that you provide a smooth upgrade
path.
Ralf
- Original Message
From: Christopher Barker <[EMAIL PROTECTED]>
To: Discuss
Ralf W. Grosse-Kunstleve wrote:
> We have some older 3rd party packages that require Numeric (24.2), but like
> to also use newer
> 3rd party packages that require a recent numpy. Can Numeric and numpy
> co-exist in the same
> process? -- I'm mainly worried about clashes at the C API level.
nope
Hi,
We have some older 3rd party packages that require Numeric (24.2), but like to
also use newer
3rd party packages that require a recent numpy. Can Numeric and numpy co-exist
in the same
process? -- I'm mainly worried about clashes at the C API level.
Thanks!
Ralf
___
On Fri, Oct 3, 2008 at 10:59 AM, Gael Varoquaux <
[EMAIL PROTECTED]> wrote:
> I am doing a calculation where one call numpy.dot ends up taking 90% of
> the time (the array is huge: (61373, 500) ).
>
> Any chance I can make this faster? I would believe BLAS/ATLAS would be
> behind this, but from my
I am doing a calculation where one call numpy.dot ends up taking 90% of
the time (the array is huge: (61373, 500) ).
Any chance I can make this faster? I would believe BLAS/ATLAS would be
behind this, but from my quick analysis (ldd on numpy/core/multiarray.so)
it doesn't seem so. Have I done some
On Fri, Oct 3, 2008 at 11:21 AM, Michel Dupront
<[EMAIL PROTECTED]> wrote:
>
> I was using swig 1.3.24.
> I installed the last swig version 1.3.36 and now it is working fine !
> and it makes me very very happy !!!
>
SWIG often has that effect on people :)
--
Nathan Bell [EMAIL PROTECTED]
http://
Kelly Vincent wrote:
> I'm using Numpy to do some basic array manipulation, and I'm getting
> some unexpected behavior from shape. Specifically, I have some 3x3 and
> 2x2 matrices, and shape gives me (5, 3) and (3, 2) for their respective
> sizes. I was expecting (3, 3) and (2, 2), for number of ro
I'm using Numpy to do some basic array manipulation, and I'm getting some
unexpected behavior from shape. Specifically, I have some 3x3 and 2x2 matrices,
and shape gives me (5, 3) and (3, 2) for their respective sizes. I was
expecting (3, 3) and (2, 2), for number of rows, number of columns. I'
I was using swig 1.3.24.
I installed the last swig version 1.3.36 and now it is working fine !
and it makes me very very happy !!!
> From: [EMAIL PROTECTED]
> To: numpy-discussion@scipy.org
> Date: Fri, 3 Oct 2008 12:21:20 +0200
> Subject: [Numpy-discus
Roman Bertle wrote:
> Hello,
>
> I have found something I call a bug in the numpy choose() method and
> wanted to report it in trac.
>
Thanks for your report. I'm not sure why you are having trouble with
Trac, but I've created a ticket for this problem.
-Travis
__
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
On Fri, Oct 3, 2008 at 12:35 AM, Francesc Alted <[EMAIL PROTECTED]> wrote:
> It would be nice if you can update the PYPI package index too. Perhaps
> having a list of places on where to announce NumPy on every release
> would be handy.
Done. Thanks,
--
Jarrod Millman
Computational Infrastructu
Hello,
I have found something I call a bug in the numpy choose() method and
wanted to report it in trac.
http://scipy.org/BugReport states that "SciPy and NumPy Developer Pages
use the same login/password". However, I (username "smoerz") can log in
with my Scipy account at the Scipy Developer Page
Oh sorry I wrote my first email in french
Hello,
I just installed Numpy. I am interested in using Swig.
When I try to build the tests I get the following error message:
"""
swig -c++ -python Array.i
:9: Error: Macro '%typecheck' expects 1 argument
:36: Error: Macro '%typecheck' expects 1 argu
Bonjour,
Je viens d'installer Numpy. Je suis intéressé par l'utilisation de swig.
Lorsque je tente de construire les tests j'ai cette erreur:
"""
swig -c++ -python Array.i
:9: Error: Macro '%typecheck' expects 1 argument
:36: Error: Macro '%typecheck' expects 1 argument
:64: Error: Macro '%type
A Friday 03 October 2008, Jarrod Millman escrigué:
> On Thu, Oct 2, 2008 at 4:29 PM, Chris Barker <[EMAIL PROTECTED]>
wrote:
> > Robert Kern wrote:
> >> Superceded by the 1.2.0 release. See the thread "ANN: NumPy
> >> 1.2.0".
> >
> > I thought I'd seen that, but when I went to:
> >
> > http://www.
19 matches
Mail list logo
