sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Allowing double type support if possible
Labels: auto-transferred,priority: normal,feature,category: core

Transferred from http://code.opencv.org/issues/2671

```
|| Ming-Ming Cheng on 2012-12-28 22:41
|| Priority: Normal
|| Affected: None
|| Category: core
|| Tracker: Feature
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## Allowing double type support if possible

```
For 64 bit machine, which is the major type currently, operations on double is faster/equal to operations on float. Since the memory difference between double and float is not important for many people, I tried to use double in my code anywhere where float is used before so that don't care too much about type conversion. 

A problem is that, some opencv functions only support float (CV_32F). I feel strange why don't them support for double (CV_64F). One example of this function is cvtColor.
```
## History
##### Alexander Smorkalov on 2012-12-29 08:16

```
It is very rare feature for computer vision algorithm. But if you have any suggestions, you can contribute to OpenCV via Github pull request. See this page for more details: https://help.github.com/articles/using-pull-requests 
-   Category set to core
```
##### Ming-Ming Cheng on 2013-04-11 11:02

```
Thank you very much for the reply. I agree that most computer vision algorithms needs only float. I just feel that I can consistently use double since I typically don't care about the memory cost introduced by this. Consistently using double, like what was done in Matlab, avoids possible data type conversions when double is required. Modern 64bit computers process double at similar or even more efficiency than float.

Alexander Smorkalov wrote:
> It is very rare feature for computer vision algorithm. But if you have any suggestions, you can contribute to OpenCV via Github pull request. See this page for more details: https://help.github.com/articles/using-pull-requests
```
Repository: opencv
Issue: QueryFrame keeps GIL
Labels: bug,auto-transferred,priority: normal,category: python bindings

Transferred from http://code.opencv.org/issues/2672

```
|| Bouke van der Bijl on 2012-12-29 17:07
|| Priority: Normal
|| Affected: None
|| Category: python bindings
|| Tracker: Bug
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## QueryFrame keeps GIL

```
Hi,
normally when a C extension makes a blocking call it should tell the Python interpeter that it can release the GIL http://docs.python.org/2/c-api/init.html#thread-state-and-the-global-interpreter-lock.
This happens correctly for pycvWaitKey, pycvLoadImage and pycvLoadImageM. QueryFrame completely locks up the interpreter when using threads though, and it should be implemented just like pycvWaitKey, pycvLoadImage and pycvLoadImageM are instead of only being wrapped. I don't have any experience with writing Python C extensions so I am afraid I can't fix this myself.
```
## History
Repository: opencv
Issue: [iOS] Undesired Autorotate behavior
Labels: bug,auto-transferred,priority: normal,platform: ios/osx

Transferred from http://code.opencv.org/issues/2673

```
|| Diego Araos on 2012-12-30 20:42
|| Priority: Normal
|| Affected: None
|| Category: ios
|| Tracker: Bug
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## [iOS] Undesired Autorotate behavior

```
In iOS, I want my device to have a fixed orientation, but whenever my device orientation changes, CvVideoCamera insist to keep rotating it's orientation and after reviewing the source code, it seems like there is no way to avoid this from outside the framework code.

It would be great if you could add an option so I can use the camera with a fixed orientation and the CvVideoCamera follows this rule too. Maybe adding a boolean ? let's say:

    self.videoCamera = [[CvVideoCamera alloc] initWithParentView:self.cameraView];
    ...
    self.cameraView.autorotateCamera = NO;

I offer to code a fix if you let me know how to push it afterwards.

Cheers.
```
## History
##### Andrey Kamaev on 2013-01-08 16:22

```
-   Assignee set to Vadim Pisarevsky
-   Category set to ios
```
##### Sebastien Thiebaud on 2013-02-03 03:20

```
Hi,

Do you have some news about this bug. I'll release an app and this bug is still persistent.

