I find that "numpy.max(0, 1e-6) == 0" is confusing, because it makes bugs
hard to spot. The doc says that the second argument to max is an optional
integer. My bad.
But could the function raise an error if it is passed an invalid 'axis'
argument? That would have helped.
James
--
http://www-etu
Hi,
I have installed numpy but the unit tests fail. When I ran them, I got
Traceback (most recent call last):
File "/home/jhtu/local/lib/python2.7/site-packages/numpy/testing/
decorators.py", line 215, in knownfailer
return f(*args, **kwargs)
File "/home/jhtu/local/lib/python2.7/site
The MKL configuration looks right, except that I had to use:
mkl_libs = mkl_intel_lp64, mkl_intel_thread, mkl_core, iomp5
During the build process, it should tell you what it is linking
aginast. Look at the compiler options passed to icc.
- Ilan
On Tue, Jan 18, 2011 at 2:31 PM, Jonathan Tu wro
Hi,
I realized that my cluster has MKL installed. I've been trying to
install against MKL, but am having trouble getting this to work.
After it finishes, I do
import numpy
numpy.show_config()
and nothing about the MKL libraries shows up. I have edited site.cfg
to read like this:
[mkl]
Hello Jonathan,
yes, numpy work fine under Python 2.7 now. I don't see why building
numpy against the system ATLAS should not work, as long as you
install the developer version with the header files, and make sure that
you edit the site.cfg file correct.
- Ilan
On Tue, Jan 18, 2011 at 10:39 AM,
On Tue, Jan 18, 2011 at 1:02 PM, Charles R Harris
wrote:
> I believe the problem has been been 64 bit fortran for ATLAS, the mingw
> version has/had problems. A plain build using the MS compilers works fine
> without ATLAS.
>
> Chuck
Do you think there would be interest/demand for official non-AT
Hi,
I need to reinstall numpy because the cluster I am using was recently
overhauled. I am wondering if numpy works with Python 2.7 now.
Also, I would like numpy to run as fast as possible. The last time I
did this, I was advised to install ATLAS by hand, as the one that
comes with RHEL i
On Tue, Jan 18, 2011 at 10:09 AM, Ralf Gommers
wrote:
>
>
> On Tue, Jan 18, 2011 at 2:27 AM, wrote:
>>
>> On Mon, Jan 17, 2011 at 12:18 PM, Bruce Southey
>> wrote:
>> >
>> > Scipy release notes usually state the supported numpy version eg from
>> > the current 0.8.0 release notes
>> > "This rele
On Tue, Jan 18, 2011 at 2:27 AM, wrote:
> On Mon, Jan 17, 2011 at 12:18 PM, Bruce Southey
> wrote:
> >
> > Scipy release notes usually state the supported numpy version eg from
> > the current 0.8.0 release notes
> > "This release requires Python 2.4 - 2.6 and NumPy 1.4.1 or greater."
> > Conseq
I believe the problem has been been 64 bit fortran for ATLAS, the mingw
version has/had problems. A plain build using the MS compilers works fine
without ATLAS.
Chuck
On Mon, Jan 17, 2011 at 7:05 AM, Peter <
numpy-discuss...@maubp.freeserve.co.uk> wrote:
> Hi all,
>
> Are there plans to provide
10 matches
Mail list logo
