10-26-2018 12:04 AM
While working with "Quantify" vision operation I discovered unpredictable "Mean Value" result.
Mean value is not corresponding with real number of white\black pixels on an image.
See picture attached - I beleive "mean value" should be more than 0.5, but it is 0.252...
Does anyone have an explanation of that?
10-26-2018 06:49 AM
Why do you think the value should be 0.5? In the ROI, there appears to be a lot more red pixels than there are black ones...
Mike...
10-26-2018 08:43 AM
There's must be at least 0.5 or more (much more, you're right!), but not 0.25.
This weird thing happens in some ROIs - mean value may be right, may be not. This depends on what? I may attach some more strange pics of Quantify results, if needed.
11-03-2018 06:56 AM
Any ideas? NI developers read this forum?
11-05-2018 10:21 AM
Hi Agris,
I agree that this region seems like it should have an average higher than 0.25. Could you try a Histogram function on the same ROI to count the pixel values and see if it gives you a different result?
11-05-2018 11:29 AM - edited 11-05-2018 11:31 AM
Hi Ray,
Histogram reports same bad things - on attached image we see red pixels, but Vision Assistand doesn't - it reports MeanValue=0. Exactly the same results shows Quantify in this area.
I spent some time drawing ROIs, and, you know, result depends not on the image or something else... It depends on ROI tool! If you draw uneven shape with "pologonal" roi tool (see blue arrow on my screenshot), the result is shitty. If you draw rectangle on the same area - the result seems OK.
The only way to avoid strange behaviour is to use "rectangle", "circle" and "freehand" ROI tools here.
Any other ROI tools are useless, or to be honest, even pest.
Any ROI tool that can have gape or unclosed shape, shows bad results.
P.S. Thanks, Ray, for forcing me to draw some more ROIs, that's why I found the workaround 🙂