On Sat, Aug 1, 2009 at 1:14 PM, David Cournapeau wrote:
> On Fri, Jul 31, 2009 at 8:20 PM, David
> Cournapeau wrote:
>> Steven Coutts wrote:
>>> David Cournapeau ar.media.kyoto-u.ac.jp> writes:
>>>
>>> If you are willing to do
>>>
it, I would also be interested whether numpy works ok if lin
On Fri, Jul 31, 2009 at 8:20 PM, David
Cournapeau wrote:
> Steven Coutts wrote:
>> David Cournapeau ar.media.kyoto-u.ac.jp> writes:
>>
>> If you are willing to do
>>
>>> it, I would also be interested whether numpy works ok if linked against
>>> BLAS/LAPACK instead of atlas (i.e. build numpy, ag
Awww, it's fun to be foolish on Fridays!
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Fri, Jul 31, 2009 at 4:30 PM, Chris Colbert wrote:
> ahh, yeah I see now. Thanks!
>
> nothing like making myself look the fool on a friday!
>
If you have to choose a day, Friday is the day of choice. Or a least it
supposedly works that way for bad news and politics.
Chuck
___
ahh, yeah I see now. Thanks!
nothing like making myself look the fool on a friday!
Cheers!
On Fri, Jul 31, 2009 at 6:20 PM, Robert Kern wrote:
> On Fri, Jul 31, 2009 at 17:15, Chris Colbert wrote:
>> Numpy 1.3
>>
>> In [1]: import numpy as np
>>
>> In [2]: a = np.zeros(5).fill(5)
>>
>> In [3]: a
On Fri, Jul 31, 2009 at 17:15, Chris Colbert wrote:
> Numpy 1.3
>
> In [1]: import numpy as np
>
> In [2]: a = np.zeros(5).fill(5)
>
> In [3]: a
>
> In [4]: type(a)
> Out[4]:
>
> In [5]: a = np.zeros(5)
>
> In [6]: a.fill(5)
>
> In [7]: a
> Out[7]: array([ 5., 5., 5., 5., 5.])
>
>
> What i'm t
Numpy 1.3
In [1]: import numpy as np
In [2]: a = np.zeros(5).fill(5)
In [3]: a
In [4]: type(a)
Out[4]:
In [5]: a = np.zeros(5)
In [6]: a.fill(5)
In [7]: a
Out[7]: array([ 5., 5., 5., 5., 5.])
What i'm trying to do may not be the best way, but I think it should
still have worked.
Thou
Travis Oliphant wrote:
> Doesn't .view work for that?
>
> Travis
>
>
> Sent from my iPhone
>
> On Jul 29, 2009, at 6:57 AM, Neal Becker wrote:
>
>> Neal Becker wrote:
>>
>>> Does numpy have functions to convert between e.g. an array of
>>> uint32 and
>>> uint8, where the uint32 array is a pa
About sixteen months ago, I launched the SciPy Documentation Project
and its Marathon. Dozens pitched in and now numpy docs are rapidly
approaching a professional level. The "pink wave" ("Needs Review"
status) is at 56% today! There is consensus among doc writers that
much of the rest can be lab
A short field report. Python 2.6.2 installed and working with the
latest versions of:
numpy
scipy
MySQLdb
gnuplot.py and gnuplot
rpy and R 2.9.1
PyScripter
PyWin32
Rpyc 2.6
The little bit of 3.n syntax I have tried works.
So far, this seems like a stable and trouble-free stack.
Thanks for the f
Charles R Harris wrote:
>
> Sounds like this problem might depend on the specific combination of
> compiler, hardware, and Atlas. Could you tell us which amd chip and
> compiler versions you are using?
>
> Chuck
processor : 0
vendor_id : AuthenticAMD
cpu family
On Fri, Jul 31, 2009 at 5:48 AM, Steven Coutts wrote:
> David Cournapeau ar.media.kyoto-u.ac.jp> writes:
> >
> > So that's a problem with ATLAS. Maybe a gcc bug ? Another user contacted
> > me privately for my rpm repository, and got exactly the same problem
> > with the rpms, on CENTOS 5.3 as w
I've cooked a very rudimentary implementation of what I would like to
have, however I've got a small problem concerning array shape. The idea
is to have a parent array (a group) that can be instantiated like a
regular array and that build internally all the relevant contiguous
child arrays. I wou
Hi Matthieu,
Thanks for the explanation. After having looked at the documentation, I
decided to do my own plain Python c-api implementation.
Thanks for your time
Raymond
Matthieu Brucher wrote:
> 2009/7/30 Raymond de Vries :
>
>> Hi
>>
>>
>>> Indeed, the solution is as simple as this ;
David Cournapeau ar.media.kyoto-u.ac.jp> writes:
>
> So that's a problem with ATLAS. Maybe a gcc bug ? Another user contacted
> me privately for my rpm repository, and got exactly the same problem
> with the rpms, on CENTOS 5.3 as well. I will try to look at it on a
> centos VM if I have time thi
Steven Coutts wrote:
> David Cournapeau ar.media.kyoto-u.ac.jp> writes:
>
> If you are willing to do
>
>> it, I would also be interested whether numpy works ok if linked against
>> BLAS/LAPACK instead of atlas (i.e. build numpy, again from scratch, with
>> ATLAS=None python setup.py build, an
David Cournapeau ar.media.kyoto-u.ac.jp> writes:
If you are willing to do
> it, I would also be interested whether numpy works ok if linked against
> BLAS/LAPACK instead of atlas (i.e. build numpy, again from scratch, with
> ATLAS=None python setup.py build, and then run the test suite).
>
Ye
Dinesh B Vadhia wrote:
> A suggestion:
>
> How about releasing Numpy for the AMD64 version first (without Scipy)
> and then follow up with a later release with Scipy support? This
> would satisfy Numpy-only users which can't be a bad thing rather than
> having a version that is not usable (I be
David Cournapeau ar.media.kyoto-u.ac.jp> writes:
>
> That's really strange - Linux is the most tested configuration, numpy
> 1.3.0 should run without problems. There is something unusual with your
> configuration that I am missing.
>
> Could you build numpy 1.3.0 from scratch and paste the out
A suggestion:
How about releasing Numpy for the AMD64 version first (without Scipy) and then
follow up with a later release with Scipy support? This would satisfy
Numpy-only users which can't be a bad thing rather than having a version that
is not usable (I believe) by either Numpy or Scipy
David Cournapeau ar.media.kyoto-u.ac.jp> writes:
>
> Make sure your scipy is built against numpy 1.2.1. You cannot build
> scipy against numpy 1.3.0, and then use scipy with numpy 1.2.1 (but you
> can build against numpy 1.2.1 and use scipy with numpy 1.3.0).
>
> cheers,
>
> David
Yes it was
Steven Coutts wrote:
> Steven Coutts couttsnet.com> writes:
>
>
>> Ok, downgraded numpy to 1.2.1 and all the tests pass now!
>>
>> Regards
>>
>>
>
> But now scipy seg faults straight away
>
> http://pastebin.com/de13dd62
>
> Downgraded scipy to 0.7.0 and still the same seg fault :(
>
M
Steven Coutts wrote:
>
> Ok, downgraded numpy to 1.2.1 and all the tests pass now!
>
That's really strange - Linux is the most tested configuration, numpy
1.3.0 should run without problems. There is something unusual with your
configuration that I am missing.
Could you build numpy 1.3.0 from
Steven Coutts couttsnet.com> writes:
>
> But now scipy seg faults straight away
>
> http://pastebin.com/de13dd62
>
> Downgraded scipy to 0.7.0 and still the same seg fault :(
>
Downgrading all the way back to scipy-0.6.0 makes scipy work.
Any ideas why no newer version work?
Regards
Steven Coutts couttsnet.com> writes:
>
> Ok, downgraded numpy to 1.2.1 and all the tests pass now!
>
> Regards
>
But now scipy seg faults straight away
http://pastebin.com/de13dd62
Downgraded scipy to 0.7.0 and still the same seg fault :(
___
N
Steven Coutts wrote:
>
> Ok, http://pastebin.com/ddaae526
>
> Seg faults here -:
>
> test_cdouble (test_linalg.TestEigh)
>
> I am using gfortran.
>
> Regards
Ok, downgraded numpy to 1.2.1 and all the tests pass now!
Regards
___
NumPy-Discussion
David Cournapeau wrote:
>
> Not sure it can be considered as progress :) Could you run the test
> suite with verbosity set to ten (numpy.test(verbose=10)) ?
>
> Also, which fortran compiler are you using ? g77 or gfortran ?
>
> cheers,
>
> David
Ok, http://pastebin.com/ddaae526
Seg faults h
Steven Coutts wrote:
> David Cournapeau wrote:
>
>> Lapack 3.2 is problematic, so I would try to downgrade to 3.1.1 first.
>> Which OS are you on ? The exact core you are running, as well as the
>> output of the test suite (numpy.test()) would be helpful,
>>
>> cheers,
>>
>> David
>>
>
>
David Cournapeau wrote:
>
> Lapack 3.2 is problematic, so I would try to downgrade to 3.1.1 first.
> Which OS are you on ? The exact core you are running, as well as the
> output of the test suite (numpy.test()) would be helpful,
>
> cheers,
>
> David
Ok, I have downgraded to lapack 3.1.1 an
Steven Coutts wrote:
> Steven Coutts couttsnet.com> writes:
>
>
>> I am getting this error when trying to run a script using scipy.
>>
>> Python 2.5
>>
>> atlas-3.9.0
>> lapack-3.2
>> numpy-1.3.0
>> scipy-0.7.1
>>
>> Anyone any ideas how I can fix this?
>>
Lapack 3.2 is problematic, so I
Steven Coutts couttsnet.com> writes:
>
> I am getting this error when trying to run a script using scipy.
>
> Python 2.5
>
> atlas-3.9.0
> lapack-3.2
> numpy-1.3.0
> scipy-0.7.1
>
> Anyone any ideas how I can fix this?
>
> Regards
>
Also tried Atlas 3.9.11 and 3.8.3 with no luck.
Anyone g
31 matches
Mail list logo
