The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Here is the answers for the above stated problems
STEREO CAMERA PROBLEM: To calibrate stereo camera without hardware synchronisation, the approximate=0.01 flag should be used. If it's set up then this problem becomes the original calibration problem.
To solve it you have to rename cv_bridge_boost.dylib to cv_bridge_boost.so. After you will start seeing the calibration window, how it will not respond to mouse clicks. To solve it you have to rebuild opencv with GTK as a backend. These are the steps I took to successfully build opencv
I had to modify CMakeLists.txt in opencv folder as follows
Line 129:
OCV_OPTION(WITH_GTK "Include GTK support" OFF )
LINE 135:
OCV_OPTION(WITH_OPENGL "Include OpenGL support" ON IF (NOT ANDROID) )
LINE 617:
status(" Carbon:" NO)
LINE 616:
status(" Carbon:" NO)
LINE 140:
OCV_OPTION(WITH_QT "Build with Qt Backend support" OFF IF (NOT ANDROID AND NOT IOS) )
Then gtk should be installed
brew install gtk+
brew install gtkglext
and /opt/X11/lib/pkgconfig should be added to ~/.profile
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/opt/X11/lib/pkgconfig:$PKG_CONFIG_PATH
after building opencv, I could run stereo calibration without a problem.
PS: I hope I did not forget to mention any steps.
| | 2 | No.2 Revision |
Here is the answers for the above stated problems
STEREO CAMERA PROBLEM: problems. To calibrate stereo camera without hardware synchronisation, the approximate=0.01 flag should be used. If it's set up then this problem becomes the original calibration problem.
problem with monocular camera.
To solve it you have to rename cv_bridge_boost.dylib to cv_bridge_boost.so. After you will start seeing the calibration window, how it will not respond to mouse clicks. To solve it you have to rebuild opencv with GTK as a backend. These are the steps I took to successfully build opencv
I had to modify CMakeLists.txt in opencv folder as follows
Line 129:
OCV_OPTION(WITH_GTK "Include GTK support" OFF )
LINE 135:
OCV_OPTION(WITH_OPENGL "Include OpenGL support" ON IF (NOT ANDROID) )
LINE 617:
status(" Carbon:" NO)
LINE 616:
status(" Carbon:" NO)
LINE 140:
OCV_OPTION(WITH_QT "Build with Qt Backend support" OFF IF (NOT ANDROID AND NOT IOS) )
Then gtk should be installed
brew install gtk+
brew install gtkglext
and /opt/X11/lib/pkgconfig should be added to ~/.profile
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/opt/X11/lib/pkgconfig:$PKG_CONFIG_PATH
after building opencv, I could run stereo calibration without a problem.
PS: I hope I did not forget to mention any steps.
| | 3 | No.3 Revision |
Here is the answers for the above stated problems. To calibrate stereo camera without hardware synchronisation, the approximate=0.01 flag should be used. If it's set up then this problem becomes the original calibration problem with monocular camera.
To solve it you have to rename cv_bridge_boost.dylib to cv_bridge_boost.so. After you will start seeing the calibration window, how however it will not respond to mouse clicks. To solve it this you have to rebuild opencv with GTK as a backend. These are the steps I took to successfully build opencv
I had to modify CMakeLists.txt in opencv folder as follows
Line 129:
OCV_OPTION(WITH_GTK "Include GTK support" OFF )
LINE 135:
OCV_OPTION(WITH_OPENGL "Include OpenGL support" ON IF (NOT ANDROID) )
LINE 617:
status(" Carbon:" NO)
LINE 616:
status(" Carbon:" NO)
LINE 140:
OCV_OPTION(WITH_QT "Build with Qt Backend support" OFF IF (NOT ANDROID AND NOT IOS) )
Then gtk should be installed
brew install gtk+
brew install gtkglext
and /opt/X11/lib/pkgconfig should be added to ~/.profile
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/opt/X11/lib/pkgconfig:$PKG_CONFIG_PATH
after building opencv, I could run stereo calibration without a problem.
PS: I hope I did not forget to mention any steps.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.