Ask Your Question

GruenSein's profile - activity

2020-04-06 09:11:00 -0500 received badge  Popular Question (source)
2018-10-13 07:31:38 -0500 commented answer CMake option to prefer static libs

Thanks for your time, even though I think, this is unrelated to macOS. CMake is able to locate the libraries properly an

2018-10-13 05:48:01 -0500 commented answer CMake option to prefer static libs

So, I installed OpenCV using brew with the --build-from-source flag. This actually builds dynamic and static libs. It ex

2018-10-13 05:12:42 -0500 commented answer CMake option to prefer static libs

Thank you for your reply. Unfortunately, this is not working for me. I have the shared as well as the static libraries i

2018-10-12 13:43:26 -0500 asked a question CMake option to prefer static libs

CMake option to prefer static libs Hello all, I am using OpenCV 3.4.3 on macOS 10.14 for one of my projects. While I ha

2018-07-21 04:05:40 -0500 commented answer how to insert a small size image on to a big image

Does this also work with getRectSubPix-ROIs? Will OpenCV handle the interpolation, when I copy or add to a sub pixel ROI

2017-09-01 09:19:07 -0500 asked a question Calib3D performance

Calib3D performance Hi all, I am performing many camera calibrations sequentially using a very large number of marker c

2017-07-24 03:59:15 -0500 commented question UndistortPoints randomly returning huge values

Possibly, but if so, it happens within OpenCVs undistortPoints function call. I have looked at the problem a bit more closely and found that usually when it happens it is only one of 100k points that exhibits this behavior. For now, my solution is to filter it out and only use the remaining peaks but I'd much rather fix this behavior completely

2017-07-21 03:06:31 -0500 asked a question UndistortPoints randomly returning huge values

Hi all,

to let me put everything in context, let me describe what I am doing/trying to do. I have a multiple camera setup which I calibrate using OpenCV. The images obtained from the cameras contain a bunch of bright spots which I use to triangulate their real world coordinates. This has been working flawlessly so far. To improve the real world coordinate accuracy, I use the resulting point cloud and the positions of the peaks in the images, to refine the calibration of each camera. This is also working well. Afterwards, I repeat the undistortion of the raw peak positions in the images so that the undistorted peak list reflects the changed calibration parameters. In randomly occuring cases after recalibrating the cameras, however, I am left with absolutely unusably undistorted peak positions that exhibit values of the order of 1.0E+28 and above. Usually, the undistored peak positions should be in the range of +-1 or so. So far, I have only been able to trace this behavior back to the undistortPoints call. My suspicion is that the calibration uses a not-quite-robust-enough optimizer so that a large number of world-image-coordinate pairs (approx. 100k) with some degree of uncertainty can cause it to diverge.

Has anyone else seen this kind of behavior and can suggest some countermeasures?

Thanks for your input and all the best, Alex