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
Seems like there has been a regression or change of behaviour in
IJ, around ROIs and getting bounds.
This code change makes ROI handling more explicit and uses only
ImagePlus methods (not ImageProcessor or ImageStack).
Fixes#345
Seems like there has been a regression or change of behaviour in
IJ, around ROIs and getting bounds.
This code change makes ROI handling more explicit and uses only
ImagePlus methods (not ImageProcessor or ImageStack).
Fixes#345
Seems like there has been a regression or change of behaviour in
IJ, around ROIs and getting bounds.
This code change makes ROI handling more explicit and uses only
ImagePlus methods (not ImageProcessor or ImageStack).
Fixes#345
Describe the bug
Slice Geometry doesn't respect ROIs and then complains there isn't an ROI when there is one
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Slice Geometry runs using either the whole image if there is no ROI, or only the pixels inside the ROI if an ROI is set
Additional context
https://forum.image.sc/t/second-moment-of-area-imin-and-imax/47098/14
The text was updated successfully, but these errors were encountered: