sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: iOS Installation Instructions are Out of Date
Labels: bug,auto-transferred,priority: normal,category: documentation,affected: 2.4

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

```
|| Philip Salvaggio on 2014-03-04 02:25
|| Priority: Normal
|| Affected: 2.4.8 (latest release)
|| Category: documentation
|| Tracker: Bug
|| Difficulty: Easy
|| PR: 
|| Platform: ARM / iOS
```
## iOS Installation Instructions are Out of Date

```
The instructions found on this page:

http://docs.opencv.org/doc/tutorials/introduction/ios_install/ios_install.html

no longer work for creating opencv2.framework. The symbolic link for /Developer is no longer needed. More importantly, the build_framework.py file must be executed from the opencv/platforms/ios/ directory. The new command should read.

cd ~/<my_working_directory>/opencv/platforms/ios/
python build_framework.py ~/<my_working_directory>/ios
```
## History
##### Dinar Ahmatnurov on 2014-03-04 10:53

```
Hi, Philip! 

Could you please create a pull request for this? http://code.opencv.org/projects/opencv/wiki/How_to_contribute
-   Assignee set to Roman Donchenko
-   Status changed from New to Open
```
##### John Moses on 2014-03-14 05:32

```
Philip Salvaggio wrote:
> The instructions found on this page:
> 
> http://docs.opencv.org/doc/tutorials/introduction/ios_install/ios_install.html
> 
> no longer work for creating opencv2.framework. The symbolic link for /Developer is no longer needed. More importantly, the build_framework.py file must be executed from the opencv/platforms/ios/ directory. The new command should read.
> 
> cd ~/<my_working_directory>/opencv/platforms/ios/
> python build_framework.py ~/<my_working_directory>/ios

I could not get either to work.  I get the following error:
OSError: [Errno 2] No such file or directory: '../build/iPhoneOS-arm64/install/include/opencv2'

Additionally, whatever the solution is opencv/platforms/ios/readme.txt will need to be updated as well.  Several other people are having similar problems:
http://stackoverflow.com/questions/16179120/error-compiling-the-opencv-framework
http://answers.opencv.org/question/14566/opencv-24-build-failed-error-while-creating-ios/
```
Repository: opencv
Issue: Opencv 2.4.8, MinGW, cv::CascadeClassifier();
Labels: bug,auto-transferred,priority: normal,category: build/install,affected: 2.4

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

```
|| Denis Gottardello on 2014-03-05 17:06
|| Priority: Normal
|| Affected: 2.4.8 (latest release)
|| Category: build/install
|| Tracker: Bug
|| Difficulty: 
|| PR: 
|| Platform: x86 / Windows
```
## Opencv 2.4.8, MinGW, cv::CascadeClassifier();

```
In order to build OpenCV with MinGW32 is necessary to apply the patch described here:
http://stackoverflow.com/questions/21103042/error-while-building-opencv-monitorfromrect-was-not-declared-in-this-scope
But the serious problem is that the object *"cv::CascadeClassifier()"* is unusable.
The row
*"cv::CascadeClassifier *a= new cv::CascadeClassifier();"*
or
*"cv::CascadeClassifier a;"*
causes an application crash!
On Linux and Mac all works well.
```
## History
##### Denis Gottardello on 2014-03-05 17:07

```
The problem happens also with BackgroundSubtractorMOG2 and BackgroundSubtractorMOG.
```
##### Dinar Ahmatnurov on 2014-03-05 17:16

```
Roman. please have a look
-   Priority changed from Blocker to Normal
-   Assignee set to Roman Donchenko
-   Category set to build/install
```
##### Dinar Ahmatnurov on 2014-03-05 17:17

```
-   Status changed from New to Open
```
##### Denis Gottardello on 2014-06-17 19:49

```
Is this bug still open?
```
##### Denis Gottardello on 2015-01-01 17:58

