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
You are taking the histogram of a float image, so it's casting it to uint16 before scanning. Five bins on a range of 0 - 65535 means each bin is more than 10,000 wide, so all your values fall in bin 0. If you cast to uint8 (uchar) yourself, you should see something more expected.
It's best to fix the range, of course. C is roughly -128 to 128, and h is 0 - 360, so you can move them to 0 - 255 like this:
(perhaps the histogram functions should always cast to uchar, with ushort as an option you have to turn on explcitly? It might be less surprising ... though it's too late to change the behaviour now, unfortunately)
I'm trying to get an ndim histogram of the CH part of an image:
(here's the image: )
Why are all values counted into 0,0,0?
The documentation says something about casting (
hist_find_ndim
), but still most of the values should be in range, shouldn't they?The text was updated successfully, but these errors were encountered: