Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • $\begingroup$ It still can be a bug, as author could erroneously think that Matlab has a problem with first pair of indices. $\endgroup$ Commented Oct 19, 2017 at 21:07
  • $\begingroup$ @Dims Please contact Wolfram Support and let them know about this problem (then tell us what they said). $\endgroup$ Commented Oct 19, 2017 at 22:09
  • $\begingroup$ @Dims I think it does make sense in a way because MATLAB often presents 3D arrays (conceptually) as a "list of pages/slices" where each page is a matrix. That's also how it displays them. The way Import handles the data conforms with that view: we get a list of the same matrices in Mathematica as we saw at the MATLAB command line. Except that MATLAB uses the last index for the pages while Mathematica uses the first. $\endgroup$ Commented Oct 20, 2017 at 16:34
  • $\begingroup$ @Dims Of course once one starts looking at higher dimensional arrays, this does not generalize very well. That's why we did not make this choice in MATLink (but that was a long time ago and I forgot most of the discussions). I guess the most intuitive index handling depends on the specific application. I prefer MATLink's. $\endgroup$ Commented Oct 20, 2017 at 16:35