```
Up!
```
Repository: opencv
Issue: Chamfer distance sample crashes with glibc  double free or corruption
Labels: bug,auto-transferred,priority: normal,category: legacy,category: contrib,affected: 2.4

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

```
|| Aleksandrs Ecins on 2014-03-11 17:01
|| Priority: Normal
|| Affected: 2.4.8 (latest release)
|| Category: legacy, contrib
|| Tracker: Bug
|| Difficulty: 
|| PR: 
|| Platform: x64 / Linux
```
## Chamfer distance sample crashes with glibc  double free or corruption

```
Hello,

Trying to run the sample Chmafer matching code from OpenCV (/trunk/opencv/samples/cpp/chamfer.cpp) I get the following error:
    * glibc detected :double free or corruption (!prev): 0x0000000000745bb0 **

The reason is that in function @chamerMatching(img, tpl, results, costs)@ a template is created and then a reference to it is added inside @matcher_ object@:
<pre>
ChamferMatcher::Template template_(templ, (float)templScale);
ChamferMatcher::Matches match_instances = matcher_.matching(template_, img);
</pre>

As a result when the function returns @template_@ is destroyed first and then when @matcher_@ is destroyed it tries to destroy the same template again hence you gen an error.
I was able to get the code to run by commenting out the line that deletes templates in the desctructor of @Matching@:
<pre>
    ~Matching()
    {
        for (size_t i = 0; i<templates.size(); i++) {
            //delete templates[i];
        }
    }
</pre>
However, is is not a solution to the proble since it can introduce memory leaks.
```
## History
##### Ivan Korolev on 2014-03-17 05:33

```
Hi Aleksandrs,
thanks for the bug report! Unfortunately, now we have limited human resources. So if you could investigate this issue and get back with some additional information or send a fixing pull request on GitHub (http://www.code.opencv.org/projects/opencv/wiki/How_to_contribute), it would be much appreciated!

-   Assignee changed from Vadim Pisarevsky to Aleksandrs Ecins
-   Status changed from New to Open
```
Repository: opencv
Issue: Inconsistent default parameters for SURF_GPU
Labels: bug,auto-transferred,priority: normal,affected: 2.4,category: gpu/cuda (contrib)

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

```
|| Nikolas Engelhard on 2014-03-19 09:35
|| Priority: Normal
|| Affected: 2.4.8 (latest release)
|| Category: gpu (cuda)
|| Tracker: Bug
|| Difficulty: Easy
|| PR: 
|| Platform: Any / Any
```
## Inconsistent default parameters for SURF_GPU

```
Hello

I just started with OpenCV with Cuda support and wrote a little project using SURF_GPU and found a strange behaviour:

in GPU.hpp:
  explicit SURF_GPU(double _hessianThreshold, int _nOctaves=4,
         int _nOctaveLayers=2, *bool _extended=false*, float _keypointsRatio=0.01f, bool _upright = false);

but also

modules/nonfree/src/surf_gpu.cpp
cv::gpu::SURF_GPU::SURF_GPU()
    {
        hessianThreshold = 100;
        *extended = 1;*
        nOctaves = 4;
        nOctaveLayers = 2;
        keypointsRatio = 0.01f;
        upright = false;
}



This code therefore fails: 
        SURF_GPU sgpu;
        assert( ! sgpu.extended);

but this one is valid:
        SURF_GPU sgpu(100);
        assert( ! sgpu.extended);

Passing a value for the hessianThreshold should not change the descriptor size.

Fixing this is trivial but would also probably break some programs.
```
## History
##### Nikolas Engelhard on 2014-03-19 09:35

```
-   Assignee deleted (Vladislav Vinogradov)
```
##### Daniil Osokin on 2014-03-20 09:17

```
Hi, thanks for the attention. Please, send a pull request with fix (http://code.opencv.org/projects/opencv/wiki/How_to_contribute).
-   Description changed from Hello I just started with OpenCV with Cuda
    support and wrote a little proje... to Hello I just started with
    OpenCV with Cuda support and wrote a little projec... More
-   Assignee set to Nikolas Engelhard
```
##### Nikolas Engelhard on 2014-03-20 10:50

