Ask Your Question

Jendker's profile - activity

2019-04-02 10:18:28 -0500 commented answer cv::inRange higher bound out of range of 0-180 in HSV

Thank you!

2019-04-02 10:18:20 -0500 marked best answer cv::inRange higher bound out of range of 0-180 in HSV

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...

2019-04-02 10:18:20 -0500 received badge  Scholar (source)
2019-04-02 08:48:54 -0500 asked a question cv::inRange higher bound out of range of 0-180 in HSV

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

2018-10-23 11:08:39 -0500 received badge  Critic (source)
2018-10-23 11:07:22 -0500 commented question detecting laser dots and get the coordinates

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

2018-10-09 04:57:06 -0500 commented question Constancy of const cv::Mat

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

2018-10-09 04:54:43 -0500 commented question Constancy of const cv::Mat

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

2018-10-09 03:21:01 -0500 commented question Constancy of const cv::Mat

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

2018-10-09 03:12:23 -0500 edited question Constancy of const cv::Mat

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

2018-10-01 11:25:34 -0500 received badge  Supporter (source)
2018-10-01 08:44:29 -0500 received badge  Student (source)
2018-10-01 08:18:51 -0500 edited question Constancy of const cv::Mat

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

2018-10-01 07:35:41 -0500 edited question Constancy of const cv::Mat

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

2018-10-01 07:34:50 -0500 asked a question Constancy of const cv::Mat

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

2018-09-28 09:08:21 -0500 commented question Difference between output of grabCut between runs

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

2018-09-28 08:29:50 -0500 commented question Difference between output of grabCut between runs

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

2018-09-28 08:13:18 -0500 commented question Difference between output of grabCut between runs

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

2018-09-28 08:11:44 -0500 commented question Difference between output of grabCut between runs

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

2018-09-28 08:04:55 -0500 edited question Difference between output of grabCut between runs

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

2018-09-28 07:07:05 -0500 edited question Difference between output of grabCut between runs

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

2018-09-28 06:55:03 -0500 edited question Difference between output of grabCut between runs

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

2018-09-28 06:37:34 -0500 edited question Difference between output of grabCut between runs

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

2018-09-28 05:59:40 -0500 asked a question Difference between output of grabCut between runs

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

2018-09-27 06:47:10 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-27 06:38:17 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-27 05:58:24 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-27 05:58:18 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-27 04:59:35 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-27 04:33:16 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-27 04:32:41 -0500 edited question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-27 04:26:37 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-27 04:01:34 -0500 edited question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-27 03:56:53 -0500 edited question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-27 03:53:43 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

Post edited

2018-09-27 03:53:35 -0500 edited question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-27 03:44:53 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-26 12:08:17 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-26 11:44:03 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-26 11:41:24 -0500 commented question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-26 10:45:04 -0500 edited question Memory leaks cv::kmeans in cv:grabCut

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

2018-09-26 10:43:52 -0500 asked a question Memory leaks cv::kmeans in cv:grabCut

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

2018-08-13 03:54:39 -0500 commented answer How do I compile a C program that contains a OPENCV header file?h

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

2018-08-13 03:53:51 -0500 commented answer How do I compile a C program that contains a OPENCV header file?h

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

2018-08-13 03:53:31 -0500 commented answer How do I compile a C program that contains a OPENCV header file?h

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

2018-08-10 03:50:34 -0500 received badge  Enthusiast
2018-08-08 03:47:00 -0500 edited question Potential memory leaks on cv::cvtColor with Emscripten

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

2018-08-08 03:45:42 -0500 answered a question How do I compile a C program that contains a OPENCV header file?h

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

2018-08-08 03:43:18 -0500 commented question Potential memory leaks on cv::cvtColor with Emscripten

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