sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Connected Components Labeling in CUDA is buggy
Labels: bug,auto-transferred,priority: low,affected: 2.4,category: gpu/cuda (contrib)

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

```
|| Andrey Pavlenko on 2013-05-24 15:53
|| Priority: Low
|| Affected: branch '2.4' (2.4-dev)
|| Category: gpu (cuda)
|| Tracker: Bug
|| Difficulty: 
|| PR: 
|| Platform: x64 / Windows
```
## Connected Components Labeling in CUDA is buggy

```
The attached code results in incorrect image.
Also there is no test for it, if I'm not mistaken...
```
## History
##### Vadim Pisarevsky on 2015-05-21 22:19

```
ok, connected component is not the most important function which has to be run on GPU; considering the amount of available support and new Marina's projects, let's lower the priority
-   Affected version changed from branch 'master' (2.4.9) to branch
    '2.4' (2.4-dev)
-   Operating System set to Windows
-   HW Platform set to x64
-   Priority changed from High to Low
```
Repository: opencv
Issue: Access to OpenNI DeviceInfos for Multi-Sensor-Applications
Labels: auto-transferred,priority: normal,feature,category: videoio(camera)

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

```
|| Hagen Borstell on 2013-06-04 13:36
|| Priority: Normal
|| Affected: None
|| Category: highgui-camera
|| Tracker: Feature
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## Access to OpenNI DeviceInfos for Multi-Sensor-Applications

```
Hello,

OpenNI provides the reading of device information (DeviceInfos: names, uri, pid, vendor, etc.). Thus, a sensor can be uniquely identified in a multi-sensor application. 

This is important to clearly assign specific information (calibration parameters) to a specific sensor in multisensor applications.

Is it possible to make this information accessible over the OpenCV interface (cap_openni.cpp) or open a specific sensor (pid=....)?

p.s. In OpenCV you are  limited to open "any" sensor --> VideoCapture capture( CV_CAP_OPENNI ); The order is arbitrary/random, right?

