[Numpy-discussion] NumPy-Discussion Digest, Vol 66, Issue 61
Tue Mar 20 07:13:15 CDT 2012
Thanks for your answer and the related help !
In fact, I was hoping to have a less memory and more speed solution. Something
equivalent to a "raster calculator" for numpy. Wouldn't it make sense to have
some optimized function to work on more than 2 arrays for numpy anyway ?
At the end, I am rather interested by more speed.
I tried first a code-sparing version :
array = numpy.asarray([(aBlueChannel < 1.0),(aNirChannel > aBlueChannel *
1.0),(aNirChannel < aBlueChannel * 1.8)]).all()
But this one is at the end more than 2 times slower than :
array1 = numpy.empty([3,6566,6682], dtype=numpy.bool)
numpy.less(aBlueChannel, 1.0, out=array1)
numpy.greater(aNirChannel, (aBlueChannel * 1.0), out=array1)
numpy.less(aNirChannel, (aBlueChannel * 1.8), out=array1)
array = array1.all()
(and this solution is about 30% faster than the original one)
I could find another way which was fine for me too:
array = (aBlueChannel < 1.0) * (aNirChannel > (aBlueChannel * 1.0)) *
(aNirChannel < (aBlueChannel * 1.8))
But this one is only 5-10% faster than the original solution, even if probably
using less memory than the 2 previous ones. (same was possible with operator
+, but slower than operator *)
On Monday 19 March 2012 18:00:02 firstname.lastname@example.org wrote:
> Message: 2
> Date: Mon, 19 Mar 2012 13:20:23 +0000
> From: Richard Hattersley <email@example.com>
> Subject: Re: [Numpy-discussion] Using logical function on more than 2
> arrays, availability of a "between" function ?
> To: Discussion of Numerical Python <firstname.lastname@example.org>
> > Content-Type: text/plain; charset=ISO-8859-1
> What do you mean by "efficient"? Are you trying to get it execute
> faster? Or using less memory? Or have more concise source code?
> Less memory:
> - numpy.vectorize would let you get to the end result without any
> intermediate arrays but will be slow.
> - Using the "out" parameter of numpy.logical_and will let you avoid
> one of the intermediate arrays.
> More speed?:
> Perhaps putting all three boolean temporary results into a single
> boolean array (using the "out" parameter of numpy.greater, etc) and
> using numpy.all might benefit from logical short-circuiting.
> And watch out for divide-by-zero from "aNirChannel/aBlueChannel".
> Richard Hattersley
14776 Brandenburg an der Havel
Follow us on Twitter! www.twitter.com/rapideye_ag
Head Office/Sitz der Gesellschaft: Brandenburg an der Havel
Management Board/Vorstand: Ryan Johnson
Chairman of Supervisory Board/Vorsitzender des Aufsichtsrates:
Commercial Register/Handelsregister Potsdam HRB 24742 P
Tax Number/Steuernummer: 048/100/00053
VAT-Ident-Number/Ust.-ID: DE 199331235
DIN EN ISO 9001 certified
More information about the NumPy-Discussion