[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54614] [octave forge] (image) wrong results o

From: Hartmut
Subject: [Octave-bug-tracker] [bug #54614] [octave forge] (image) wrong results of entropyfilt
Date: Tue, 9 Oct 2018 16:03:08 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Follow-up Comment #7, bug #54614 (project octave):

The general scheme in patch #9235 is the following (for example in

-  retval = __spatial_filtering__ (I, domain, "entropy", I, nbins);
+  retval = __spatial_filtering__ (I, domain, "entropy", zeros (size (I)),

The problem with this approach is (I think Carne mentioned this a long while
ago), that we then use double the amount of memory. And the memory for the
zeros is not very useful at all :(

Do you have a clever idea, how to
* use __spatial_filtering__ (keeping its 4t input argument alive)
* not use more memory than necessary
* and still be able to tell __spatial_filtering__ in most use cases to NOT add
this forth argument to the result?

Maybe we could find a trick inside __spatial_filtering__ to treat an EMPTY
forth argument as a matrix of zeros (of size(I)) , but without actually
requirement memory for all those zeros? Do you have a clever idea how to
implement this in __spatial_filtering__?


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]