On Thursday, 18 May 2017 15:08:22 BST you wrote:
> But it is sure incredibly slow
Yep, it is a 2^16 bin histogram vs a 2^8 one... and most methods are
iterative. That is why the binning is quite convenient for speeding it up, but
as you found out it has its side effects.
> and doesn't help with the observation that
> the red overlay does not match the reported value from the IJ builtin Huang
> method -- because there is no preview overlay!
16bit overlays are not supported in IJ. I do not think there is a way of
currently generating such a LUT table and display it.
The set threshold in that plugin currently works on 8 bit images only. When I
get some time I will look into this.
> But, it doesn't work suitable for my intended use , which contains the
> following stanza, allowing the user to 'improve' upon the autothreshold
> before applying binarization, because it doesn't even provide a preview
> overlay at all.
Yes, I see, that is not currently possible. 32bit images are not supported
either.
> There's a few other problems with it also...
I would be happy to know which ones, it would be useful if it can be improved.
> I don't fundamentally have a problem with the result being altered from the
> precise value by 8bit reduction ... if it is consistent, but the problem
> now is the overlay doesn't match the actual result.
Going back to the built-in threshold applet, I did not quite understand why
does the 'stack histogram' option is not a suitable solution. It avoids the
problem you found last too (or maybe I missed something?).
Regards
Gabriel
--
ImageJ mailing list:
http://imagej.nih.gov/ij/list.html
Locked