```
Hello Daniil

I'll try to submit a patch but I won't have the time in the next weeks.
```
##### Daniil Osokin on 2014-03-21 07:49

```
Thanks, Nikolas! Looking forward to your pull request!
-   Assignee changed from Nikolas Engelhard to Vladislav Vinogradov
```
##### Sergei Nosov on 2014-03-24 15:08

```
-   Status changed from New to Open
```
Repository: opencv
Issue: Wrong types for constants in Matlab or wrong type conversion
Labels: bug,auto-transferred,priority: normal,affected: 3.4,category: matlab bindings

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

```
|| Yuval Ta on 2014-04-09 08:58
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: matlab bindings
|| Tracker: Bug
|| Difficulty: 
|| PR: 
|| Platform: x64 / Windows
```
## Wrong types for constants in Matlab or wrong type conversion

```
I noticed this when calling cv.matchTemplate from matlab. The method type (cv.TM_CCOEFF_NORMED, ...) are of type 'double', and probably mistakenly converted to zero (thus always use the CV_TM_SQDIFF method) before calling the matchTemplate function.
The simple workaround is to convert the method type to 32 bit integer, but I assume it's not the intended way.

Doesn't work (return result of CV_TM_SQDIFF method):
cv.matchTemplate(I, T, cv.TM_CCOEFF_NORMED);
Works:
cv.matchTemplate(I, T, uint32(cv.TM_CCOEFF_NORMED));

This might be duplicate of #3465.

Thanks
```
## History
##### Dmitry Retinskiy on 2014-05-30 05:56

```
Hi Vadim,

could you check this problem?
Thanks.
```
##### Dmitry Retinskiy on 2014-05-30 05:56

```
-   Status changed from New to Open
```
Repository: opencv
Issue: Python & .jp2 - imread() error on Windows only
Labels: bug,auto-transferred,priority: normal,affected: 2.4,category: imgcodecs

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

```
|| Yasuyuki Araki on 2014-04-10 08:30
|| Priority: Normal
|| Affected: 2.4.0 - 2.4.8
|| Category: highgui-images
|| Tracker: Bug
|| Difficulty: Medium
|| PR: 
|| Platform: x86 / Windows
```
## Python & .jp2 - imread() error on Windows only

```
Attempting to open some JPEG2000 files fails on Windows 7.

im = cv2.imread("chartsample.jp2")
error: cannot decode code stream

It succeeds on Linux (CentOS 6) and Mac (OS X 10).
Is there any workarounds?
```
## History
##### chuansheng wei on 2014-04-10 17:52

```
i've try myself to read the img on ubuntu and win7,it succeed on both system. maybe your windows7 system got some problem
```
##### Alexander Shishkov on 2014-05-06 20:34

```
-   Affected version changed from 2.4.8 (latest release) to 2.4.0 -
    2.4.8
-   Difficulty set to Medium
-   Assignee set to Alexander Smorkalov
-   Category set to highgui-images
```
##### Andrew Senin on 2014-05-07 15:47

```
-   Status changed from New to Open
```
Repository: opencv
Issue: Training models for the Latent SVM detector
Labels: bug,auto-transferred,priority: normal,affected: 2.4,category: objdetect

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

```
|| David W.  on 2014-04-21 07:58
|| Priority: Normal
|| Affected: branch '2.4' (2.4-dev)
|| Category: objdetect
|| Tracker: Bug
|| Difficulty: Easy
|| PR: 
|| Platform: Any / Any
```
## Training models for the Latent SVM detector

