2014-11-10 13:17:01 -0600 | asked a question | For traincascade, does -mode affect learning with LBP? Hello, Does the -mode parameter affect training with local binary pattern features? From my understanding it won't, since -mode uses either basic upright haar features or more advanced ones proposed by Lienhart and Maydt (from my understanding). I think LBP is a different set of features altogether? I have also found no evidence of it in the sourcecode. I am just asking this question to be sure about my assumption, since I could have easily overlooked something :) |
2014-11-03 07:48:48 -0600 | received badge | ● Student (source) |
2014-11-02 15:02:40 -0600 | asked a question | Can I pause traincascade? How? Hello all, I am currently using the opencv_traincascade application to train a cascade classifier. I have read that it is possible to pause the program (and even use the intermediate result). How should I go about doing this? Can I just kill the program (ctrl+c)? And how do I continue where I left off later? I just want to make sure I don't lose all of my data- it has been training for well over a day so far. Thanks in advance. |
2014-10-28 15:38:34 -0600 | commented answer | Question about FAST Detector I found both pages on my own too- I'm not sure how I missed line 360. Will keep in mind that the first ones are usually defaults, Thank you for all the support and have a nice day! |
2014-10-28 15:11:02 -0600 | received badge | ● Editor (source) |
2014-10-28 15:09:28 -0600 | commented question | Question about FAST Detector Thank you. |
2014-10-28 15:09:17 -0600 | commented answer | Question about FAST Detector Thank you. I'm not sure how I did not stumble upon it reading documentation though. Could you give me a reference to where I could find that the default specifies N=9? |
2014-10-28 15:06:11 -0600 | received badge | ● Supporter (source) |
2014-10-28 15:06:06 -0600 | received badge | ● Scholar (source) |
2014-10-28 14:37:53 -0600 | asked a question | Question about FAST Detector EDIT: This question has been answered. I have tried to close this, but my lack of reputation does not allow it. I welcome anyone with the permission to close this to do so. Hi, I wanted to examine which points in the image were picked up by using the default FAST Detector. I currently use EmguCV to do so, though I think my settings are the same as in this guide (I am calling the default constructor, tried different threshold values and non-max suppression on). I went through the wikipedia article and the guide I pointed to earlier, and tested it on one part of my image. This was the result . From my understanding, FAST determines whether or not there is a corner based on the following circle of grayscale values (taken from the image, but for clarity): It is a corner when at least N contiguous pixels are either threshold T brighter or darker than the center point. In this case I think N=12 (as default), and (at first) picked T = 10. This means that this segment of the picture should fail to mark as a corner, since the middle-top and left-middle pixels both have a value of 219, but the middle-bottom and right-middle pixel have 41. Varying the threshold T however, I did find that this spot does not get detected when T >= 85. This is probably because the top-right and bottom-left pixels have an intensity of 161 (76+85). Could anyone help me explain this behavior? Why does it find the spot at T < 85? Is the default N < 12? Or am I missing some step here? Thanks in advance. |