imcrop function problem for 16bit image 2019b

2 次查看（过去 30 天）

显示更早的评论

Meshooo 2019-9-20

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/481286-imcrop-function-problem-for-16bit-image-2019b

评论： Meshooo 2019-10-18

采纳的回答： Walter Roberson

在 MATLAB Online 中打开

Dear all,

The following imcrop code gives an error in 2019b

I = imread('XX.tif');
[Icrop, rect] = imcrop(I, [ ]);

It seems that 2019b does't support [ ] with imcrop. If you are working with 16 bit images then you will be in trouble because you need to see the image before croping it, and for that you need to put the [ ].

Any idea how to overcome this problem?

Thank you in advance.

Meshoo

6 个评论
显示 4更早的评论隐藏 4更早的评论

Meshooo 2019-10-11

编辑：Meshooo 2019-10-11

Hi Walter,

I couldn't understand exactly what do you mean. I am just runing my old codes in 2019 and got an error.

People working with uint16 images usually use [ ] to show the image on their screens, for example: imshow(I_unit16, [ ]).

Similarly, we need to use [ ] when croping uint16 image in order to dispaly the image before cropping it. That was possible in older versions of MATLAB but not in 2019b.

Regards,

Meshoo

Walter Roberson 2019-10-12

在 MATLAB Online 中打开

Please name a particular release that documents using [] as a parameter to imcrop() . I looked through the archived documentation for several releases and could not find any evidence that it was ever a supported option.

Similarly, we need to use [ ] when croping uint16 image in order to dispaly the image before cropping it.

So display the image with imshow() with the documented [] option, and call imcrop() on the handle returned by imshow:

h = imshow(I, []);
[Icrop, rect] = imcrop(h);

请先登录，再进行评论。

请先登录，再回答此问题。

采纳的回答

Walter Roberson 2019-10-12

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/481286-imcrop-function-problem-for-16bit-image-2019b#answer_396060

在 MATLAB Online 中打开

h = imshow(I, []);
[Icrop, rect] = imcrop(h);

9 个评论
显示 7更早的评论隐藏 7更早的评论

Image Analyst 2019-10-18

Then you'll be making a lot of bug reports. There is a constant flow of functions either changing inputs, being deprecated, or being removed completely as versions progress through the years. I don't see how that, either filing bug reports or writing a custom wrapper and calling that from your code, is any better than just hitting the delete key 3 times.

Meshooo 2019-10-18