input datatype about mitoolbox HOT 7 CLOSED

Yes, the C code expects all the inputs to be doubles, and it assumes that any input handed by Matlab will be a double (through an explicit cast). The Matlab wrappers probably should be modified to test the arrays and convert them to doubles first, though this will be slow if the user doesn't realise it's happening.

from mitoolbox.

Hello, I have faced the same problem as @iBM88 had until I started looking for help online.
I think this should be written in the README since it's quite an important thing.
Also there are some kinds of inputs which make MATLAB crash (at least in R2015a), for example when they are matrices instead of column vectors.

from mitoolbox.

I'll work on the README at the weekend, it could do with a touch up.

What kind of inputs make it crash? Is this directly calling the mex functions or using the MATLAB wrappers?

from mitoolbox.

Matrix inputs and uint8 vectors. It crashed calling the MATLAB wrapper mi.

from mitoolbox.

So you called mi(X,Y) where X & Y were both matrices of uint8 values?

from mitoolbox.

Yes, for example:
I = imread('cameraman.tif');
mi(I,I) --> crashes
mi(I(:),(:)) --> crashes

On Thu, Jan 7, 2016 at 10:57 AM, Adam Pocock [email protected]
wrote:

So you called mi(X,Y) where X & Y were both matrices of uint8 values?

—
Reply to this email directly or view it on GitHub
#1 (comment).

from mitoolbox.

Ok. I've added checks to the MATLAB wrappers so they reject inputs which aren't doubles. It should now throw an error message rather than crashing MATLAB.

from mitoolbox.