```
Hi there! :)

The OpenCV implementation of the Latent SVM detector [1] from the objdetect module works great with the prebuild models from the opencv_extra repository [2].
But how can you train your own models? Some information on this topic in the OpenCV documentation would be very helpful. How were the models from opencv_extra generated?
Does somebody know the relationship between the OpenCV implementation and the "original" one [3]? Unfortunatly the author does not know [4].

I hope that we have somebody in the community who knows something about this stuff.

[1] http://docs.opencv.org/master/modules/objdetect/doc/latent_svm.html
[2] https://github.com/Itseez/opencv_extra/tree/master/testdata/cv/latentsvmdetector
[3] http://www.cs.berkeley.edu/~rbg/latent/
[4] https://github.com/rbgirshick/voc-dpm/issues/4
```
## History
##### Dmitry Retinskiy on 2014-09-17 10:16

```
Hi David,

I'd suggest asking your question at this forum http://answers.opencv.org.
-   Affected version changed from 2.4.8 (latest release) to branch '2.4'
    (2.4-dev)
```
##### Steven Puttemans on 2014-09-22 13:47

```
If you want a new model, you need to download the original software of Felzenswalb.
It has a training interface with it.

Those models can be used in OpenCV. There is no OpenCV dedicated training interface provided.

The models in the extra folder are just retrieved from the Pascal VOC Challenge.
```
Repository: opencv
Issue: openCV support for multiple camera instance in Android
Labels: auto-transferred,feature,priority: low,category: videoio(camera),platform: android

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

```
|| ganesh manvizhi on 2014-04-22 15:44
|| Priority: High
|| Affected: None
|| Category: android
|| Tracker: Feature
|| Difficulty: Hard
|| PR: 
|| Platform: None / None
```
## openCV support for multiple camera instance in Android

```
Is it possible to access multiple camera (4 cameras in my case) in openCV on Android platform. If so, Please also mention the Android versions that supports this feature of openCV. 

Please let me clarify this issue ASAP.

Regards,
Ganesh.M
```
## History
##### Alexander Smorkalov on 2014-04-30 19:05

```
-   Target version changed from 2.4.9 to 2.4.10
```
##### Dmitry Retinskiy on 2014-05-29 07:23

```
Hi Ganesh,

I'd recommend to ask the community at Q&A forum:
http://answers.opencv.org/questions/
```
##### Ayberk Özgür on 2014-09-29 12:56

```
It should be possible in theory, as long as those 4 cameras are all connected to different USB buses (which is highly unlikely).
```
Repository: opencv
Issue: Failed to cross-compile with mingw-w64 
Labels: bug,auto-transferred,priority: normal,category: build/install,affected: 3.4

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

```
|| Alexey Gornostaev on 2014-04-23 06:19
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: build/install
|| Tracker: Bug
|| Difficulty: Easy
|| PR: 
|| Platform: x64 / Linux
```
## Failed to cross-compile with mingw-w64 

```
https://github.com/Itseez/opencv/blob/master/modules/core/src/parallel.cpp

45: #if defined WIN32 || defined WINCE

should looks like

45: #if defined WIN32 || defined WINCE || defined _WIN32

cause SYSTEM_INFO structure is undefined here elsewhere:

454: #if defined WIN32 || defined _WIN32
455:    SYSTEM_INFO sysinfo;
```
## History
##### Alexey Gornostaev on 2014-04-23 06:22

```
another one: highgui/src/cap_ffmpeg.cpp using HMODULE declaration but not includes windows-specific headers
```
##### Dmitry Retinskiy on 2014-05-30 05:27

```
Hi Roman,
could you check this problem?
Thanks.
-   Status changed from New to Open
```
##### Philippe FOUBERT on 2014-05-30 10:13

```
Hi,

Just for information: I am also using mingw-w64 on branch 'master' (3.0-dev) (update at least once a week) and I don't have any compilation problem.

+Details:+
* mingw   : gcc version 4.8.2, x86_64-win32-seh, Built by MinGW-W64 project
* OS      : Windows 7 Professionnel, Service Pack 1, 64 bits
* branch  : https://github.com/philippefoubert/opencv.git
* computer: Intel core i7-3740QM CPU @2.70GHz

Regards,
  Philippe.
```
Repository: opencv
Issue: OpenCV Python unable to access correct OpenNI device channels
Labels: bug,auto-transferred,priority: normal,affected: 2.4,category: videoio(camera)

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