Thank you!
```
##### Ricardo Ruiz on 2013-04-02 21:41

```
I see a couple of fixes, but don't work for me.
http://stackoverflow.com/questions/14876895/how-do-i-make-cvvideocamera-not-auto-rotate
http://answers.opencv.org/question/8329/opencv-setting-ios-orientation/
Any progress on this issue?
```
Repository: opencv
Issue: Link the FaceRecognizer tutorials to the Contribs tutorial page
Labels: auto-transferred,feature,priority: low,category: documentation

Transferred from http://code.opencv.org/issues/2687

```
|| Shervin Emami on 2013-01-09 01:36
|| Priority: Low
|| Affected: None
|| Category: documentation
|| Tracker: Feature
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## Link the FaceRecognizer tutorials to the Contribs tutorial page

```
The FaceRecognizer tutorials are in the API Reference section (http://docs.opencv.org/modules/contrib/doc/facerec/index.html) instead of the Contrib tutorials section (http://docs.opencv.org/doc/tutorials/contrib/table_of_content_contrib/table_of_content_contrib.html#table-of-content-contrib). Perhaps it should be moved, or atleast a link put on the Contrib tutorials page showing where the tutorials actually are?
```
## History
Repository: opencv
Issue: window issues on mac os x mountain lion (10.8)
Labels: bug,auto-transferred,priority: normal,category: highgui-gui,affected: 2.4

Transferred from http://code.opencv.org/issues/2694

```
|| Andrei Zaharescu on 2013-01-12 02:40
|| Priority: Normal
|| Affected: 2.4.3
|| Category: highgui-gui
|| Tracker: Bug
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## window issues on mac os x mountain lion (10.8)

```
When running any opencv sample application on Mac OS X (10.8) that uses basic highgui imshow functionality, see the following problems: 
* the window does not have the focus by default
* the window position is not remembered between subsequent runs, as it is the case on Windows
* the window flags are not respected. When setting the CV_WINDOW_NORMAL in namedWindow and resizing the window, the content is not auto-resized anymore
* when displaying an image that is too narrow (lets say 400x100), the window is in effect wider than the image, which in practice causes issues when capturing mouse events over the window, since one expects the image to span the whole window.
```
## History
##### Daniil Osokin on 2013-01-14 04:38

```
-   Description changed from When running any opencv sample application
    on Mac OS X (10.8) that uses basic... to When running any opencv
    sample application on Mac OS X (10.8) that uses basic... More
```
##### Daniil Osokin on 2013-01-14 04:40

```
Hi! Please, specify OpenCV version and provide test code sample to reproduce the bug, otherwise the ticket will be closed.
```
##### Daniil Osokin on 2013-01-14 04:40

```
-   Assignee changed from Vadim Pisarevsky to Andrei Zaharescu
```
##### Vadim Pisarevsky on 2013-01-22 22:21

```
-   Target version deleted (2.4.4)
```
##### Vadim Pisarevsky on 2013-01-24 17:53

```
-   Assignee deleted (Andrei Zaharescu)
```
##### Vadim Pisarevsky on 2013-01-31 19:05

```
-   Target version set to 3.0
-   Affected version set to 2.4.3
-   Assignee set to Vadim Pisarevsky
```
Repository: opencv
Issue: SURF keypoints' response is inaccurate in Windows x32 Release build
Labels: bug,auto-transferred,priority: normal,affected: 2.4,category: nonfree

Transferred from http://code.opencv.org/issues/2696

```
|| Andrey Pavlenko on 2013-01-14 09:56
|| Priority: Normal
|| Affected: 2.4.3
|| Category: nonfree
|| Tracker: Bug
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## SURF keypoints' response is inaccurate in Windows x32 Release build

```
I'm adding the following accuracy test to the OpenCV:
<pre>TEST(Features2d_RotationInvariance2_Detector_SURF, regression)
{
    Mat cross(100, 100, CV_8UC1, Scalar(255));
    line(cross, Point(30, 50), Point(69, 50), Scalar(100), 3);
    line(cross, Point(50, 30), Point(50, 69), Scalar(100), 3);

    SURF surf(8000., 3, 4, true, false);

    vector<KeyPoint> keypoints;

    surf(cross, noArray(), keypoints);

    ASSERT_EQ(keypoints.size(), 5);
    ASSERT_LT( fabs(keypoints[1].response - keypoints[2].response), 1e-6);
    ASSERT_LT( fabs(keypoints[1].response - keypoints[3].response), 1e-6);
    ASSERT_LT( fabs(keypoints[1].response - keypoints[4].response), 1e-6);
}</pre>

It fails in Windows x32 Release build with @/O2@ compiler option, but doesn't with @/O1@ one.
It also passes on Windows x64 and Linux systems.
```
## History
##### Vadim Pisarevsky on 2013-01-22 16:17

```
-   Target version deleted ()
-   Affected version set to 2.4.3
```
##### Vadim Pisarevsky on 2013-01-24 17:53

```
-   Assignee deleted (Maria Dimashova)
```
##### Vadim Pisarevsky on 2013-01-27 15:00

```
-   Category changed from features2d to nonfree
```
##### Vadim Pisarevsky on 2013-01-27 15:02

```
-   Assignee set to Vadim Pisarevsky
```
##### Kirill Kornyakov on 2013-02-14 08:11

```
-   Target version set to 2.4.4
```
##### Andrey Kamaev on 2013-02-28 14:37

```
-   Target version changed from 2.4.4 to 2.4.5
```
##### Andrey Kamaev on 2013-04-03 20:20

```
-   Target version changed from 2.4.5 to Next Hackathon
```
Repository: opencv
Issue: Algorithm set/info not threadsafe
Labels: wontfix,auto-transferred,category: core,affected: 2.4

Transferred from http://code.opencv.org/issues/2697

```
|| daniel oberhoff on 2013-01-14 13:11
|| Priority: Low
|| Affected: 2.4.6 (latest release)
|| Category: core
|| Tracker: Bug
|| Difficulty: 
|| PR: 
|| Platform: Any / Any
```
## Algorithm set/info not threadsafe

```
Hi,

I make heavy use of threads and lazy initialization in my code. But it seems anything related to the new algorithm info infrastructure is not thread safe. And I mean not when applied on a single instance, but across a whole class. I.e. when I retreive the info simultanously for separate instances of the same class, I get a segfault. same for setting, and again, these are separate instances.

If you wish I can generate stack traces for you.

btw it would be nice, if algorithm parameters where somehow documented somewhere.

Best
```
## History
##### Marina Kolpakova on 2013-01-14 13:31

```
-   Assignee set to Vadim Pisarevsky
-   Category set to core
```
##### Vadim Pisarevsky on 2013-01-21 14:05

```
without a sample code it's not possible to reproduce the problem. setting Algorithm properties should be thread-safe. info() method is not completely thread-safe, the first invocation may do some initialization, but the problem should not appear in the existing OpenCV classes.

so, please, provide the sample code so that we can reproduce the problem
-   Affected version set to 2.4.3
-   Priority changed from Normal to Low
-   Assignee changed from Vadim Pisarevsky to daniel oberhoff
```
##### Vladislav Vinogradov on 2013-09-30 07:56

```
Hello Vadim,

There is a new report with the same issue : http://code.opencv.org/issues/3292

I attached a sample code that reproduce the issue (tested on Linux with TBB).

@Algorithm::info@ is implemented in the following way:

<pre>
::cv::AlgorithmInfo* classname::info() const
{
    static volatile bool initialized = false;
    if( !initialized )
    {
        initialized = true;
        memberinit;
    }
    return &classname##_info();
}
</pre>

There is no synchronization between threads.
So one thread can set @initialized@ variable to @true@ and go to sleep before @memberinit@, while the second thread will read @initialized@ value as @true@ and will use uninitialized struct.
-   Affected version changed from 2.4.3 to 2.4.6 (latest release)
-   Operating System set to Any
-   HW Platform set to Any
-   Assignee changed from daniel oberhoff to Vadim Pisarevsky
-   File main.cpp added
```
Repository: opencv
Issue: cv::GridAdaptedFeatureDetector write of parameters not working
Labels: bug,auto-transferred,priority: normal,category: features2d

