2020-04-10 11:28:48 -0600 | received badge | ● Popular Question (source) |
2016-12-09 02:04:48 -0600 | received badge | ● Enthusiast |
2016-12-06 17:13:07 -0600 | commented answer | cv::triangulatePoints give strange results Ok. I will check it again. Maybe I copy sth wrong and if so I will correct post. |
2016-12-05 19:50:18 -0600 | commented question | cv::triangulatePoints give strange results I write answer to my post because it was easier than edit the first one (to not loose my question and written data). I write link to the images (50 pairs), all that I have from calibration and I also put my code |
2016-12-05 19:48:09 -0600 | answered a question | cv::triangulatePoints give strange results So I write the most important part of my code (not all because program is large but I think it will be enough) Images Intrinsic and extrinsic parameteres for left Intrinsic and extrinsic parameteres for right 1. Here is startOffline() method that starts all calculation: 2. Here is stereovideocallback() method that allows to detect markers and save data to m_history. 3. Here is loadCalibration() function and readCameraParameters() (more) |
2016-12-05 00:11:00 -0600 | commented question | cv::triangulatePoints give strange results After undistortPoints? I get 0.231818 x 0.127843 for first and 0.2478 x 0.162624 for second image |
2016-12-04 19:16:43 -0600 | commented question | cv::triangulatePoints give strange results First I corrected my mistake (I change type of original points pt1 and pt2 from cv::Point to cv::Point2f). And I use now undistortPoints before saving to m_history from where I get points to triangulate method. I update post and add results after undistortPoints and triangulation. |
2016-12-04 18:36:42 -0600 | commented question | cv::triangulatePoints give strange results Other library uses only: camera matrix, distortion coeffs, marker size that I set before start calculation. Nothing else. I correct that typo and update values of triangulation (now I get very large values from triangulation) |
2016-12-04 17:39:41 -0600 | commented question | cv::triangulatePoints give strange results From first image is: 432.921x321.005 and for second is 432.918x321.005 |
2016-12-04 16:57:22 -0600 | commented question | cv::triangulatePoints give strange results After cameras calibration I use stereoRectify to obtain projection matrices. In a moment I will update my post with projection matrices values |
2016-12-04 16:38:15 -0600 | commented question | cv::triangulatePoints give strange results Please explain more precisely what you ask, because I do not quite understand (maybe because of not perfect knowledge of English) |
2016-12-03 17:23:23 -0600 | received badge | ● Editor (source) |
2016-12-03 17:20:56 -0600 | asked a question | cv::triangulatePoints give strange results Hi, Here is my code: Where I do mistake? Results from triangulation: And from other library (it seems quite correct): My projection matrices: EDIT: After correct cv::Point to cv::Point2f and with cv::undistortPoints I get that: (I pass to cv::undistortPoints only ... (more) |
2016-10-04 06:50:07 -0600 | commented question | cvFindExtrinsicParameters2 use and translation vector meaning? I am not using cvFindExtrinsicParameters2. It is contained in method from library that I use. Library has very poor documentation, and I want to understand if I can use that method to my purpose. |
2016-10-04 06:08:56 -0600 | asked a question | cvFindExtrinsicParameters2 use and translation vector meaning? Hi, I have two questions. First question. I have marker. I get 2D coords of marker in pixels (image plane). Second question Can I use cvFindExtrinsicParameters2 to calculate 3D coords if I have 2D coords in pixels, intrinsic and extrinsic parameters? Or it is used only to calculate rotation matrix and translation vector? |