John, you want c.compressed().
John Hunter wrote:
I'm a bit of an ma newbie. I have a 2D masked array R and want to
extract the non-masked values in the last column. Below I use logical
indexing, but I suspect there is a built-in way w/ masked arrays. I
read through the docstring, but didn't
Christopher Barker wrote:
Joe Harrington wrote:
My
suggestion is that all the other pages be automatic redirects to the
scipy.org page or subpages thereof.
+1
if that means something like:
www.numpy.scipy.org (or www.scipy.org/numpy )
Then I'm all for it.
I just made
I've put together some .debs for numpy-0.9.8. There are binaries
compiled for amd64 and i386 architectures of Ubuntu Dapper, and I
suspect these will build from source for just about any Debian-based
distro and architecture.
The URL is http://sefton.astraw.com/ubuntu/dapper and you would add
Erin Sheldon wrote:
Anyway - Recarrays have convenience attributes such that
fields may be accessed through . in additioin to
the field() method. These attributes are designed for
read only; one cannot alter the data through them.
Yet they are writeable:
tr=numpy.recarray(10,
I noticed in your note labeled 'June 16, 2006' that you refer to the
desc field. However, in the struct description above, there is only a
field named descr.
Also, I suggest that you update the information in the comments of descr
field of the structure description to contain the fact that
David Cournapeau wrote:
That's great. Last week, I sended several messages to the list
regarding your messages about debian packages for numpy, but it looks
they were lost somewhere
Right now, I use the experimental package of debian + svn sources for
numpy, and it works well. Is
GNU libc version 2.3.2 has a bug[1] feclearexcept() error on CPUs with
SSE (fixed in 2.3.3) which has been submitted to Debian[2] but not
fixed in sarge.
See http://www.its.caltech.edu/~astraw/coding.html#id3 for more
information and .debs which fix the problem.
[1]
Sasha wrote:
On 7/24/06, Travis Oliphant [EMAIL PROTECTED] wrote:
Andrew Straw has emphasized that the current strategy of appending the
SVN version number to development versions of the SVN tree makes it hard
to do version sorting.
I am not sure what the problem is, but if the concern
David wrote:
Stephan Tolksdorf wrote:
Hi
A user named jlc46 is misusing the wiki page Installing SciPy/Windows
to ask for help on his installation problems. How can I
a) contact him in order to ask him to post his questions on the mailing
lists, and
You cannot find out his email
Dear Albert,
I have started to use numpy and ctypes together and I've been quite
pleased. Thanks for your efforts and writings on the wiki.
On the topic of ctypes but not directly following from your email: I
noticed immediately that the .ctypes attribute of an array is going to
be a de-facto
Sven Schreiber wrote:
Hi,
Satya Upadhya schrieb:
from Numeric import *
Well this list is about the numpy package, but anyway...
This list is for numpy, numarray, and Numeric. There's just a lot more
numpy talk going on these days, but numpy-discussion comes from the
bad
The following code indicates there is a problem adding a numpy scalar
type to a Numeric array. Is this expected behavior or is there a bug
somewhere?
This bit me in the context of updating some of my code to numpy, while
part of it still uses Numeric.
import Numeric
import numpy
print
Travis Oliphant wrote:
Sebastian Haase wrote:
Travis Oliphant wrote:
It's not necessarily dead, the problem is complexity of implementation
and more clarity about how all dtypes are supposed to be printed, not
just this particular example. A patch would be very helpful
William Grant wrote:
Hi,
I'm currently attempting to get scipy 0.5.1 into Ubuntu, however it
currently cannot happen as numpy doesn't build with Python 2.5. I note
that changeset 3109
(http://projects.scipy.org/scipy/numpy/changeset/3109#file1) is meant to
give 2.5 compatibility, but it is those
It is a wiki, and contributions are absolutely welcome, so please go
ahead and change it to be more clear.
Bill Baxter wrote:
I think that's supposed to be covered by this line:
The default array data-type is now float64 (c double precision)
instead of c integer.
But yeh, I agree. It's
It sounds like your hardware drivers may be buggy -- you should only get
segfaults, not (the Windows equivalent of) kernel panics, when your
userspace code accesses wrong memory.
But if you have buggy hardware drivers, I suppose it's possible that
locking the memory will help. This wouldn't be
David Cournapeau wrote:
I don't know anything about your device, but a driver directly accessing
a memory buffer from a userland program sounds like a bug to me.
David, DMA memory (yes, I know thats an example of RAS Syndrome,
apologies) allows hardware to fill a chunk of RAM and then hand it
Fernando Perez wrote:
Here is some more info. We left a long-running job over the weekend
with the prints you suggested. Oddly, something happened at the OS
level which killed our SSH connection to that machine, but the above
numpy dealloc() warning never printed (we logged this).
As an
David Cournapeau wrote:
- To send data from the calling process to matlab, you first have to
create a mxArray, which is the basic matlab handler of a matlab array,
and populating it. Using mxArray is very ackward : you cannot create
mxArray from existing data, you have to copy data to
David Cournapeau wrote:
Andrew Straw wrote:
David Cournapeau wrote:
- To send data from the calling process to matlab, you first have to
create a mxArray, which is the basic matlab handler of a matlab array,
and populating it. Using mxArray is very ackward : you cannot
David Cournapeau wrote:
Andrew Straw wrote:
David Cournapeau wrote:
- To send data from the calling process to matlab, you first have to
create a mxArray, which is the basic matlab handler of a matlab array,
and populating it. Using mxArray is very ackward : you cannot
21 matches
Mail list logo