Transferred from http://code.opencv.org/issues/2698

```
|| Erik R on 2013-01-14 15:36
|| Priority: Normal
|| Affected: None
|| Category: features2d
|| Tracker: Bug
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## cv::GridAdaptedFeatureDetector write of parameters not working

```
As the title says, its not possible for a GridAdaptedFeatureDetector to write its parameters to a file.
When using a standard detector (e.g. GFTT) "write(fs)" calls the detector's constructor, but for the gridadapted version it goes into GFTTDetector::detectImpl instead, casting an error when trying to create the grayImage.
Also, pyramid version is not working either. 

Example:
<pre>
#include <opencv2\features2d\features2d.hpp>
int main ( int argc, char **argv )
{
    cv::initModule_features2d(); // Not needed?

    cv::Ptr<cv::FeatureDetector> feature_detector = cv::FeatureDetector::create("GridGFTT"); // goes into GFTTDetector::detectImpl instead of constructor in write method
    //cv::Ptr<cv::FeatureDetector> feature_detector = cv::FeatureDetector::create("PyramidGFTT"); // not working either
    //cv::Ptr<cv::FeatureDetector> feature_detector = cv::FeatureDetector::create("GFTT"); // goes into constructor in write method (works)

    cv::FileStorage fs("grid_params.xml", cv::FileStorage::WRITE);
    {
        cv::WriteStructContext ws(fs, "params", CV_NODE_MAP);
        feature_detector->write(fs);
    }
    fs.release();
    return 0;
}
</pre>
```
## History
Repository: opencv
Issue: cap_qtkit.mm: CvCaptureFile::CvCaptureFile does not open URL paths
Labels: auto-transferred,feature,priority: low,category: videoio

Transferred from http://code.opencv.org/issues/2705

```
|| Xavier Ho on 2013-01-16 04:00
|| Priority: Low
|| Affected: None
|| Category: highgui-video
|| Tracker: Feature
|| Difficulty: 
|| PR: 
|| Platform: None / None
```
## cap_qtkit.mm: CvCaptureFile::CvCaptureFile does not open URL paths

```
The minimal case: Load a video stream from an Apexis IP Camera and display it on a Mac.

Example (Python):
<pre>
import cv2
capture = cv2.VideoCapture('http://192.168.1.2/...')
if not capture.isOpened():
    print 'Unable to open video.'

success, image = capture.read()
while success:
    cv2.imshow('Video', image)
    cv.waitKey(2)
    success, image = capture.read()
</pre>

We have also tried the RTSP streaming variant from the same camera, but we get the same error.

The problem: Mac's QTKit implementation assumes the filename is always a file:
It uses [QTMovie movieWithFile].

The same code works on Ubuntu 12.10 with gstreamer.  It would be sensible for the Mac version to provide the same support for URL paths.

We think an alternative codepath would fix this issue. [QTMovie movieWithURL], for example.

I am happy to do a pull request if this ticket is accepted as important bug fix.  Please let us know your thoughts.
```
## History
##### Xavier Ho on 2013-01-16 04:03

```
Possible related: http://code.opencv.org/issues/2474
```
##### Xavier Ho on 2013-01-16 05:35

```
I found a workaround for Macs by compiling WITH_GSTREAMER.  You have to unblacklist it first, and then it works fine.  See http://stackoverflow.com/questions/14350813/compile-opencv-2-4-3-rc-with-gstreamer-on-mac-os-x-10-8/14351969#14351969.
```
##### Vadim Pisarevsky on 2015-05-22 07:21

```
I would consider it as feature request, especially since you found a workaround.
-   Priority changed from Normal to Low
-   Tracker changed from Bug to Feature
```
Repository: opencv
Issue: Segmentation fault inside cvSetTrackbarPos
Labels: bug,auto-transferred,priority: normal,category: highgui-gui

Transferred from http://code.opencv.org/issues/2706

```
|| Nikita Manovich on 2013-01-16 08:27
|| Priority: Normal
|| Affected: None
|| Category: highgui-gui
|| Tracker: Bug
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## Segmentation fault inside cvSetTrackbarPos

```
I have attached an example from a book. When I tried to close the window using "X" I had segmentation fault inside cvSetTrackbarPos function from highgui module because in this case trackbar variable was NULL.

I didn't investigate the structure of the module in depth but with the attached patch I don't see the crash anymore.
```
## History
##### Marina Kolpakova on 2013-01-16 23:17

```
-   Category set to highgui-gui
```
Repository: opencv
Issue: adding optional output of cost-array to stereointerfaces StereoBM and StereoSGBM
Labels: auto-transferred,priority: normal,feature,category: calib3d

Transferred from http://code.opencv.org/issues/2708

```
|| Daniel Kapusi on 2013-01-16 11:38
|| Priority: Normal
|| Affected: None
|| Category: calibration, 3d
|| Tracker: Feature
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## adding optional output of cost-array to stereointerfaces StereoBM and StereoSGBM

```
It would be nice, to have optional a quality measure for the disparity values also in the simple interfaces StereoBM and StereoSGBM.

StereoBM::operator()( InputArray _left, InputArray _right, OutputArray _disparity, int disptype )
StereoSGBM::operator ()( InputArray _left, InputArray _right, OutputArray _disp )

maybe in this way ->

StereoBM::operator()( InputArray _left, InputArray _right, OutputArray _disparity, int disptype, OutputArray _costs = noArray())
StereoSGBM::operator ()( InputArray _left, InputArray _right, OutputArray _disp, OutputArray _costs = noArray())
```
## History
Repository: opencv
Issue: A 3D Color Histogram Equalization Methods
Labels: auto-transferred,priority: normal,feature,category: imgproc,category: video

Transferred from http://code.opencv.org/issues/2718

```
|| Rel Guzman Apaza on 2013-01-19 00:38
|| Priority: Normal
|| Affected: None
|| Category: imgproc, video
|| Tracker: Feature
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## A 3D Color Histogram Equalization Methods

```
<pre>
It should be some functions on the library for 3D Histogram Eq.
Or is this already exists in the library?
</pre>
```
## History
Repository: opencv
Issue: Clean up test data
Labels: auto-transferred,feature,priority: low,category: infrastructure,Hackathon

Transferred from http://code.opencv.org/issues/2722

```
|| Kirill Kornyakov on 2013-01-21 13:43
|| Priority: Normal
|| Affected: None
|| Category: infrastructure
|| Tracker: Feature
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## Clean up test data

```
On a weekly OpenCV meeting we decided, that we need to clean & minimize test data. Here are tasks selected for the hackathon:
# Remove unused images and duplicated files (cascades)
# Look at large files and decide if we need the at all
# Make tests to use the same input images, i.e. stitching images can be used by feature2d tests
# Remove auto-generated images, but if only their size is large
```
## History
##### Vadim Pisarevsky on 2013-01-24 17:54

```
-   Assignee deleted (Vadim Pisarevsky)
```
##### Kirill Kornyakov on 2013-02-14 08:08

```
-   Target version set to 2.4.5
```
##### Andrey Kamaev on 2013-04-01 09:56

```
-   Target version changed from 2.4.5 to 3.0
```
Repository: opencv
Issue: Integrate gpb-ucm from https://github.com/vrabaud/gPb and add python binding
Labels: auto-transferred,feature,category: imgproc,category: video,priority: low

Transferred from http://code.opencv.org/issues/2728

```
|| David Miller on 2013-01-22 21:37
|| Priority: Normal
|| Affected: None
|| Category: imgproc, video
|| Tracker: Feature
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## Integrate gpb-ucm from https://github.com/vrabaud/gPb and add python binding

```
Integrate gpb-ucm code from https://github.com/vrabaud/gPb and add a python binding.
```
## History
##### Maria Dimashova on 2013-01-23 13:09

