Hi,
In the README.txt of the numpy installation it says that one could use a
site.cfg file to
specify non-standard locations of ATLAS en LAPACK libraries, but it doesn't
explain how.
I have a directory software/atlas3.6.0/lib/Linux_PPROSSE2/ which contains
libcombinedlapack.a libatlas.a
Bill Baxter wrote:
> If you do this:
> >>> numpy.linalg.eig(numpy.random.rand(3,3))
>
> You'll (almost always) get a wrong answer back from numpy. Something
> like:
>
> (array([ 1.72167898, -0.07251007, -0.07251007]),
> array([[ 0.47908847, 0.72095163, 0.72095163],
>[ 0.56659142, -0.46
Thanks for the info Nils. Sounds like it was fixed post-1.0b1. Good news.And Trac seems to be letting me in again. Not sure what was wrong there.--bbOn 8/18/06,
Nils Wagner <[EMAIL PROTECTED]> wrote:
Bill Baxter wrote:> If you do this:> >>> numpy.linalg.eig(numpy.random.rand(3,3))>> You'll (al
On Fri, Aug 18, 2006 at 01:54:44PM +0900, David Cournapeau wrote:
> import numpy as N
> from ctypes import cdll, POINTER, c_int, c_uint
>
> _hello = cdll.LoadLibrary('libhello.so')
>
> _hello.sum.restype= c_int
> _hello.sum.artype = [POINTER(c_int), c_uint]
>
> def sum(data):
> retur
Hello all
>
> I decided to upgrade to 1.0b2 just to see what I get and now I get 7kB of
> "possibly lost" memory, coming from PyObject_Malloc (in
> /usr/lib/libpython2.4.so.1.0). This is a constant 7kB, however, and it
> isn't getting any larger if I increase the loop iterations. Looks good
> the
Hello all
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:numpy-
> [EMAIL PROTECTED] On Behalf Of David Cournapeau
> Sent: 18 August 2006 06:55
> To: Discussion of Numerical Python
> Subject: [Numpy-discussion] ctypes: how does load_library work ?
>
>
> That works OK, but to avoid
Stefan van der Walt wrote:
> On Fri, Aug 18, 2006 at 01:54:44PM +0900, David Cournapeau wrote:
>
>> import numpy as N
>> from ctypes import cdll, POINTER, c_int, c_uint
>>
>> _hello = cdll.LoadLibrary('libhello.so')
>>
>> _hello.sum.restype= c_int
>> _hello.sum.artype = [POINTER(c_int),
Hi,
I'm starting to (slowly) replace numarray by NumPy at the core of PyTables,
specially at those places where the speed of NumPy is *much* better, that is,
in the creation of arrays (there are places in PyTables where this is
critical, most specially in indexation) and in copying arrays. In b
Albert Strasheim wrote:
> Hello all
>
>
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:numpy-
>> [EMAIL PROTECTED] On Behalf Of David Cournapeau
>> Sent: 18 August 2006 06:55
>> To: Discussion of Numerical Python
>> Subject: [Numpy-discussion] ctypes: how does load_library work
Hi there,
in numpy-1.0b2 the logic in setup.py is slightly off. The attached patch
fixes the issue.
Greetings,
Norbert
PS: I would have preferred to submit this patch via the sourceforge
bug-tracker, but that seems rather confusing: there are tabs "Numarray
Patches" and "Numarray Bugs" but no "N
A Divendres 18 Agost 2006 15:36, Norbert Nemec va escriure:
> PS: I would have preferred to submit this patch via the sourceforge
> bug-tracker, but that seems rather confusing: there are tabs "Numarray
> Patches" and "Numarray Bugs" but no "NumPy bugs" and the tab "Patches"
> seems to be used for
Can you provide some details about your approach to migrating to
NumPy? Are you following some documentation on migration or do you
have your own plan of attack?
Chris
On Aug 18, 2006, at 6:59 AM, Francesc Altet wrote:
> Hi,
>
> I'm starting to (slowly) replace numarray by NumPy at the
Hi Norbert
On Fri, Aug 18, 2006 at 03:36:47PM +0200, Norbert Nemec wrote:
> in numpy-1.0b2 the logic in setup.py is slightly off. The attached patch
> fixes the issue.
Please file a ticket so that we don't lose track of this.
Stéfan
--
A Divendres 18 Agost 2006 16:44, Chris Kees va escriure:
> Can you provide some details about your approach to migrating to
> NumPy? Are you following some documentation on migration or do you
> have your own plan of attack?
Well, to say the truth none of both ;-). The truth is that I was tr
Hi,
It is so common to have problems with erecxxtion, Try VIrAGRA and forget about it http://www.vabaominheran.com which in turn . . .
Charges up your batteries. We know a thing or two as well, Hingst,
greeter of strangers to Paradise, and we are not your usual goaty
Christopher Hanley wrote:
> What happened to numpy.bool8? I realize that bool_ is just as good. I
> was just wondering what motivated the change?
>
>
I think it was accidental... The numpy scalar tp_names were recently
changed to be more consistent with Python and the bool8 construct
proba
Chris Kees wrote:
> Hi,
>
> I just ran convertcode.py on my code (from the latest svn source
> of numpy) and it looks like it just changed the import statements to
>
> import numpy.oldnumeric as Numeric
>
> So it doesn't look like it's really helping me move over to the
> new usage.
David Grant wrote:
> I'm contemplating upgrading to 1.0b2. The main reason is that I am
> experiencing a major memory leak and before I report a bug I think the
> developers would appeciate if I was using the most recent version. Am
> I correct in that the only major change that might actually b
Hi,
array dtype descriptors have an attribute itemsize that gives the total
number of bytes required for an item of that dtype.
Scalar types, like numy.int32, also have that attribute,
but it returns "something else" - don't know what:
>>> a.dtype.itemsize
4
>>> a.dtype.name
'float32'
>>> N.int
Norbert Nemec wrote:
> Hi there,
>
> in numpy-1.0b2 the logic in setup.py is slightly off. The attached patch
> fixes the issue.
>
> Greetings,
> Norbert
>
> PS: I would have preferred to submit this patch via the sourceforge
> bug-tracker, but that seems rather confusing: there are tabs "Numarray
Sebastian Haase wrote:
> Hi,
> array dtype descriptors have an attribute itemsize that gives the total
> number of bytes required for an item of that dtype.
>
> Scalar types, like numy.int32, also have that attribute,
> but it returns "something else" - don't know what:
>
>
> Furthermore ther
I realize it was just released, but is there going to be a windows release
for 1.02b?
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make y
On Friday 18 August 2006 11:38, Travis Oliphant wrote:
> Sebastian Haase wrote:
> > Hi,
> > array dtype descriptors have an attribute itemsize that gives the total
> > number of bytes required for an item of that dtype.
> >
> > Scalar types, like numy.int32, also have that attribute,
> > but it r
Hi Travis,The description of what these codes do is in the latest version of the
second chapter of my book (which is part of the preview chapters thatare available on the web).Speaking of which, is it possible for us early buyers to get updated copies?Chuck
---
[EMAIL PROTECTED] wrote:
> I realize it was just released, but is there going to be a windows release
> for 1.02b?
>
>
There will be either be one of 1.0b3 or one of 1.0b2 released for
windows by Monday.
-Travis
-
Using
On 8/18/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
> David Grant wrote:
> > I'm contemplating upgrading to 1.0b2. The main reason is that I am
> > experiencing a major memory leak and before I report a bug I think the
> > developers would appeciate if I was using the most recent version. Am
> >
Hi all,
here is the SAGE signal handling code, graciously donated by William Stein.
I'd suggest putting (with any modifications to adapt it to numpy conventions)
this into the actual numpy headers, so that not only all of our
auto-generation tools (f2py, weave) can use it, but so that it also
On 8/18/06, Fernando Perez <[EMAIL PROTECTED]> wrote:
> here is the SAGE signal handling code, graciously donated by William Stein.
Hit send too soon... I forgot to thank William for this code :)
hopefully one of many things we'll be sharing between numpy/scipy and
SAGE.
Cheers,
f
-
Sebastian Haase wrote:
> On Friday 18 August 2006 11:38, Travis Oliphant wrote:
>
>> Sebastian Haase wrote:
>>
>>> Hi,
>>> array dtype descriptors have an attribute itemsize that gives the total
>>> number of bytes required for an item of that dtype.
>>>
>>> Scalar types, like numy.int32,
On Friday 18 August 2006 15:25, Travis Oliphant wrote:
> Sebastian Haase wrote:
> > On Friday 18 August 2006 11:38, Travis Oliphant wrote:
> >> Sebastian Haase wrote:
> >>> Hi,
> >>> array dtype descriptors have an attribute itemsize that gives the
> >>> total number of bytes required for an item
Hi,
I am correctly assuming that numpy needs the full lapack distribution,
and not just the few lapack routines given by atlas? After installing
numpy I still get the warning
ImportError:
/software/python-2.4.1/lib/python2.4/site-packages/numpy/linalg/lapack_lite.so:
undefined symbol: s_wsfe
w
s_wsfe is not LAPACK's routine it's a routine from the g2c library.
You have to link it in in addition to lapack_lite.
Piotr
On Friday 18 August 2006 18:07, [EMAIL PROTECTED] wrote:
> Hi,
>
> I am correctly assuming that numpy needs the full lapack
> distribution, and not just the few lapack rout
Sebastian Haase wrote:
> On Friday 18 August 2006 15:25, Travis Oliphant wrote:
>
>> Sebastian Haase wrote:
>>
>>> On Friday 18 August 2006 11:38, Travis Oliphant wrote:
>>>
Sebastian Haase wrote:
> Hi,
> array dtype descriptors have an attribute itemsize
> This leak is caused by add_docstring, but it's supposed to leak. I wonder if
> there's a way to register some kind of on-exit handler in Python so that
> this can also be cleaned up?
import atexit
atexit.register(your_cleanup_function)
whose api is no args on input:
def your_cleanup_function()
On Fri, Aug 18, 2006 at 04:45:03PM +0200, Stefan van der Walt wrote:
> Hi Norbert
>
> On Fri, Aug 18, 2006 at 03:36:47PM +0200, Norbert Nemec wrote:
> > in numpy-1.0b2 the logic in setup.py is slightly off. The attached patch
> > fixes the issue.
>
> Please file a ticket so that we don't lose tra
On Friday 18 August 2006 16:51, Travis Oliphant wrote:
> Sebastian Haase wrote:
> > On Friday 18 August 2006 15:25, Travis Oliphant wrote:
> >> Sebastian Haase wrote:
> >>> On Friday 18 August 2006 11:38, Travis Oliphant wrote:
> Sebastian Haase wrote:
> > Hi,
> > array dtype descripto
Hi,
[PL]: s_wsfe is not LAPACK's routine it's a routine from the g2c library.
[PL]: You have to link it in in addition to lapack_lite.
Thanks for the pointer.
Sorry about my ignorance about these things. But is lapack_lite linked
to numpy even if you specify the full lapack library?
Afte
Hi All,
I've noticed a lot of trailing whitespace while browsing through the
numpy subversion repository. So here is a perl script I pinched from
the linux-kernel mailing list that does a good job of removing it.
Chuck
cleanfile
Description: Binary data
38 matches
Mail list logo
