Databases
StackOverflow2013
Postsdbo
PODifferent results with Haar cascade when in release/debug mode
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODifferent results with Haar cascade when in release/debug mode
    primarykey
    data
    text
    <p>I am using a Haar cascade classifier trained from the <a href="http://cbcl.mit.edu/software-datasets/CarData.html" rel="nofollow noreferrer">MIT cars dataset</a> to detect vehicles in OpenCV (trained using the utilities provided with OpenCV). This works reasonably well when compiled in Debug mode, but when compiled in Release mode the cascade doesn't make any detections at all. Running the following code on the test image below gives a detection in debug mode but nothing in release mode (this behaviour continues through all images in my data sequence).</p> <p>Can you suggest why this occurs and, more importantly, what I can do to obtain detections when running in Release mode?</p> <p><strong><a href="http://db.tt/cnpuh8r3" rel="nofollow noreferrer">Cascade File</a></strong></p> <p><strong>Code</strong> </p> <pre><code>cv::Mat testImage = cv::imread("testImage.png",0); cv::equalizeHist(testImage, testImage); cv::CascadeClassifier vehicleCascade; vehicleCascade.load("cars3.xml"); // Detect vehicles std::vector&lt;cv::Rect&gt; cars; vehicleCascade.detectMultiScale( testImage, // Input image cars, // Output bounding boxes 1.1, // scale factor - how much image size is reduced at each scale 5, // min neighbours - how many neighbours required to maintain rect 0|CV_HAAR_SCALE_IMAGE, // Not used cv::Size(30,30), // Min poss object size cv::Size() // Max poss object size ); std::cout &lt;&lt; "Found " &lt;&lt; cars.size() &lt;&lt; " objects.\n"; for (int i=0; i&lt;cars.size(); ++i) cv::rectangle(testImage, cars.at(i), CV_RGB(255,0,0), 3); cv::namedWindow("Haar cascade"); cv::imshow("Haar cascade", testImage); cv::waitKey(0); cv::imwrite("output.png", testImage); </code></pre> <p><strong>TestImage</strong></p> <p><img src="https://i.stack.imgur.com/oK7ZO.jpg" alt="testImage"></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChris
    1. USChris
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODifferent results with Haar cascade when in release/debug mode
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODifferent results with Haar cascade when in release/debug mode
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODifferent results with Haar cascade when in release/debug mode
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe image and cascade files load fine, in my actual code I use full directory paths. As far as I can tell, there are no errors in either mode, the only difference being the number of objects detectMultiScale returns.
      singulars
      1. PODifferent results with Haar cascade when in release/debug mode
      1. USChris
    2. COOk :/ I deleted my first comment since the part about the png was not relevant.
      singulars
      1. PODifferent results with Haar cascade when in release/debug mode
      1. USÉtienne
    3. COThis is often a sign of having UB and relying on specific behaviour (either in your code or in the library) or relying on specifically generated code that is different (e.g. floating point accuracy due to stuff staying in registers in release mode). The best thing you can do here is to compare all involved computations step by step in both modes and figure out where they start to deviate
      singulars
      1. PODifferent results with Haar cascade when in release/debug mode
      1. USPlasmaHH
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload