Jendker's profile - activity

Thank you!

I am working on segmenting the image based on the colour.

Right now I am considering how the cv::inRange function performs if my upper range of specific channel will be higher than max. value if 180, while the actual value on image will be close to 0?

Please let me present an example in HSV colour space: I have the filter with lowerb = (170, 50, 50), upperb = (190, 255, 255). Here I want to detect pink colour, which comes further into orange, so that the points of H are slightly above 0.

In the given case will the point (5, 180, 180) get accepted, so that cv::inRange will append the points above 0? Or should I apply two inRange filters:

lowerb = (170, 50, 50), upperb (179, 255, 255)
lowerb = (0, 50, 50), upperb (10, 255, 255)

and sum the results to achieve what I need?

I was trying to find the answer to my question in the OpenCV source code, but it was rather difficult to understand...

cv::inRange higher bound out of range of 0-180 in HSV I am working on segmenting the image based on the colour. Right n

What do you mean by not working? Crashes, doesn't compile, does not output this what you expect? What does it output, ma

And InputArrayOfArrays in case of vector and access with src.getMatVector(vector<mat> output). Just in case someon

And InputArrayOfArrays in case of vector. Just in case someone will be looking at this question in the future.

Ok, I will stick to InputArray then, thank you!

Constancy of const cv::Mat One of the possibilities of changing the cv::Mat would be to take part of the data with ROI a

Change of const cv::Mat One of the possibilities of changing the cv::Mat would be to take part of the data with ROI and

Change of const cv::Mat One of the possibilities of changing the cv::Mat would be to take part of the data with ROI and

Change of const cv::Mat One of the possibilities of changing the cv::Mat would be to take part of the data with ROI and

Got it, thank you. It wouldn't be difficult to change to my generator with different seed in those functions, but I don'

But I guess it will not help me in the end, the result is going to be random and algorithm non deterministic. I will hav

Thank you berak, it really seems to be some issue with randomization here, thank you! I will start with kmeans as you re

I don't know... Was it? I am still fighting with the same issue as before, grabCut works nice here for segmentation, wan

Difference between output of grabCut between runs Hello everyone, When running grabCut on an the same input in the loop

How far is grabCut deterministic? Hello everyone, When running grabCut on an the same input in the loop every time I wi

How far is grabCut deterministic? Hello everyone, When running grabCut on an the same input in the loop every time I wi

How far is grabCut deterministic? Hello everyone, When running grabCut on an the same input in the loop every time I wi

How far is grabCut deterministic? Hello everyone, When running grabCut on an the same input in the loop every time I wi

After removing some alterations to the mask (setting foreground/background), making it simpler I managed to get it right

After removing some alterations to the mask (setting foreground/background), making it simpler I managed to get it right

No, no, these are png, I store them in the vector and clone before any processing as presented in the edited post right

No, no, these are png, I store them in the vector and clone before any processing as presented in the edited post right

No, no, these are png, I store them in the vector and clone before any processing as presented in the edited post.

Hah ^^ I made the unit test of my grabCut function and by itself it works ok, but if I add haarCascade before it then I

Memory leaks cv::kmeans in cv:grabCut Hello everyone, I am using cv::grabcut to remove the background from the face pho

Hah ^^ I made the unit test of my grabCut function and by itself it works ok, but if I add haarCascade before it then I

Memory leaks cv::kmeans in cv:grabCut Hello everyone, I am using cv::grabcut to remove the background from the face pho

Memory leaks cv::kmeans in cv:grabCut Hello everyone, I am using cv::grabcut to remove the background from the face pho

Post edited

Memory leaks cv::kmeans in cv:grabCut Hello everyone, I am using cv::grabcut to remove the background from the face pho

Thank you for your input! Unfortunately there is something wrong there, because if I run grabCut on the same data two ti

Thanks! I will have a look on these. Here is screenshot from CLion, if there is any better way for a report please let m

I was trying OpenCV master right now, but there are so many changes in the flags, that it is difficult to compile my pro

What can I do to make it easier? I will try with the screenshot of CLion maybe, where I run valgrind...

Memory leaks cv::kmeans in cv:grabCut Hello everyone, I am using cv::grabcut to remove the background from the face pho

Memory leaks cv::kmeans in cv:grabCut Hello everyone, I am using cv::grabcut to remove the background from the face pho

Did you compile OpenCV with emcc? https://docs.opencv.org/3.4.0/d4/da1/tutorial_js_setup.html Besides loading with cvLoa

Did you compile OpenCV with emcc? https://docs.opencv.org/3.4.0/d4/da1/tutorial_js_setup.html Besides loading with cvLoa

Did you compile OpenCV with emcc? https://docs.opencv.org/3.4.0/d4/da1/tutorial_js_setup.html Besides cvLoadImage will p

Potential memory leaks on cv::cvtColor with Emscripten Hello everyone, I am having a curious case with OpenCV 3.4.2. Wh

I am doing it pretty normally with CMake build system. Just rember to compile OpenCV also with emcc and you will be fine

I am not sure what is the actual source of such behaviour. Should I maybe report it on OpenCV github issues or rather Em