From: Anne Archibald
On 6 April 2010 15:42, Ken Basye wrote:
> Folks,
> I hope this is a simple question. When I created a ufunc with
> np.frompyfunc(), I got an error when I called the result with an 'out'
> argument:
In fact, ordinary ufuncs do not accept names for their arguments. T
Briefly, I'm encountering difficulties getting things working in numpy
distutils for fwrap's build system.
Here are the steps I want the build system to accomplish:
1) Compile a directory of Fortran 90 source code -- this works.
- The .mod files generated by this compilation step are put in t
On 6 April 2010 15:42, Ken Basye wrote:
> Folks,
> I hope this is a simple question. When I created a ufunc with
> np.frompyfunc(), I got an error when I called the result with an 'out'
> argument:
In fact, ordinary ufuncs do not accept names for their arguments. This
is annoying, but fixing it
On 04/06/2010 04:07 PM, Michael Gilbert wrote:
> Hi,
>
> I am applying Monte Carlo for a problem involving mixed deterministic
> and random values. In order to avoid a lot of special handling and
> corner cases, I am using using numpy arrays full of a single value to
> represent the deterministic
Hi,
I am applying Monte Carlo for a problem involving mixed deterministic
and random values. In order to avoid a lot of special handling and
corner cases, I am using using numpy arrays full of a single value to
represent the deterministic quantities.
Anyway, I found that the standard deviation t
On Sat, Apr 3, 2010 at 2:28 PM, Philip Sterne wrote:
> I hope this is the correct place to post my question. I'd like python to
> interface with c++ code that makes heavy use of Blitz++ arrays. After a
> day's hacking I appear to have a simple working solution which I am
> attaching. (It uses Bo
Folks,
I hope this is a simple question. When I created a ufunc with
np.frompyfunc(), I got an error when I called the result with an 'out'
argument:
>>> def foo(x): return x * x + 1
>>> ufoo = np.frompyfunc(foo, 1, 1)
>>> arr = np.arange(9).reshape(3,3)
>>> ufoo(arr, out=arr)
Traceback (
On Apr 6, 2010, at 9:08 AM, David Cournapeau wrote:
Hi Travis,
On Tue, Apr 6, 2010 at 7:43 AM, Travis Oliphant > wrote:
I should have some time over the next couple of weeks, and I am very
interested in refactoring the NumPy code to separate out the Python
interface layer from the "library"
Hi Travis,
On Tue, Apr 6, 2010 at 7:43 AM, Travis Oliphant wrote:
>
>
> I should have some time over the next couple of weeks, and I am very
> interested in refactoring the NumPy code to separate out the Python
> interface layer from the "library" layer as much as possible. I had
> some discuss
On Tue, Apr 6, 2010 at 9:22 AM, Ken Basye wrote:
> From: Vincent Schut
>
> On 04/05/2010 06:06 PM, Keith Goodman wrote:
>
>
> On Mon, Apr 5, 2010 at 8:44 AM, Ken Basye wrote:
>
>
> Hi Folks,
> I have two arrays, A and B, with the same shape. I want to find the
> highest values in A along some
From: Vincent Schut
On 04/05/2010 06:06 PM, Keith Goodman wrote:
On Mon, Apr 5, 2010 at 8:44 AM, Ken Basye wrote:
Hi Folks,
I have two arrays, A and B, with the same shape. I want to find the
highest values in A along some axis, then extract the corresponding
values from B. I can
On 4/6/2010 6:46 AM, Yogesh Tomar wrote:
> import numpy
> import numpy.linalg
> x=numpy.eye(1000)
> for i in range(10):
> eigenvalues,eigenvectors=numpy.linalg.eig(x)
> eigenvalues,eigenvectors=numpy.linalg.eig(x)
> print str(i),'---'*
I'm not seeing any
I also think the same. There is some problem with my python installation.
Because a similar installation python-2.6.4 and numpy-1.3.0 which I did
elsewhere does not seg fault for the same code.
But I need your help to figure it out.
Can you please elaborate on ref count bug? that might help.
Rega
On Tue, Apr 6, 2010 at 8:28 PM, Yogesh Tomar wrote:
> numpy 1.3.0 also segfaults the same way.
I mean building numpy 1.3.0 against python 2.6.1 instead of 2.6.4 -
since the crash happen on a python you built by yourself, that's the
first thing I would look into before looking into numpy or python
numpy 1.3.0 also segfaults the same way.
Is it the problem with libc library?
Gdb stacktrace.
gdb) run /home/eqan/64bit/current/segf.py
Starting program: /home/eqan/tapas/64bit/Python/2.6.4_x641/bin/python
/home/eqan/64bit/current/segf.py
[Thread debugging using libthread_db enabled]
[New Threa
On Tue, Apr 6, 2010 at 7:46 PM, Yogesh Tomar wrote:
>
> Hi all,
>
> I am getting numpy segmentation fault on a custom install of python to a
> prefix.
What happens if you build numpy 1.3.0 against python 2.6.1 (instead of
your own 2.6.4) ? For numpy, a strace is not really useful (a
backtrace fro
On 04/05/2010 06:06 PM, Keith Goodman wrote:
> On Mon, Apr 5, 2010 at 8:44 AM, Ken Basye wrote:
>> Hi Folks,
>> I have two arrays, A and B, with the same shape. I want to find the
>> highest values in A along some axis, then extract the corresponding
>> values from B. I can get the highest val
Hi all,
I am getting numpy segmentation fault on a custom install of python to a
prefix.
I am running this example code.
*import numpy
import numpy.linalg
x=numpy.eye(1000)
for i in range(10):
eigenvalues,eigenvectors=numpy.linalg.eig(x)
eigenvalues,eigenvectors=numpy.linalg.eig(x)
p
Hi all,
I am getting numpy segmentation fault on a custom install of python to a
prefix.
I am running this example code.
*import numpy
import numpy.linalg
x=numpy.eye(1000)
for i in range(10):
eigenvalues,eigenvectors=numpy.linalg.eig(x)
eigenvalues,eigenvectors=numpy.linalg.eig(x)
p
If anyone was interested I found that the easiest solution involved
patching up the strides after calling PyArray_SimpleNewFromData(). I
still haven't gotten any sort of memory interaction so any objects
created by Blitz are deleted by Blitz, while Python objects are deleted
by Python. (Irres
20 matches
Mail list logo