```
|| Andrew Braun on 2014-04-24 03:48
|| Priority: Normal
|| Affected: 2.4.9 (latest release)
|| Category: highgui-camera
|| Tracker: Bug
|| Difficulty: Medium
|| PR: 
|| Platform: x64 / Linux
```
## OpenCV Python unable to access correct OpenNI device channels

```
I put together some simple code in python to grab different channels from OpenNI devices. I built OpenCV myself with all the PrimeSense and OpenNI support enabled. The OpenNI samples work perfectly for both the Kinect sensor and PrimeSense sensor, as well as the OpenCV samples  for testing OpenNI support (./cpp-example-openni_capture). 

Here is the code I put together.

@   

    import cv2
    import cv2.cv as cv
    capture = cv2.VideoCapture(cv.CV_CAP_OPENNI)
    capture.set(cv.CV_CAP_OPENNI_IMAGE_GENERATOR_OUTPUT_MODE, cv.CV_CAP_OPENNI_VGA_30HZ)
    print capture.get(cv.CV_CAP_PROP_OPENNI_REGISTRATION)
    while True:
        if not capture.grab():
            print "Unable to Grab Frames from camera"
            break
        okay1, depth_map = capture.retrieve(cv.CV_CAP_OPENNI_DEPTH_MAP)
        if not okay1:
            print "Unable to Retrieve Disparity Map from camera"
            break
        okay2, gray_image = capture.retrieve(cv.CV_CAP_OPENNI_GRAY_IMAGE)
        if not okay2:
            print "Unable to retrieve Gray Image from device"
            break
        cv2.imshow("depth camera", depth_map)
        cv2.imshow("rgb camera", gray_image)
        if cv2.waitKey(10) == 27:
            break
    cv2.destroyAllWindows()
    capture.release()
@

So everything runs fine, but the results that are being displayed are not the correct channels... For example if I wanted to access the gray image channel and the depth map channel, both images being displayed are depth_maps. 

Yes I've tried accessing other channels and changing the OPENNI_IMAGE_GENERATOR_MODE. Unfortunately the results have stayed consistent. No matter what I try I always get the same depth channel back. depth_map-gray_image yields an all black image.

Like I said the C++ OpenCV OpenNI examples all work perfectly for both the Kinect sensor and primesense sensor. It seems like a problem with the Python modules, or I am doing something really stupid.

Running on Ubuntu 12.04 LTS OpenCV version 2.4.9

Thanks for helping.
Drew
```
## History
##### Alexander Smorkalov on 2014-04-30 19:05

```
-   Target version changed from 2.4.9 to 2.4.10
```
##### Dmitry Retinskiy on 2014-09-17 10:12

```
Alexander, could you check this?
Thanks.
-   Affected version changed from 2.4.8 (latest release) to 2.4.9
    (latest release)
-   Assignee set to Alexander Smorkalov
-   Status changed from New to Open
```
Repository: opencv
Issue: python cv2.floodFill Segmentation Fault on large images
Labels: bug,auto-transferred,priority: normal,category: imgproc,category: video,affected: 2.4

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

```
|| Michael Goldman on 2014-04-30 16:07
|| Priority: Normal
|| Affected: 2.4.0 - 2.4.8
|| Category: imgproc, video
|| Tracker: Bug
|| Difficulty: Medium
|| PR: 
|| Platform: x64 / Linux
```
## python cv2.floodFill Segmentation Fault on large images

```
Performing python floodFill on large images ~2Gigapixels yields segmentation fault. Have tried on Ubuntu 12.04 with 12GB memory and RedHat 5.10 with ~96GB memory.

-- success
% python floodfill_repro.py 32768 32768

-- success
% python floodfill_repro.py 46341 46341

-- fail
% python floodfill_repro.py 46341 46342

-- fail
% python floodfill_repro.py 65535 65535
```
## History
##### Alexander Shishkov on 2014-05-06 20:19

