Mon 14 Jan 2013 10:36:25 PM UTC, original submission:
This bug was originally reported on the mailing list by Giorgio Denunzio <giorgio.denunzio@unisalento.it> on 2012/10/21
input parameters:
1) matlab wants vectors, one row for each distance/direction couple, and the necessary information is a vector with x- and y- components, describing the particular relative-position vector(s) we are interested in ('Offset' parameter) (no idea if I was clear… perhaps it is better to try matlab help :-) ; octave wants distinct angles (degrees) and distances:
2) matlab implicitly transforms the input-image bit depth ('NumLevels' parameter), while octave needs that you change it beforehand; matlab wants to know the limits of gray level values ('GrayLimits' parameter), octave does not (I do not know if it assumes the whole range of possible values in accordance with the bit depth, or it calculates min and max from the image data (I suppose the former is correct, but I have not checked yet).
Octave just wants to know how many levels are there (not their values). Anyway I still have to totally verify this. The output is also different because octave gives a 4D matrix (numlevels x numlevels x distances x angles, iirc), while matlab gives a 3D matrix:
|