Thank you very much for your response.
```
## History
##### Daniil Osokin on 2013-06-04 13:47

```
Hi, Hagen!
Thank you for attention! Could you please contribute this functionality (http://code.opencv.org/projects/opencv/wiki/How_to_contribute)? OpenCV's developers will review it and add to OpenCV.
-   Target version set to 2.4.6
-   Assignee changed from Vadim Pisarevsky to Hagen Borstell
```
##### Kirill Kornyakov on 2013-06-14 09:50

```
-   Target version deleted (2.4.6)
```
Repository: opencv
Issue: VideoCapture does not support the Minoru 3D camera (and possibly other multi USB camera configurations)
Labels: wontfix,auto-transferred,category: videoio,affected: 2.4

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

```
|| Matias Nitsche on 2013-06-11 18:57
|| Priority: Normal
|| Affected: 2.4.5 (latest release)
|| Category: highgui-video
|| Tracker: Bug
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## VideoCapture does not support the Minoru 3D camera (and possibly other multi USB camera configurations)

```
Currently, it is not possible to instantiate two VideoCapture's using both USB devices corresponding to the Minoru 3D camera. According to what I've read, this is probably due to the fact that one camera takes up all available bandwidth. There's an existing implementation, libv4l2cam, which supports accessing the Minoru correctly.
I don't have the expertise to understand why this library works, but maybe someone with the knowledge may be able to change OpenCV VideoCapture code to support this kind of devices.
```
## History
Repository: opencv
Issue: The regression test Features2d_SURF_using_mask fails
Labels: bug,auto-transferred,priority: normal,affected: 2.4,category: features2d

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

```
|| Ivan Korolev on 2013-06-14 13:21
|| Priority: Normal
|| Affected: 2.4.0 - 2.4.4
|| Category: features2d
|| Tracker: Bug
|| Difficulty: None
|| PR: 
|| Platform: None / None
```
## The regression test Features2d_SURF_using_mask fails

```
The @featureDetector_->detect(image, keyPoints, mask)@ method returns key points that are outside the mask.
```
## History
Repository: opencv
Issue: FileStorage can't read VOC annotations
Labels: auto-transferred,priority: normal,feature,category: core

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

```
|| Ming-Ming Cheng on 2013-07-12 13:23
|| Priority: Normal
|| Affected: None
|| Category: core
|| Tracker: Feature
|| Difficulty: 
|| PR: 
|| Platform: None / None
```
## FileStorage can't read VOC annotations

```
VOC and ImageNet use the same xml annotation format. Although they are most famous computer vision dataset. The annotation format is not supported in OpenCV. Some reasons for crash includes:

1. The VOC annotation format don't start with '<?xml version="1.0"?> <opencv_storage>'. 
2. Some values, e.g. <owner><flickrid>, might contains characters not supported. 
3. Values like <filename>000005.jpg</filename> needs to be changed to <filename>"000005.jpg"</filename> in order to avoid crash in reading.

Above problems can be avoid by some simple pre-processing. The other bug, which is reported by OpenCV as "Duplicated key", can't be easily addressed. However, each VOC image has several <object> key.
```
## History
##### Nikita Manovich on 2013-07-12 14:30

```
Hi,

Thank you for the report. I don't think that it is a bug. You have suggested some new functionality. Could you please help us and submit a pull request? Unfortunately we have limited resources. We will be glad to see you as a contributer. Please read http://www.code.opencv.org/projects/opencv/wiki/How_to_contribute for more information.
-   Difficulty deleted (Medium)
-   Assignee set to Maria Dimashova
-   Status changed from New to Open
-   Category set to core
-   Tracker changed from Bug to Feature
```
##### Nikita Manovich on 2013-07-12 14:30

```
-   Assignee deleted (Maria Dimashova)
```
Repository: opencv
Issue: Support disabling LZW compression for writing TIFF images
Labels: auto-transferred,priority: normal,feature,category: imgcodecs

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

```
|| Nikolay Rogoshchenkov on 2013-07-16 12:28
|| Priority: Normal
|| Affected: None
|| Category: highgui-images
|| Tracker: Feature
|| Difficulty: 
|| PR: 
|| Platform: None / None
```
## Support disabling LZW compression for writing TIFF images

```
Will be very useful to have ability to disable/enable LZW compression for writing TIFF-files. Now TIFF-files writing with default LZW compression.
```
## History
##### Nikita Manovich on 2013-07-16 18:24

```
Hi,

Thank you for the feature request. If you can help us and implement the functionality it will be cool. You can find all necessary information on the following page: http://code.opencv.org/projects/opencv/wiki/How_to_contribute.
-   Status changed from New to Open
-   Category set to highgui-images
```
Repository: opencv
Issue: BORDER_WRAP not available in FilterEngine
Labels: auto-transferred,feature,category: imgproc,category: video,priority: low

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

```
|| Tama McGlinn on 2013-07-20 23:44
|| Priority: Low
|| Affected: None
|| Category: imgproc, video
|| Tracker: Feature
|| Difficulty: Easy
|| PR: 
|| Platform: None / None
```
## BORDER_WRAP not available in FilterEngine

```
modules/imgproc/src/filter.cpp:160 - CV_Assert( columnBorderType != BORDER_WRAP );

This line prevents me from making a linear filter with BORDER_WRAP type. I have no idea why this is, nor how to fix it.
```
## History
##### Steven Puttemans on 2013-07-21 12:25

```
This is due to no code in the filter algorithm being provided for solving problems with the cv_borderwrap type of borderstyle. To fix it what you can do is create a pull request with the assert gone, then see how it influences the problem and where it goes wrong. But I am guessing some algorithms beneath it will generate errors which need to be fixed then.
```
##### Ivan Korolev on 2013-07-22 10:35

```
Hello Tama McGlinn,
Thank you for submitting this ticket. Unfortunately, FilterEngine doesn't support BORDER_WRAP type of border. If you could add this feature on your side, a pull request in our GitHub repo (http://www.code.opencv.org/projects/opencv/wiki/How_to_contribute for more details) would be highly appreciated! If you decide to continue with introducing this feature then please explain what is purpose of this feature? 
-   Priority changed from Normal to Low
-   Status changed from New to Open
-   Tracker changed from Bug to Feature
```
##### Alexander Smorkalov on 2013-11-27 10:53

```
-   Target version changed from 2.4.7 to Next Hackathon
-   Assignee deleted (Vadim Pisarevsky)
```
##### isscandar isscandar on 2014-09-30 18:10

```
Ivan Korolev wrote:

> If you decide to continue with introducing this feature then please explain what is purpose of this feature?

Hello Ivan,
in my applications I often work with a region of interest with the shape of an annulus, for some particular tasks I rectify the annulus transforming it in a rectangular stripe; a circular path (ideally one-pixel wide) inside the annulus is so transformed into a row in the rectangular stripe, for these rows I think that the @BORDER_WRAP@ interpolation would be the best interpolation scheme. I faced the same need of Tama McGlinn when I tried to do @cv::cornerHarris@ with @borderType@ equal to @cv::BORDER_WRAP@ (OpenCV 2.4.4).

Thank you.
```
Repository: opencv
Issue: BFMatcher
Labels: bug,auto-transferred,priority: normal,affected: 2.4,category: features2d

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

```
|| Robert Aschenbrenner on 2013-07-24 17:49
|| Priority: Normal
|| Affected: 2.4.9 (latest release)
|| Category: features2d
|| Tracker: Bug
|| Difficulty: 
|| PR: https://github.com/Itseez/opencv/pull/3025
|| Platform: x64 / Linux
```
## BFMatcher

```
Using BFMatcher with "NORM_HAMMING" on binary descriptors (created by FREAK) gives unexpected results in certain conditions:

<pre>
std::vector<Mat> descriptors; //FREAK descriptors of e.g. 1000 images
... //compute actual descriptors
BFMatcher bfMatcher(NORM_HAMMING, false);
bfMatcher.add(descriptors);
int nn = 10; //Number of nearest neighbours
bfMatcher.knnMatch(query_descriptors, matches, nn);
</pre>

The above code returns invalid results, if *nn* happens to be smaller than any image's descriptor set.
For example one single image _test.jpg_ might have only *9* (<nn) according FREAK descriptors.
The BFMatcher will calculate all distances using @batchDistance@ (https://github.com/Itseez/opencv/blob/master/modules/features2d/src/matchers.cpp#L366).
Eventually it passes the current best results (@nidx@) to @cv::batchDistance@ in https://github.com/Itseez/opencv/blob/master/modules/core/src/stat.cpp#L1792.
The problem arises in the following section:
<pre>
 K = std::min(K, src2.rows);

    _dist.create(src1.rows, (K > 0 ? K : src2.rows), dtype);
    Mat dist = _dist.getMat(), nidx;
    if( _nidx.needed() )
    {
        _nidx.create(dist.size(), CV_32S);
        nidx = _nidx.getMat();
    }
</pre>
@K@ is reduced, when _test.jpg_ (src2) is inspected, since it only has *9* rows.
@_nidx.create(dist.size(), CV_32S);@ reduces the dimension of @nidx@ to 9 columns, invalidating older results.
Later images may increase the column size again to 10.
The assumption, that the number of descriptors of every image is always > nn, seems unenforced.
```
## History
##### Ivan Korolev on 2013-07-25 06:43

```
Hi Robert,
thanks for the bug report. Do you think you can fix the problem? If you could investigate this issue or send a fixing pull request (http://www.code.opencv.org/projects/opencv/wiki/How_to_contribute for more details) your help would be highly appreciated!
```
##### Ivan Korolev on 2013-07-25 06:43

```
-   Status changed from New to Open
```
##### Robert Aschenbrenner on 2013-08-03 13:18

```
Hi, I am afraid that I do not have sufficient time at the moment. In my code I'm circumventing the above mentioned case by extra checks.
I suspect the code in stat.cpp is not only used by BFMatcher.
Maybe the original author could have a look?
```
##### Philipp Hasper on 2014-08-04 12:28

```
Unfortunately it seems that I don't have the rights to assign a pull request to this issue. So I have to paste the URL manually: https://github.com/Itseez/opencv/pull/3025
```
##### Alexander Karsakov on 2014-08-14 11:47

```
-   Affected version changed from 2.4.0 - 2.4.5 to 2.4.9 (latest
    release)
-   Pull request set to https://github.com/Itseez/opencv/pull/3025
-   Assignee deleted (Maria Dimashova)
```
Repository: opencv
Issue: cv:HoGDescriptor support for 16bit gray-scale images
Labels: auto-transferred,priority: normal,feature,category: objdetect

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

```
|| Siegfried Hochdorfer on 2013-07-25 10:03
|| Priority: Normal
|| Affected: None
|| Category: objdetect
|| Tracker: Feature
|| Difficulty: 
|| PR: 
|| Platform: None / None
```
## cv:HoGDescriptor support for 16bit gray-scale images

```
Hi,
the current implementation of the cv::HoGDescriptor supports CV_8U and CV_8UC3 images. I am very interested in an implementation of the cv::HoGDescriptor for 16bit gray-scale (CV_16U) images. I want to try to implement it. But before I start I have two questions. First, is it in generally possible to implement support for 16U_C1 images? Second, how (and who) can I ask for help if i get in problems while trying to implement 16bit support?
```
## History
##### Ivan Korolev on 2013-07-26 06:14

```
Hi Siegfried, 
thank you for your participation, this functionality will be useful! 
> First, is it in generally possible to implement support for 16U_C1 images?
I think it is possible.
> Second, how (and who) can I ask for help if i get in problems while trying to implement 16bit support?
All your questions can be asked here or on GitHub (for more details http://www.code.opencv.org/projects/opencv/wiki/How_to_contribute). The second variant is more preferable, because GitHub is the best place to discuss code.  
-   Assignee set to Marina Kolpakova
-   Status changed from New to Open
```
Repository: opencv
Issue: Add EPNP and P3P to cvFindExtrinsicCameraParams2
Labels: auto-transferred,priority: normal,feature,category: calib3d

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

```
|| Goncalo Lopes on 2013-07-27 11:45
|| Priority: Normal
|| Affected: None
|| Category: calibration, 3d
|| Tracker: Feature
|| Difficulty: 
|| PR: 
|| Platform: None / None
```
## Add EPNP and P3P to cvFindExtrinsicCameraParams2

```
It would be extremely helpful to have the EPNP method on the C API as well. It should be relatively easy to add a "flags" parameter at the end with a default value to keep backwards compatibility and use internal conversions to cv::Mat to use solvePnP.

I know the C API is not currently under active development, but for some applications it is still unfortunately the only effective way to interop with OpenCV...
```
## History
##### Steven Puttemans on 2013-07-28 15:15

```
I guess this is what you call a lost cause. The old OpenCV 1.x C API is depricated, support and development on it has been removed and most likely it will be removed completely in the openCV 3.0 interface. So I don't think more C code will be added to the base system.
-   Assignee set to Alexander Shishkov
```
##### Victor Kocheganov on 2013-08-06 08:58

```
Hello Goncalo,

thank you for sharing your ideas and submitting this ticket!
Unfortunately our resources are very limited at the moment. So if you will have time to help the community and implement this feature by yourself that would be great and highly appreciated! (please read http://www.code.opencv.org/projects/opencv/wiki/How_to_contribute for more details).

Thank you in advance,
Victor Kocheganov
-   Target version set to 2.4.7
-   Assignee changed from Alexander Shishkov to Vadim Pisarevsky
-   Category set to calibration, 3d
```
##### Victor Kocheganov on 2013-08-08 05:41

```
-   Target version changed from 2.4.7 to 3.0-alpha
-   Status changed from New to Open
```
##### Maksim Shabunin on 2015-04-27 09:11

```
-   Target version changed from 3.0-alpha to 3.0
```
Repository: opencv
Issue: white border while displaying a full image with python2.7 and opencv
Labels: bug,auto-transferred,priority: normal,affected: 2.4,category: imgcodecs

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

```
|| Stefano Spirolazzi on 2013-08-02 10:49
|| Priority: Normal
|| Affected: branch '2.4'
|| Category: highgui-images
|| Tracker: Bug
|| Difficulty: 
|| PR: 
|| Platform: x86 / Any
```
## white border while displaying a full image with python2.7 and opencv

```
Hi!

I want to display a black image in a full screen mode. It looks a really sample task to do, but when i run the code below i get a little white strip on top and on the left. It doesn't matter if i change the size of the numpy array, i always get it.
If you run this code, do you get a fully black screen??
I have tried with different laptop and different version of opencv
thanks

@img = np.zeros((800, 1280)) #my resolution is 800, 1280
cv2.namedWindow("test", cv2.WND_PROP_FULLSCREEN)
cv2.setWindowProperty("test", cv2.WND_PROP_FULLSCREEN, cv2.cv.CV_WINDOW_FULLSCREEN)
cv2.imshow("test",img)
cv2.waitKey(0)@
```
## History
##### Victor Kocheganov on 2013-08-06 06:55

```
Hello Stefano,

thank you for submitting this ticket!
Could you please duplicate this question to http://answers.opencv.org/questions/, likely somebody's already faced with similar issue and could help. And it would be highly appreciated if you'll have time to investigate this issue and propose your own fix (if this is indeed a bug). Please see also http://www.code.opencv.org/projects/opencv/wiki/How_to_contribute for details.

Thank you in advance,
Victor Kocheganov
-   Target version set to 2.4.7
-   Assignee set to Vadim Pisarevsky
-   Status changed from New to Open
-   Category set to highgui-images
```
##### Victor Kocheganov on 2013-08-09 10:37

```
-   Assignee changed from Vadim Pisarevsky to Alexander Smorkalov
```
##### Alexander Smorkalov on 2013-08-29 13:59

```
Hello Stefano!

I tried to reproduce your issue on my Linux desktop. Your code works perfect for me. I use Ubuntu and GTK back-end for OpenCV. Please select proper platform in ticket properties if you use something other. I will try the same on Windows and close the issue if everything is ok.
My python and c++ code:

<pre>
import numpy as np
import cv2

img = np.zeros((1080, 1920)) #my resolution is 800, 1280
cv2.namedWindow("test", cv2.WND_PROP_FULLSCREEN)
cv2.setWindowProperty("test", cv2.WND_PROP_FULLSCREEN, cv2.cv.CV_WINDOW_FULLSCREEN)
cv2.imshow("test",img)
cv2.waitKey(0)
</pre>


<pre>
#include <opencv2/core/core.hpp>
#include <opencv2/highgui/highgui.hpp>

int main(int, char**)
{
    cv::Mat frame = cv::Mat::zeros(1080, 1920, CV_8UC3);
    cv::namedWindow("test", cv::WND_PROP_FULLSCREEN);
    cv::setWindowProperty("test", cv::WND_PROP_FULLSCREEN, CV_WINDOW_FULLSCREEN);
    cv::imshow("test", frame);
    cv::waitKey(0);
    return 0;
}
</pre>
```
##### Alexander Smorkalov on 2013-08-29 14:52

```
I reproduce the issue on Windows 8 with WIN32UI back-end.
```
##### Alexander Smorkalov on 2013-09-12 10:51

```
-   Target version changed from 2.4.7 to Next Hackathon
```
Repository: opencv
Issue: VideoWriter output with VP8 not working on Fedora and Ubuntu
Labels: bug,auto-transferred,priority: normal,category: videoio,affected: 2.4

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

```
|| Jan Sedlák on 2013-08-08 14:01
|| Priority: Normal
|| Affected: 2.4.0 - 2.4.5
|| Category: highgui-video
|| Tracker: Bug
|| Difficulty: 
|| PR: 
|| Platform: x64 / Linux
```
## VideoWriter output with VP8 not working on Fedora and Ubuntu

```
Hi, I have asked "this question":http://answers.opencv.org/question/18203/videowriter-output-using-vp8-not-working/ but no one answered it and I think that this is bug.

I want to use VideoWriter with webm output, I am using VP8 codec. It creates VideoWriter correctly and without an error. It creates output file and it puts information about resolution in it, but when I write image into it, it doesn't do anything and output file is always only 7 KiB. I have also tried it in C++ with the same result.

I am using Fedora 19, 64bit. I have added RPM Fusion repos and tried to install every gstreamer plugin, ffmpeg and everything that popped out when I searched "VP8". I also tried it in Ubuntu 13.04 with the same result. When I tried to use different codec (xvid), it worked.

You can try it with code I have pasted on answers.opencv.org.
```
## History
##### Alexander Smorkalov on 2013-08-08 18:16

```
-   Target version set to Next Hackathon
-   Assignee set to Alexander Smorkalov
-   Category set to highgui-video
```
##### Victor Kocheganov on 2013-08-09 08:43

```
-   Status changed from New to Open
```
Repository: opencv
Issue: gpu::StereoConstantSpaceBP crash
Labels: bug,auto-transferred,priority: normal,affected: 2.4,category: gpu/cuda (contrib)

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

```
|| Roman P on 2013-08-12 13:39
|| Priority: Normal
|| Affected: 2.4.0 - 2.4.6
|| Category: gpu (cuda)
|| Tracker: Bug
|| Difficulty: 
|| PR: 
|| Platform: x64 / Windows
```
## gpu::StereoConstantSpaceBP crash

```
When calling StereoConstantSpaceBP operator() on some images, OpenCV crashes with the error message:

OpenCV Error: Gpu API call (unknown error) in unknown function, file D:/Libraries/opencv_2_4_6/opencv/modules/gpu/src/cuda/stereocsbp.cu, line 683

System used: Windows 7 x64, NVIDIA GPU NVS 300, 8 GB RAM, CUDA 5.5, MS Visual Studio Professional 2012 (update 3)

Code reproducing this behavior and example images are attached.
```
## History
##### Steven Puttemans on 2013-08-12 14:38

```
I guess it is a stupid question, but you did rebuilt openCV to include GPU support right?
```
##### Roman P on 2013-08-13 12:24

```
Yes, OpenCV was build with the GPU support.
```
##### Kirill Kornyakov on 2013-08-14 12:00

```
OK, we'll try to check it on our side. Vlad, could you have a look please?

BTW, Roman, if you're able to debug the issue yourself, please work on a pull request. Vladislav is on vacations, and I'm not sure whether he is going to look at this issue soon...
-   Target version set to 2.4.7
-   Assignee set to Vladislav Vinogradov
-   Category set to gpu (cuda)
```
##### Kirill Kornyakov on 2013-08-14 12:04

```
-   Priority changed from High to Normal
```
##### Sergei Nosov on 2013-08-14 15:03

```
-   Status changed from New to Open
```
##### Alexander Smorkalov on 2013-11-27 10:23

```
Vlad, could you have a look please?
-   Affected version changed from 2.4.6 (latest release) to 2.4.0 -
    2.4.6
```
##### Alexander Smorkalov on 2013-11-27 10:23

```
-   Target version changed from 2.4.7 to 2.4.8
```
##### Alexander Smorkalov on 2013-12-30 10:38

```
-   Target version changed from 2.4.8 to 2.4.9
```
##### Alexander Smorkalov on 2014-04-30 19:05

```
-   Target version changed from 2.4.9 to 2.4.10
```
##### Andrea Tomassetti on 2015-03-25 11:39

```
Hi,
I know that this a very old issue but i have the same exactly problem. From time to time, with some images that have different sizes, when calling StereoConstantSpaceBP operator(), OpenCV crashes
<pre>
OpenCV Error: Gpu API call (an illegal memory access was encountered) in unknown function, file D:/toolkits/opencv-2.4.9/modules/gpu/src/cuda/stereocsbp.cu, line 683
error: D:/toolkits/opencv-2.4.9/modules/gpu/src/cuda/stereocsbp.cu:683: error: (-217) an illegal memory access was encountered
</pre>
System used: Windows 8.1 x64, NVIDIA GPU GeForce 740M, 8 GB RAM, CUDA 6.5, MS Visual Studio Professional 2013

The code that sometimes works and sometimes doesn't is the one tooked from gpu samples.
I can try debug the issue myself, if someone, kindly, show me the way.
```