Am Sonntag, 20. Januar 2008 23:15:24 schrieb Travis Vaught:
On Jan 20, 2008, at 3:30 PM, Charles R Harris wrote:
Thanks for the attention to this...I think we need to seek continual
improvement to the web site (numpy's default pages, again, could use
some TLC). I've tweaked the bug a bit
A Sunday 20 January 2008, Nicholas escrigué:
I am trying to package a set of vector arrays into a single rec array
with column titles.
c = numpy.rec.fromarrays([a,b],names='a,b')
the problem is there is no 'copy' argument in .fromarrays which I can
set to False. i.e. is there a way to do
Hi,
If I remember correctly then the warnings were disabled because
when compiling numpy/scipy on windows there were *lots* of
warnings, especially for pyrex generated sources.
When there is an error, all warnings will be shown. Hmm, and on
linux the warnings should also be shown (this actually
Neal Becker wrote:
I noticed that if I generate complex rv i.i.d. with var=1, that numpy
says:
var (real part) - (close to 1.0)
var (imag part) - (close to 1.0)
but
var (complex array) - (close to complex 0)
Is that not a strange definition?
I don't think there is any ambiguity
Hello all,
I'm scratching my head over how to make this image color space conversion
from RGB to HSV quicker. It requires input from all three bands of a
given pixel at each pixel, and thus can't be easily flattened. I've already
implemented psyco and removed the extra step of calling
Hi,
The following will cause a bus error on a big endian machine (Solaris 10
Sun in this case):
Python 2.5.1 (r251:54863, Jun 29 2007, 15:29:55) [C] on sunos5
Type help, copyright, credits or license for more information.
import numpy
o = numpy.ndarray(shape=3,dtype=[('SEGMENT', '|S4'),
Am Montag, 21. Januar 2008 15:39:21 schrieb theodore test:
Right now it takes around 9 seconds for a single 1600x1200 RGB image, a
conversion that I've seen implemented more or less instantly in, say,
ImageJ. What can I do to make this conversion more efficient?
You should just remove the
Pearu Peterson wrote:
Hi,
If I remember correctly then the warnings were disabled because
when compiling numpy/scipy on windows there were *lots* of
warnings, especially for pyrex generated sources.
Yes, that's certainly one of the thing I intend to improve with numscons
:) (as an aside,
| Date: Mon, 21 Jan 2008 09:39:21 -0500
| From: theodore test [EMAIL PROTECTED]
|
| Hello all,
|
| I'm scratching my head over how to make this image color space
| conversion from RGB to HSV quicker. It requires input from all
| three bands of a given pixel at each pixel, and thus can't
Hi,
I don't know if this is known, but since I wasted half a day on it,
I thought I could avoid the pain for someone else: do not build numpy
with -fomit-frame-pointer with mingw (windows), it will crash. I don't
know if this just cannot be used, if this is a mingw bug, or something
on
Did you include arrayobject.h and call import_array()
in the initialization function, after the call to
Py_InitModule() ?
--- Danny Chan [EMAIL PROTECTED] wrote:
Hi!
I am trying to compile a c extension that uses numpy
arrays on windows. I can compile the extension file,
but once I get to
Neal Becker wrote:
Neal Becker wrote:
I noticed that if I generate complex rv i.i.d. with var=1, that numpy
says:
var (real part) - (close to 1.0)
var (imag part) - (close to 1.0)
but
var (complex array) - (close to complex 0)
Is that not a strange definition?
I don't think there
Hi,
I don't know the area but following your code I would suggest the
completely untested code. I am not sure about the conditions to get h
so I leave you get to the correct h and transform it appropriately.
Bruce
# First create 2 dimensional array/matrix (number of pixels by three):
'rows' are
Hi,
Search for the docstring standard, I hit this:
http://www.scipy.org/DocstringStandard
but I think the current thinking is this:
http://projects.scipy.org/scipy/numpy/wiki/CodingStyleGuidelines
Is that correct? Does the first page apply to matplotlib in some way?
Should we change the first
Hi Theodore
Probably not the fastest, but a full example of how you may vectorize your loop.
Ran just one test, and that speeded up the original code.
Example:
from numpy import empty_like
def vectorized_rgb2hsv(im):
im is a (m, n, 3) array.
im = im/255.
out =
On Jan 21, 2008 2:03 PM, Matthew Brett [EMAIL PROTECTED] wrote:
Search for the docstring standard, I hit this:
http://www.scipy.org/DocstringStandard
Good catch, I didn't know this page existed. If I recall correctly,
Keir Mierle showed up on the mailing list around the time we were
On Jan 21, 2008 6:09 PM, Jarrod Millman [EMAIL PROTECTED] wrote:
On Jan 21, 2008 2:03 PM, Matthew Brett [EMAIL PROTECTED] wrote:
Search for the docstring standard, I hit this:
http://www.scipy.org/DocstringStandard
Good catch, I didn't know this page existed. If I recall correctly,
Pierre GM wrote:
On Sunday 20 January 2008 16:32:40 you wrote:
Pierre,
The attached script shows how one can make a masked array with different
dimensions for the mask than for the data. I presume this is a bug. It
is triggered by the present code in the matplotlib quiver function.
Yep,
On Jan 21, 2008 8:38 PM, Charles R Harris [EMAIL PROTECTED] wrote:
On Jan 21, 2008 6:09 PM, Jarrod Millman [EMAIL PROTECTED] wrote:
On Jan 21, 2008 2:03 PM, Matthew Brett [EMAIL PROTECTED] wrote:
Search for the docstring standard, I hit this:
http://www.scipy.org/DocstringStandard
David Cournapeau wrote:
Nobody likes to write doc, specially if you have to follow many rules.
Not being able to see the result does not help. I don't know much
about the current documation tools situation with python, but I have
seen good, automatically generated doc for python modules: for
On Jan 21, 2008 7:56 PM, Charles R Harris [EMAIL PROTECTED] wrote:
On Jan 21, 2008 8:38 PM, Charles R Harris [EMAIL PROTECTED] wrote:
If I hit the source code link in the generated html, it looks like that
page was generated from the old document format. The new document format
doesn't
Hi,
I need to use numpy in an environment which does not support shared libraries.
Previously, I have used the old Numeric where I created a Makefile to build a
static Numeric library which was later on linked to the python interpreter.
As far as I understood, numpy uses sort of extended
Hi,
I think the main problem would be that some parts of Numpy are coded in C
and that they must be compiled as a shared library so that Python can access
them.
Matthieu
2008/1/22, Jussi Enkovaara [EMAIL PROTECTED]:
Hi,
I need to use numpy in an environment which does not support shared
Hi all,
Just a quick reminder for all about the upcoming Sage/Scipy Days 8 at
Enthought collaborative meeting:
http://wiki.sagemath.org/days8
Email me directly ([EMAIL PROTECTED]) if you plan on coming,
so we can have a proper count and plan accordingly.
Cheers,
f
On Jan 21, 2008 11:27 PM, Robert Kern [EMAIL PROTECTED] wrote:
Charles R Harris wrote:
On Jan 21, 2008 6:09 PM, Jarrod Millman [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
On Jan 21, 2008 2:03 PM, Matthew Brett [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Jussi Enkovaara wrote:
Hi,
I need to use numpy in an environment which does not support shared libraries.
Previously, I have used the old Numeric where I created a Makefile to build a
static Numeric library which was later on linked to the python interpreter.
As far as I understood, numpy
26 matches
Mail list logo
