Hello all,
> I'm not sure the licensing really makes it possible though. Numpy isn't
> exactly an application, but rather a development tool, so I'm not sure
> how Intel would feel about it being distributed. Also, it looks like
> they require each "developer" to have license, rather than only the
On Tue, 11 Dec 2007, Ryan Krauss wrote:
> I have a student trying to get started with such
> a machine. Numpy is causing Python to crash. What is the
> easiest solution?
Use 1.0.3.1
> Is it just Numpy or also Scipy?
It is also SciPy. Stuff that relies
only on NumPy wil work, plus anything
On Dec 11, 2007 6:45 PM, Ryan Krauss <[EMAIL PROTECTED]> wrote:
> Near as I can tell, this is still unresolved for people with non-sse2
> machines. Is that right?
Yup. Your more detailed testing seems to confirm the hunch I had at
the weekend workshop that SSE2 is the culprit. Thanks for the in
Near as I can tell, this is still unresolved for people with non-sse2
machines. Is that right?
I have a student trying to get started with such a machine. Numpy is
causing Python to crash. What is the easiest solution? Does he need
to build numpy from source on that machine (I actually still h
David Cournapeau wrote:
> On Dec 12, 2007 2:58 AM, Christopher Barker <[EMAIL PROTECTED]> wrote:
>> David Cournapeau wrote:
I think this idea is the way to go (maybe along with an ACML build, but my
limited testing seemed to indicate that MKL works on AMD CPUs).
>>> I am personally t
On Dec 12, 2007 3:04 AM, Christopher Barker <[EMAIL PROTECTED]> wrote:
> Fernando Perez wrote:
> > a simple, reasonable solution that is likely to work: ship TWO
> > binaries of Numpy/Scipy each time:
> >
> > 1. {numpy,scipy}-reference: built with the reference blas from netlib,
> > no atlas, perio
On Dec 12, 2007 2:58 AM, Christopher Barker <[EMAIL PROTECTED]> wrote:
> David Cournapeau wrote:
> >> I think this idea is the way to go (maybe along with an ACML build, but my
> >> limited testing seemed to indicate that MKL works on AMD CPUs).
> >>
> > I am personally totally against it. It is on
Hans Meine wrote:
> On Dienstag 11 Dezember 2007, Timothy Hochberg wrote:
>
>>> You mean one of the following?
>>> a.clip(min = 10, max = numpy.finfo(a.dtype).max)
>>> a.clip(min = 10, max = numpy.iinfo(a.dtype).max)
>>>
>> No. I mean:
>>
>> numpy.maximum(a, 10)
>>
>> To correspond to
On Dienstag 11 Dezember 2007, Timothy Hochberg wrote:
> > You mean one of the following?
> > a.clip(min = 10, max = numpy.finfo(a.dtype).max)
> > a.clip(min = 10, max = numpy.iinfo(a.dtype).max)
>
> No. I mean:
>
> numpy.maximum(a, 10)
>
> To correspond to the above example.
Great, thanks for
On Dec 11, 2007 11:04 AM, Christopher Barker <[EMAIL PROTECTED]> wrote:
> Fernando Perez wrote:
> > a simple, reasonable solution that is likely to work: ship TWO
> > binaries of Numpy/Scipy each time:
> >
> > 1. {numpy,scipy}-reference: built with the reference blas from netlib,
> > no atlas, peri
Fernando Perez wrote:
> a simple, reasonable solution that is likely to work: ship TWO
> binaries of Numpy/Scipy each time:
>
> 1. {numpy,scipy}-reference: built with the reference blas from netlib,
> no atlas, period.
>
> 2. {}-atlas: built with whatever the developers have at the time,
> which
David Cournapeau wrote:
>> I think this idea is the way to go (maybe along with an ACML build, but my
>> limited testing seemed to indicate that MKL works on AMD CPUs).
>>
> I am personally totally against it. It is one thing to support
> proprietary software, that's quite another to build our offi
At 02:32 AM 12/11/2007, you wrote:
>If so I'd be happy to contribute part of the purchase price,
>and I assume others would too.
>
>What's more, I *have* an old PIII at home.
The main company I consult for is set to buy the Intel compiler and
FFT lib for Windows, for the express purpose of compil
On Dec 11, 2007 2:32 AM, Hans Meine <[EMAIL PROTECTED]> wrote:
> Am Montag, 10. Dezember 2007 23:46:17 schrieb Timothy Hochberg:
> > > TypeError: function takes at least 2 arguments (1 given)
> > >
> > > (I could simulate that by passing max = maximum_value_of(a.dtype), if
> > > that existed, see
On Dec 11, 2007 8:47 PM, Albert Strasheim <[EMAIL PROTECTED]> wrote:
> Hello
>
> I think this idea is the way to go (maybe along with an ACML build, but my
> limited testing seemed to indicate that MKL works on AMD CPUs).
>
I am personally totally against it. It is one thing to support
proprietary
2007/12/11, Albert Strasheim <[EMAIL PROTECTED]>:
>
> Hello
>
> I think this idea is the way to go (maybe along with an ACML build, but my
> limited testing seemed to indicate that MKL works on AMD CPUs).
I'm trying to build numpy with ACML, but ACML misses the CBLAS interface and
thus the compil
Hello
I think this idea is the way to go (maybe along with an ACML build, but my
limited testing seemed to indicate that MKL works on AMD CPUs).
In fact, I apparently proposed it about a year ago:
https://svn.enthought.com/enthought/ticket/899
No takers so far...
Cheers,
Albert
P.S. NumPy o
On Dec 11, 2007 3:16 PM, Fernando Perez <[EMAIL PROTECTED]> wrote:
>
> On Dec 10, 2007 11:04 PM, David Cournapeau <[EMAIL PROTECTED]> wrote:
> > On Dec 11, 2007 12:46 PM, Andrew Straw <[EMAIL PROTECTED]> wrote:
> > > According to the QEMU website, QEMU does not (yet) emulate SSE on x86
> > > target
Am Montag, 10. Dezember 2007 17:23:07 schrieb Matthieu Brucher:
> I had the same problem sooner today, someone told me the answer : use
> numpy.info object ;)
I saw this shortly after posting (what a coincidence), and I planned to reply
to myself, but my mail did not make it to the list very quic
Am Montag, 10. Dezember 2007 23:46:17 schrieb Timothy Hochberg:
> > TypeError: function takes at least 2 arguments (1 given)
> >
> > (I could simulate that by passing max = maximum_value_of(a.dtype), if
> > that existed, see my other mail.)
>
> Why not just use minimum or maximum as needed instead
20 matches
Mail list logo
