You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following discussion in here, I'd like to raise an issue about IJM.show().
IJM.show('I') or net.imagej.matlab.ImageJMATLABCommands.show('I') is a great way to transfer array data from MATLAB workspace to ImageJ, thanks to ImageJ-MATLAB.
However, I’ve noticed that X and Y of axes of images are flipped over between MATLAB and ImageJ, which is not smart at all.
MATLAB's permute can manipulate data to avoid this problem. But, because it apparently needs to copy data internally, it requires double memory, which is not ideal. An imglib2 /ImageJ2 -style permute (which re-indexes but does not copy) might be a better solution.
This issue is also related, but more specifically about multidimensional images.
This issue doesn't only affect IJM.show() but in general the conversion between IJ and Matlab. For example, data input by #@ script parameters suffer from the same issue:
Following discussion in here, I'd like to raise an issue about
IJM.show()
.IJM.show('I')
ornet.imagej.matlab.ImageJMATLABCommands.show('I')
is a great way to transfer array data from MATLAB workspace to ImageJ, thanks toImageJ-MATLAB
.However, I’ve noticed that X and Y of axes of images are flipped over between MATLAB and ImageJ, which is not smart at all.
MATLAB's
permute
can manipulate data to avoid this problem. But, because it apparently needs to copy data internally, it requires double memory, which is not ideal. An imglib2 /ImageJ2 -style permute (which re-indexes but does not copy) might be a better solution.This issue is also related, but more specifically about multidimensional images.
#17
The text was updated successfully, but these errors were encountered: