David Cournapeau wrote:
> I don't think it is wise to advocate the use of develop for python
> newcomers.
Fair enough.
What I know is that every scheme I've come up with for working with my
own under-development packages has been a pain in the #$@, and -develop
has worked well for me.
> The ea
Adrien Guillon wrote:
> I use single-precision floating point operations.
>
> My understanding, however, is that Intel processors may use extended
> precision for some operations anyways unless this is explicitly
> disabled, which is done with gcc via the -ffloat-store operation.
IIUC, that forc
Folks,
Apologies for asking here, but I ran across this problem yesterday
and probably need to file a bug. The problem is I don't know if this is
a Numpy bug, a Python bug, or both. Here's an illustration, platform
information follows.
TIA,
Ken
##
On 04/21/2010 08:36 AM, Robert Kern wrote:
> On Tue, Apr 20, 2010 at 18:45, Charles R Harris
> wrote:
>
>> On Tue, Apr 20, 2010 at 7:03 AM, Andreas Hilboll wrote:
>>
>>> Hi there,
>>>
>>> is there an easy way to do something like trim_zeros() does, but for a
>>> n-dimensional array? I
On 21 April 2010 11:03, Pauli Virtanen wrote:
> ke, 2010-04-21 kello 10:47 -0400, Adrien Guillon kirjoitti:
> [clip]
>> My understanding, however, is that Intel processors may use extended
>> precision for some operations anyways unless this is explicitly
>> disabled, which is done with gcc via th
On Wed, Apr 21, 2010 at 8:47 AM, Adrien Guillon wrote:
> Hello all,
>
> I've recently started to use NumPy to prototype some numerical
> algorithms, which will eventually find their way to a GPU (where I
> want to limit myself to single-precision operations for performance
> reasons). I have rece
ke, 2010-04-21 kello 10:47 -0400, Adrien Guillon kirjoitti:
[clip]
> My understanding, however, is that Intel processors may use extended
> precision for some operations anyways unless this is explicitly
> disabled, which is done with gcc via the -ffloat-store operation.
> Since I am prototyping al
Hello all,
I've recently started to use NumPy to prototype some numerical
algorithms, which will eventually find their way to a GPU (where I
want to limit myself to single-precision operations for performance
reasons). I have recently switched to the use of the "single" type in
NumPy to ensure I
On Tue, Apr 20, 2010 at 18:45, Charles R Harris
wrote:
>
> On Tue, Apr 20, 2010 at 7:03 AM, Andreas Hilboll wrote:
>>
>> Hi there,
>>
>> is there an easy way to do something like trim_zeros() does, but for a
>> n-dimensional array? I have a 2d array with only zeros in the first and
>> last rows a
On Wed, Apr 21, 2010 at 1:52 AM, Sebastian Haase wrote:
> On Tue, Apr 20, 2010 at 2:23 AM, Ralf Gommers
> wrote:
> > It seems I've crawled a bit further up the learning curve since last time
> I
> > tried. Scipy binaries for python 2.5 (built against numpy 1.2) are now on
> > Sourceforge, please
Dan Roberts wrote:
> Thanks for the reply. You're certainly right that your work is
> extremely beneficial to mine. At present I'm afraid a great deal of
> NumPy C code isn't easily reusable and it's great you're addressing
> that. I may not have been thinking in line with Maciej, but I was
On Tue, Apr 20, 2010 at 10:34 AM, Christopher Barker
wrote:
>
>
> Pradeep Jha wrote:
>> Thank you so much Robert. You are awesome :) That totally the problem.
>> One more question for you. Which are the things that you have to
>> declare in PYTHONPATH manually?
>
> I never put anything in PYTHONP
Oops, I intended to dig more through the NumPy source before I sent the
final version of that message, so I could be speaking from an informed
standpoint.
Thanks,
Daniel Roberts
>
> ___
> NumPy-Discussion mailing list
> NumPy-Discuss...
--
Travis O
Thanks for the reply. You're certainly right that your work is extremely
beneficial to mine. At present I'm afraid a great deal of NumPy C code
isn't easily reusable and it's great you're addressing that. I may not have
been thinking in line with Maciej, but I was thinking ufuncs would be
writte
Stéfan van der Walt sun.ac.za> writes:
>
> I haven't checked your code in detail, but I'll mention two common
> problems with this approach in case it fits:
>
> 1) When convolving a KxL with an MxN array, they both need to be zero
> padded to (K+M-1)x(L+N-1).
> 2) One of the signals needs to be
Dag Sverre Seljebotn wrote:
> Ralf Gommers wrote:
>> Hi,
>>
>> I am pleased to announce the third release candidate of both Scipy
>> 0.7.2 and NumPy 1.4.1. Please test, and report any problems on the
>> NumPy or SciPy list.
>
> I had a round of segfaults in the SciPy/NumPy interlink, which I
>
Ralf Gommers wrote:
> Hi,
>
> I am pleased to announce the third release candidate of both Scipy 0.7.2
> and NumPy 1.4.1. Please test, and report any problems on the NumPy or
> SciPy list.
I had a round of segfaults in the SciPy/NumPy interlink, which I
eventually tracked down to a leftover _d
On Tue, Apr 20, 2010 at 7:03 AM, Andreas Hilboll wrote:
> Hi there,
>
> is there an easy way to do something like trim_zeros() does, but for a
> n-dimensional array? I have a 2d array with only zeros in the first and
> last rows and columns, and would like to trim this array to only the
> non-zer
On Tue, Apr 20, 2010 at 2:23 AM, Ralf Gommers
wrote:
>
>
> On Mon, Apr 19, 2010 at 9:19 PM, Ralf Gommers
> wrote:
>>
>>
>> On Mon, Apr 19, 2010 at 4:21 PM, Ralf Gommers
>> wrote:
>>>
>>>
>>> On Mon, Apr 19, 2010 at 3:35 PM, Sebastian Haase
>>> wrote:
Hi,
Congratulations. I might
On Tue, Apr 20, 2010 at 6:03 AM, Andreas Hilboll wrote:
> Hi there,
>
> is there an easy way to do something like trim_zeros() does, but for a
> n-dimensional array? I have a 2d array with only zeros in the first and
> last rows and columns, and would like to trim this array to only the
> non-zero
20 matches
Mail list logo
