-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cv2.triangulatePoints method generates different decimal values of the reconstructed points. #53
Comments
I'm not sure it's worth spending too much time on this. For our purposes both methods pass the regression test, so I suggest just use the faster method. |
The OpenCV triangulation method, based on HartleyZ00 12.2 pag.312 and appendix of Keir's thesis: A.2 N-View Triangulation, pp. 106, has not been changed much since the fist/second commit on Oct 2015/Jan2018 (see (b)). (a)
|
Triangulating points using
cv2.triangulatePoints()
over_iter_triangulate_point_w_svd()
is definitely quicker (0.91077 milliseconds vs 2.426845 milliseconds), howevercv2.triangulatePoints
seems to use a different computational methods to resolve such points. See below decimal values of reconstructed points.I guess, we might like to dig into the implementation of
cv2.triangulatePoints
to understand where the differences comes from.The text was updated successfully, but these errors were encountered: