-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Calibration of D415 in ROS #508
Comments
Hi, The output of the calibration process is set in the firmware and so, no file is needed for the operation of realsense2_camera ROS wrapper or other realsense based applications. That's why there is no file. I am not familiar with the camera_calibration application. If you need to obtain the values of the calibration to create your own .yaml file you can get the current values by typing: |
@doronhi is there a way to get the intrinsic and the distrortion vector for the camera. These if obtained can be helpful in getting relasense cameras to work wiith other opencv applications like aruco-tags |
Yes I am have the question as well. how do i get the information needed for this https://berndpfrommer.github.io/tagslam_web/intrinsic_calibration/ |
Could you elaborate? Why is |
it did i got it to work. I was just being stupid. |
Hi,
I'm trying to calibrate realsense in a similar fashion as i did for Kinect in ROS using a checkerboard.
For RGB----->rosrun camera_calibration cameracalibrator.py image:=/camera/color/image_raw camera:=/camera/color --size 8x6 --square 0.0245
For Depth-->rosrun camera_calibration cameracalibrator.py image:=/camera/color/image_rect_raw camera:=/camera/depth --size 8x6 --square 0.0245
But everytime i get the error service not found.
But when i did for kinect it saved .yaml file automatically in .ros folder. I already did the dynamic calibration as mentioned on Intel website. But that calibration file i guess i cannot use .yaml file in ros. So, i was trying to get the same .yaml file for d415 in ROS. Please help.
The text was updated successfully, but these errors were encountered: