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
I noticed that vedo.Volume uses the xyz order instead of conventionally used zyx. For example, when loading an image with vedo.load(image), the array order is xyz, but the io.imread(image) from skimage and tifffile etc. returns zyx. I am swapping x and z for now, but it might be the best to use zyx order by default.
Thanks!
Shaohe
The text was updated successfully, but these errors were encountered:
Hi! You are right and this is quite annoying.. vedo always assumes real world coordinates and I'm afraid it is too late to change convention on this one.. But I understand it can be a source of confusion.
I can add some documentation and maybe a keyword option , something like Volume(..., assume_zyx=True)
is maybe helpful?
Hi Marco,
I noticed that vedo.Volume uses the xyz order instead of conventionally used zyx. For example, when loading an image with vedo.load(image), the array order is xyz, but the io.imread(image) from skimage and tifffile etc. returns zyx. I am swapping x and z for now, but it might be the best to use zyx order by default.
Thanks!
Shaohe
The text was updated successfully, but these errors were encountered: