On Fri, Aug 23, 2013 at 6:02 AM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
Hi folks,
I had thought that maybe a numpy.long dtype was a system
(compiler)-native C long.
But on both 32 and 64 bit python on OS-X, it seems to be 64 bit. I'm
pretty sure that on OS-X 32 bit, a C
These things may depend on how the compiler implements various calls. Some
errors went the other way with Julian's SIMD work, i.e., errors getting set
that were not set before. I'm not sure what can be done about it.
On Thu, Aug 22, 2013 at 8:32 PM, Warren Weckesser
warren.weckes...@gmail.com
On 8/22/2013 10:32 PM, Warren Weckesser wrote:
Christoph
reported that this code:
```
import numpy as np
data = np.array([-0.375, -0.25, 0.0])
s = np.log(data)
```
does not generate two RuntimeWarnings when it is run with numpy 1.7.1
in a 32 bit Windows 8 environment (numpy 1.7.1
Probably the thing to do for reliable behaviour is to decide on the
behaviour we want and then implement it by hand. I.e., either clear the
FP flags inside the ufunc loop (if we decide that log shouldn't raise a
warning), or else check for nan and set the invalid flag ourselves.
(Checking for nan
On Fri, Aug 23, 2013 at 6:29 AM, Nathaniel Smith n...@pobox.com wrote:
Probably the thing to do for reliable behaviour is to decide on the
behaviour we want and then implement it by hand. I.e., either clear the
FP flags inside the ufunc loop (if we decide that log shouldn't raise a
warning),
Hi José,
The code is somewhat longish for a pure visual inspection, but my advice is
that you install memory profiler (
https://pypi.python.org/pypi/memory_profiler). This will help you
determine which line or lines are hugging the memory the most.
Saludos,
Francesc
On Fri, Aug 23, 2013 at
On Fri, Aug 23, 2013 at 10:34 AM, Francesc Alted franc...@continuum.iowrote:
Hi José,
The code is somewhat longish for a pure visual inspection, but my advice
is that you install memory profiler (
https://pypi.python.org/pypi/memory_profiler). This will help you
determine which line or
On Aug 22, 2013, at 11:57 PM, David Cournapeau courn...@gmail.com wrote:
npy_long is indeed just an alias to C long,
Which means it's likely broken on 32 bit platforms and 64 bit MSVC.
np.long is an alias to python's long:
But python's long is an unlimited type--it can't be mapped to a c type
On Fri, 2013-08-23 at 07:59 -0700, Chris Barker - NOAA Federal wrote:
On Aug 22, 2013, at 11:57 PM, David Cournapeau courn...@gmail.com
wrote:
snip
arch -32 python -c import numpy as np; print np.dtype(np.int);
print np.dtype(np.long)
int32
int64
So this is giving us a 64 bit
On Fri, Aug 23, 2013 at 8:59 AM, Chris Barker - NOAA Federal
chris.bar...@noaa.gov wrote:
On Aug 22, 2013, at 11:57 PM, David Cournapeau courn...@gmail.com wrote:
npy_long is indeed just an alias to C long,
Which means it's likely broken on 32 bit platforms and 64 bit MSVC.
np.long is an
On Fri, Aug 23, 2013 at 8:11 AM, Sebastian Berg
sebast...@sipsolutions.net wrote:
So this is giving us a 64 bit int--not a bad compromise, but not a
python long--I've got to wonder why the alias is there at all.
It is there because you can't remove it :).
sure we could -- not that we'd want
On Fri, Aug 23, 2013 at 8:15 AM, Charles R Harris
charlesr.har...@gmail.com wrote:
I use 'bBhHiIlLqQ' for the C types. Long varies between 32 64 bit,
depending on the platform and 64 bit convention chosen. The C int is always
32 bits as far as I know.
Well, not in the spec, but in practice,
On 23 August 2013 16:59, Benjamin Root ben.r...@ou.edu wrote:
A lot of the code you have here can be greatly simplified. I would start
with just trying to get rid of appends as much as possible and use
preallocated arrays with np.empty() or np.ones() or the likes.
Also, if you don't know
In article
CAH6Pt5o32Otdhk2Ms5Cy5Zo=mn48h8x2wbswk92etub4mmr...@mail.gmail.com,
Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Thu, Aug 22, 2013 at 12:14 PM, Russell E. Owen ro...@uw.edu wrote:
In article
cabl7cqjacxp2grtt8hvmayajrm0xmtn1qt71wkdnbgq7dlu...@mail.gmail.com,
Ralf
Hi,
On Fri, Aug 23, 2013 at 1:32 PM, Russell E. Owen ro...@uw.edu wrote:
In article
CAH6Pt5o32Otdhk2Ms5Cy5Zo=mn48h8x2wbswk92etub4mmr...@mail.gmail.com,
Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Thu, Aug 22, 2013 at 12:14 PM, Russell E. Owen ro...@uw.edu wrote:
In article
Hi experts!
I wrote an algorithm for study stick percolation (i.e.: networks between line
segments that intersect between them). In my algorithm N sticks (line segments)
are created inside a rectanglar box of sides 'b' and 'h' and then, one by one,
the algorithm explores the intersection
Hi,
On Fri, Aug 23, 2013 at 1:38 PM, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Fri, Aug 23, 2013 at 1:32 PM, Russell E. Owen ro...@uw.edu wrote:
In article
CAH6Pt5o32Otdhk2Ms5Cy5Zo=mn48h8x2wbswk92etub4mmr...@mail.gmail.com,
Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On
17 matches
Mail list logo
