This forum is disabled, please visit https://forum.opencv.org
| 2017-03-27 10:46:52 -0600 | received badge | ● Famous Question (source) |
| 2015-08-17 11:38:04 -0600 | received badge | ● Notable Question (source) |
| 2014-10-28 22:44:14 -0600 | commented question | error: invalid use of 'using ptr = class std::shared_ptr' There's an identifier clash between globally-defined "template<...> using ptr" and opencv in-namespace-in-function usage of the identifier. Since couldn't remove inclusion of either of the headers, renamed opentrack identifier. Is there a more proper solution? |
| 2014-09-18 09:13:03 -0600 | received badge | ● Popular Question (source) |
| 2014-01-15 23:19:11 -0600 | received badge | ● Nice Question (source) |
| 2012-08-05 15:41:57 -0600 | received badge | ● Student (source) |
| 2012-08-05 14:55:47 -0600 | commented answer | focal length and calibration This helps a lot. Thank you for the indepth explanation! |
| 2012-08-05 14:52:32 -0600 | received badge | ● Supporter (source) |
| 2012-08-05 14:52:31 -0600 | received badge | ● Scholar (source) |
| 2012-08-05 05:43:03 -0600 | asked a question | focal length and calibration Is there a mapping of camera FOV and resolution to focal length as accepted by solvePnP or especially POSIT? End-users can't be expected to do chessboard-calibration. :( Since there are camera specs available online, it would've been much easier if such mapping existed. What are the variables for focal length, anyway? I always guessed, or used a retractable ruler on POSIT, my face, and several (dozen) iterations of launching the POSIT-using code with different focal lengths. This is far from robust, though. I'll be grateful from the bottom of my heart to anyone who provides an equation that works!!! -sh |