2010/8/4 Søren Gammelmark :
>
>>
>> I wouldn't know for sure, but could this be related to changes to the
>> gcc compiler in Fedora 13 (with respect to implicit DSO linking) or
>> would that only be an issue at build-time?
>>
>> http://fedoraproject.org/w/index.php?title=UnderstandingDSOLinkChange
>
> I wouldn't know for sure, but could this be related to changes to the
> gcc compiler in Fedora 13 (with respect to implicit DSO linking) or
> would that only be an issue at build-time?
>
> http://fedoraproject.org/w/index.php?title=UnderstandingDSOLinkChange
I'm not entirely sure I understa
On Tue, Aug 3, 2010 at 3:31 PM, Søren Gammelmark wrote:
> I feel a bit silly :-)
> The compile now appear to work. Sort of. I discovered I had sneaken in a
> "pthreads" in the mkl_libs line, which is obviously not in the
> mkl-directory (I had stolen this line from a stand-alone program I wrote
>
On 01/08/10 17:38, Ralf Gommers wrote:
> I am pleased to announce the availability of the first beta of NumPy
> 1.5.0. This will be the first NumPy release to include support for
> Python 3, as well as for Python 2.7. Please try this beta and report any
> problems on the NumPy mailing list.
the de
Mon, 02 Aug 2010 23:48:52 +0800, Ralf Gommers wrote:
> I'm trying to get building to work with Python 3.1 under Wine on OS X.
> The first thing you run into is a python distutils problem, which is
> fixed by replacing line 379 of cygwinccompiler.py with
> result = RE_VERSION.search(str(out_str
On 8/3/2010 5:40 PM, Robert Faryabi wrote:
> I'm using Tabular Package for manipulating tab-delimited data.
> There is a small problem that I cannot get my head around it.
>
> When I construct my tabarray from file, the blank fields are replaced by
> "nan".
> Does any one knows how to just keep th
Hi Till,
2010/8/3, Till Stensitzki :
> Hello,
> I am sorry for contacting you directly, i tried but i didn't found
> something like a numexpr mailinglist.
> Fist of all, thanks for this modul, it really helps to speed up some of
> my fitting rounties!
> Now for my qustion: Is there any way to add
Hi there;
I'm using Tabular Package for manipulating tab-delimited data.
There is a small problem that I cannot get my head around it.
When I construct my tabarray from file, the blank fields are replaced by
"nan".
Does any one knows how to just keep them as empty string (ie. ' ')?
Thanks,
_
Hi,
Since I was testing the 1.5 beta, I also tested the alpha release of
Python 3.2 on Linux 64-bit (gcc version 4.4.4 20100630 (Red Hat
4.4.4-10) (GCC)). While my other Python versions passed the tests (once
I copied the necessary tools directory for Python3.1), Python3.2 has
problems so I c
2010/8/3 matt_in_nyc :
> X is an m by n matrix, and I want to store outer products of the form Y[i] =
> numpy.outer(X[i,:], X[i,:]), leading to the relation Y[i,j,k] =
> X[i,j]*X[i,k] for i = 0,...,m-1; j,k = 0,...,n-1. I am trying to think of
> how to do this using tensordot, but so far I am find
I feel a bit silly :-)
The compile now appear to work. Sort of. I discovered I had sneaken in a
"pthreads" in the mkl_libs line, which is obviously not in the
mkl-directory (I had stolen this line from a stand-alone program I wrote
at some point). The error message is a bit confusing though - th
I am trying to perform the following operation:
X is an m by n matrix, and I want to store outer products of the form Y[i] =
numpy.outer(X[i,:], X[i,:]), leading to the relation Y[i,j,k] =
X[i,j]*X[i,k] for i = 0,...,m-1; j,k = 0,...,n-1. I am trying to think of
how to do this using tensordot, b
Tue, 03 Aug 2010 15:52:55 -0400, David Warde-Farley wrote:
[clip]
> in PyErr_WarnEx (category=0x11eb6c54,
> text=0x5f90c0 "PyOS_ascii_strtod and PyOS_ascii_atof are deprecated.
> Use PyOS_string_to_double instead.", stack_level=0) at
> Python/_warnings.c:719
> 719 res = do_warn(m
This was using the Intel MKL/icc to compile NumPy and also icc to compile
Python on a shared cluster, but I don't think that's relevant given where the
segmentation fault occurs...
gpc-f104n084-$ gdb python
GNU gdb Fedora (6.8-27.el5)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPL
Joshua Holbrook wrote:
> I don't think I've ever actually seen someone use the matrix datatype
> instead of the array datatype.
>
> Hopefully nobody minds me asking the noob question: What's the
> advantage of the matrix datatype?
The advantage of the matrix datatype is that it is a matrix in the
On Tue, Aug 3, 2010 at 10:44 AM, Alan G Isaac wrote:
> On 8/3/2010 1:29 PM, Joshua Holbrook wrote:
>> What's the
>> advantage of the matrix datatype?
>
>
> As it turns out, that's a controversial question. ;-)
>
> One answer: pedagogy (for those used to matrices).
>
> A related answer: succinctne
On 8/3/2010 1:29 PM, Joshua Holbrook wrote:
> What's the
> advantage of the matrix datatype?
As it turns out, that's a controversial question. ;-)
One answer: pedagogy (for those used to matrices).
A related answer: succinctness and readability of *some* code.
>>> a,b,c = np.array([[
I don't think I've ever actually seen someone use the matrix datatype
instead of the array datatype.
Hopefully nobody minds me asking the noob question: What's the
advantage of the matrix datatype?
--Josh
On Tue, Aug 3, 2010 at 8:59 AM, Wayne Watson
wrote:
> Thank you. That's almost amusing. T
Thank you. That's almost amusing. Too logical for Python. I fully
expected something like m{0}[0](0)[0:0]. :-)
I don't think the tentative Numpy tutorial mentions it.
On 8/3/2010 9:28 AM, phob...@geosyntec.com wrote:
> Wayne,
>
> Matrices are two dimensional arrays so you need two indices to ac
On 8/3/2010 12:23 PM, Wayne Watson wrote:
> How do I access 1.2 in such a way as to end up with a float? I keep
> getting a matrix.
> from numpy import matrix
> m = matrix([[1.2],[2.3]])
Matrices have the odd (and imo undesirable) property that
m[0,0] != m[0][0]
You want the former.
For a
Søren Gammelmark wrote:
> Hi everyone
>
> I realize that this e-mail has been written a lot of times before. I
> have, however, not been able to make it work even though I have looked
> through a lot of e-mails on the mailinglist. I apologize if the
> solution is written neatly somewhere.
In my
Wayne,
Matrices are two dimensional arrays so you need two indices to access an
individual element:
In [1]: from numpy import matrix
In [2]: m = matrix([[1.2],[2.3]])
In [3]: m[0,0]
Out[3]: 1.2
-paul
-Original Message-
From: numpy-discussion-boun...@scipy.org
[mailto:numpy-discussio
On Tue, Aug 3, 2010 at 12:23 PM, Wayne Watson
wrote:
> How do I access 1.2 in such a way as to end up with a float? I keep
> getting a matrix.
> from numpy import matrix
> m = matrix([[1.2],[2.3]])
m[0].item() ?
Skipper
___
NumPy-Discussion mailing lis
How do I access 1.2 in such a way as to end up with a float? I keep
getting a matrix.
from numpy import matrix
m = matrix([[1.2],[2.3]])
--
Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz S
Hi everyone
I realize that this e-mail has been written a lot of times before. I
have, however, not been able to make it work even though I have looked
through a lot of e-mails on the mailinglist. I apologize if the solution
is written neatly somewhere.
As many others I would like to install
Hi Pauli,
> If your circles are quite small, you probably want to clip the "painting"
> to a box not much larger than a single circle:
>
> # untested, something like below
> def point_to_index(x, y, pad=0):
> return np.clip(200 * rr / (xmax - xmin) + pad, 0, 200), \
> np.clip(200 * rr
26 matches
Mail list logo
