Hi Evgeny, are you using the "ToArray" function? This function does change some properties while converting the array from MATLAB to .NET data type. This is because .NET follows a different convention from that of MATLAB.
1) The dimension ordering is changed from [i j k] to [k i j]. This is because MATLAB follows the column major order and .NET follows the row major order convention. But the rank of the matrix remains the same.
2) The index bound changes from [1,n] to [0,n-1]. The change in index bounds is expected, because in .NET the index starts with 0 and in MATLAB the index starts with 1.
For example, the index-bound from 1 to 10 in MATLAB becomes 0 to 9 in .NET.
Example:
Consider a 2x3x4 3D MWNumericArray ‘item1’. When you convert it into .NET array it becomes a 4x2x3 3D array. Let us call the converted array as ‘CArray’.
Now, suppose you change the value of MWNumeric array at location item1[1,3,2] to 100.
Now since [i j k] becomes [k i j], you would expect the value of CArray[2,1,3] to become 100.
But this is not the case. Since the index of .NET array starts with 0,
CArray[1,0,2] would be 123. I just subtracted 1 from each index and [2, 1, 3] became [1, 0, 2].
The following link explains the various data conversion rules that MATLAB follows while converting data from MATLAB to .NET data type or vice versa.