```
-   Affected version changed from 2.4.8 (latest release) to 2.4.0 -
    2.4.8
-   Difficulty set to Medium
-   Assignee set to Vadim Pisarevsky
-   Category set to imgproc, video
```
##### Andrew Senin on 2014-05-07 15:49

```
-   Status changed from New to Open
```
Repository: opencv
Issue: Releasing VideoCapture / Webcam doesn't work
Labels: bug,auto-transferred,priority: normal,category: python bindings,affected: 3.4

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

```
|| Martijn van der Veen on 2014-05-02 21:02
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: python bindings
|| Tracker: Bug
|| Difficulty: Medium
|| PR: 
|| Platform: x64 / Linux
```
## Releasing VideoCapture / Webcam doesn't work

```
Using python (3.4) bindings on Ubuntu 14.04 with build-in webcam using v4l4, master branch:

In [2]: cap = cv2.VideoCapture(0)
HIGHGUI ERROR: V4L/V4L2: VIDIOC_S_CROP

In [3]: a,b = cap.read() # although error, reading frame works (a=True, b=np.array)

In [4]: cap.release()

In [5]: cap.isOpened()
Out[5]: False

In [6]: cap = cv2.VideoCapture(0)
HIGHGUI ERROR: V4L2: Pixel format of incoming image is unsupported by OpenCV

In [7]: a,b = cap.read()
VIDIOC_STREAMON: Bad file descriptor


After calling .release(), webcam light stays on and webcam stays unreachable for other programs (e.g., Cheese).
```
## History
##### Martijn van der Veen on 2014-05-02 21:24

```
(Btw, the webcam _is_ released when python exits, but in some cases that's not enough - e.g., for running programs that need to release the webcam now and then.)
```
##### Alexander Smorkalov on 2014-05-04 15:58

```
-   Category set to python bindings
```
##### Andrew Senin on 2014-05-06 14:21

```
Hello Martijn, 

Since our resources are limited please consider investigating this issue and creating a fixing pull request (http://code.opencv.org/projects/opencv/wiki/How_to_contribute). All help to the project is highly appreciated!
-   Difficulty set to Medium
-   Assignee set to Martijn van der Veen
-   Status changed from New to Open
```
##### Maksim Shabunin on 2015-04-27 09:12

```
-   Target version changed from 3.0-beta to 3.0
```
##### Maksim Shabunin on 2015-04-28 13:42

```
Can not reproduce with the 3.0-rc1 release. Webcam is successfully released and reopened.

Can you, please, try to reproduce it with the latest version? Probably it has been fixed already.
-   Assignee changed from Martijn van der Veen to Maksim Shabunin
```
##### Maksim Shabunin on 2015-04-28 13:42

```
-   Status changed from Open to Incomplete
```
Repository: opencv
Issue: GraphCutSeamFinderBase has no virtual destructor
Labels: bug,auto-transferred,priority: normal,affected: 3.4,category: stitching

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

```
|| Alexey Gornostaev on 2014-05-12 04:55
|| Priority: Normal
|| Affected: branch 'master' (3.0-dev)
|| Category: stitching
|| Tracker: Bug
|| Difficulty: Easy
|| PR: 
|| Platform: x64 / Linux
```
## GraphCutSeamFinderBase has no virtual destructor

```
Stitching module failed to build with -Werror=non-virtual-dtor
```
## History
##### Dmitry Retinskiy on 2014-05-29 06:23

```
Hi Leonid,

could you check this problem?
Thanks.
-   Assignee changed from Roman Donchenko to Leonid Beynenson
-   Category changed from build/install to stitching
```
##### Dmitry Retinskiy on 2014-05-30 07:42

```
-   Status changed from New to Open
```