```
-   Category set to imgproc, video
```
Repository: opencv
Issue: Circles grid support should be added into the stereo_calib example
Labels: auto-transferred,priority: normal,feature,category: calib3d

Transferred from http://code.opencv.org/issues/2742

```
|| Ilya Lysenkov on 2013-01-29 07:48
|| Priority: Normal
|| Affected: None
|| Category: calibration, 3d
|| Tracker: Feature
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## Circles grid support should be added into the stereo_calib example

```
@stereo_calib@ example should support different patterns as @calibration@ sample does. In my experiments stereo calibration using circles grid works out of the box just by changing @findChessboardCorners@ with @findCirclesGrid@ and it gives better accuracy.
```
## History
##### Ilya Lysenkov on 2013-01-29 07:49

```
-   Assignee deleted (Vadim Pisarevsky)
```
Repository: opencv
Issue: All zeros in SIFT descriptor
Labels: bug,auto-transferred,priority: low,affected: 2.4,category: nonfree

Transferred from http://code.opencv.org/issues/2745

```
|| antonio sesto on 2013-01-30 12:20
|| Priority: Low
|| Affected: 2.4.3
|| Category: nonfree
|| Tracker: Bug
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## All zeros in SIFT descriptor

```
Hello,
 I am using the latest stable version of OpenCV, but I am having a strange problem while using SIFT.

See attached images. Many points from the query image A are mapped onto the same point of the train image B. If I use B as query and A as train, the same happens, even if the set of keypoints changes.

The problem is due to many SIFT descriptors containing all zeros. 

If the SIFT descriptor ends up in being composed by all zero, the keypoint should not be there in the first place.
```
## History
##### Vadim Pisarevsky on 2013-01-30 14:34

```
could you please supply the images and the sample code (desirably, some compact piece of code) in order to reproduce the problem. On the images I tried it don't get this problem.
-   Assignee set to Vadim Pisarevsky
-   Category set to nonfree
```
##### Vadim Pisarevsky on 2013-01-31 19:16

```
-   Assignee changed from Vadim Pisarevsky to antonio sesto
```
##### antonio sesto on 2013-02-01 11:59

```
Hello,
 you can see a description of what happens here:

http://stackoverflow.com/questions/14589595/opencv-feature-matching-with-code-from-the-tutorial

I got descriptors with all zero for every image in the folder IRELAND from the INRIA Holidays dataset. I did not try with other folders/images from the same dataset. You may find two images in attachment.

The code is taken from the tutorial:
<pre>
void full_on_line_match(const Mat& img1, const Mat& img2) {
        if(! img1.data || ! img2.data) return;

        Mat m1, m2;
        cvtColor(img1, m1, CV_RGB2GRAY);
        cvtColor(img2, m2, CV_RGB2GRAY);

        // MATCHER
        // FlannBasedMatcher matcher;
        BFMatcher matcher(NORM_L2);

        // 1 Detect keypoints
        vector<KeyPoint> keypoints1_;
        vector<KeyPoint> keypoints2_;
        detector->detect(m1, keypoints1_);
        detector->detect(m2, keypoints2_);

        // 2 Compute descriptors
        Mat dd1, dd2; // descriptors
        extractor->compute(m1, keypoints1_, dd1);
        extractor->compute(m2, keypoints2_, dd2);

        // 2.1 Cleaning descriptors: remove descr. with all zero
        vector<KeyPoint> keypoints1, keypoints2;
        Mat d1, d2;
        clean_descriptors(keypoints1_, keypoints1, dd1, d1);
        clean_descriptors(keypoints2_, keypoints2, dd2, d2);

        vector< vector<DMatch> > matches12;
        vector< vector<DMatch> > matches21;
        matcher.knnMatch( d1, d2, matches12, 2);
        matcher.knnMatch( d2, d1, matches21, 2);

        [...]
<pre>
-   File 17001.jpg added
-   File 17000.jpg added
```
##### Kirill Kornyakov on 2013-02-12 06:42

```
Vadim, should we look into it before the final 2.4.4?
```