Re: [Numpy-discussion] ndimage.label - howto force SWIG to use int32 - even on 64bit Linux ?
Hi Sebastian On 27 April 2010 10:27, Sebastian Haase seb.ha...@gmail.com wrote: Hi, I wanted to write some C code to accept labels as they come from ndimage.label. For some reason ndimage.label produces its output as an int32 array - even on my 64bit system . I've merged Thouis's patch to implement scikits.image.measurements in pure Python. Would you please try the SVN version and see if it solves your problem, and also whether it performs to your satisfaction? Regards Stéfan ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] proposing a beware of [as]matrix() warning
On Wed, Apr 28, 2010 at 2:46 PM, David Warde-Farley d...@cs.toronto.edu wrote: Would it be acceptable to retain the matrix class but not have it imported in the default namespace, and have to import e.g. numpy.matlib to get at them? +1 Jarrod ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Question about numpy.arange()
Hello, Is b an expected value? I am suspecting another floating point arithmetic issue. I[1]: a = np.arange(1.6, 1.8, 0.1, dtype='float32') I[2]: a O[2]: array([ 1.6002, 1.7005], dtype=float32) I[3]: b = np.arange(1.7, 1.8, 0.1, dtype='float32') I[4]: b O[4]: array([ 1.7005, 1.7995], dtype=float32) A bit conflicting with the np.arange docstring: * Values are generated within the half-open interval ``[start, stop)`` (in other words, the interval including `start` but excluding `stop`). * Thanks. -- Gökhan ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
