2020-04-18 16:30:49 -0600 | received badge | ● Notable Question (source) |
2020-01-26 05:03:48 -0600 | received badge | ● Notable Question (source) |
2019-06-21 03:10:32 -0600 | received badge | ● Popular Question (source) |
2018-08-22 00:13:37 -0600 | received badge | ● Popular Question (source) |
2018-05-07 14:19:50 -0600 | received badge | ● Teacher (source) |
2017-08-09 04:08:17 -0600 | answered a question | cv::VideoCapture::open(file) causes fatal memory error I've solved this issue. By analyzing the program with The issue was caused by |
2017-01-19 19:04:44 -0600 | received badge | ● Critic (source) |
2017-01-18 22:00:33 -0600 | asked a question | cv::VideoCapture::open(file) causes fatal memory error Hello. After upgrading Ubuntu to trusty, a simple video-load code became producing fatal memory error. The code is just opening an video file: Executing this causes a fatal memory error: I compiled this code with OpenCV 2.4.8 and 2.4.13; both cases finished with the above error. The backtrace by gdb was: It seemed that the issue was caused by libavformat and/or libavutil, so I reinstalled them but it didn't work. If you have any ideas to fix this issue or investigate more, please let me know. I'm struggling with this issue for these several months. Many thanks. |
2016-06-28 10:40:36 -0600 | commented question | Mat::at operator with single index berak, let's make the reason clear. OpenCV does NOT guarantee a continuous memory allocation. When the memory is not allocated continuously, a low-level block access like |
2016-06-27 23:56:35 -0600 | commented question | Mat::at operator with single index berak, with |
2016-06-27 23:54:53 -0600 | commented question | Mat::at operator with single index LBerger, I understand that when we use Mat::at, we have to know the element type and size (above, it's float, 4 byte). So I wrote like |
2016-06-27 14:16:53 -0600 | asked a question | Mat::at operator with single index Although the OpenCV documents say:
we can use Mat::at with a single index for usual MxN matrix. e.g. This way is useful to me. My question is: Is this not a regular way? If OpenCV changes the implementation and restricts the above style, then I would have a trouble. Edited: What I want to do is getting a row without a big overhead. I'm seeking a way lighter than |
2016-06-13 19:30:00 -0600 | received badge | ● Student (source) |
2016-06-13 18:18:42 -0600 | received badge | ● Scholar (source) |
2016-06-13 17:05:32 -0600 | asked a question | Multiplication between Mat and Scalar For a given mask image (binary
where I am expecting: but actually there is no definition of Computing an image for each channel (i.e. |
2016-04-21 14:48:56 -0600 | received badge | ● Enthusiast |
2016-04-04 02:25:55 -0600 | received badge | ● Self-Learner (source) |
2016-04-01 16:23:59 -0600 | received badge | ● Editor (source) |
2016-04-01 16:14:09 -0600 | answered a question | Stereo calibration for beginners A camera calibration tool implemented on ROS (Robot Operating System) was easy to use.
Although for me this tool would be enough, its source code is available online (written in Python though). Other good pages were:
|
2016-04-01 16:07:16 -0600 | commented question | Stereo calibration for beginners Thank you so much for the pages! |
2016-03-30 14:28:56 -0600 | asked a question | Stereo calibration for beginners Hello, I'd like to make a stereo program in C++ with OpenCV 2.4. I just tested cv::StereoBM and cv::StereoSGBM without calibration, but the result was inaccurate. Could you give me good references (URLs) written about recent stereo calibration with OpenCV? I also want some sample codes. Although I googled stereo calibration with OpenCV, there are many resources including old ones, someone's trials, I couldn't find a good reference. Please recommend a good introduction. Thanks! -- Akihiko |