You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I've been using this tool for the past few weeks, and have to say it works quite well. However, I was realizing there is a lack of documentation on the convention for the output roll, pitch, and yaw angles. When trying to incorporate these angles into a URDF (via the rpy arg) the transform ended up being way off despite looking good during the calibration, which made me realize that two different angle conventions are likely being used.
If there is pre-existing documentation that I missed kindly point me in that direction. Thank you!
The text was updated successfully, but these errors were encountered:
There is no documentation for that, although I did implement it specifically so I could copy and paste the values directly into a URDF. I don't know why it's not working for you.
I have run into a similar issue where using the commented rpy flipped the camera.
It might be related to #132
Could it be a conversion difference between how eigen and ros-geometry convert quaternion to euler angles?
In my case, using the ros-geometry euler_from_quaternion on the quaternion saved in the launch file with sxyzprovides good euler angles.
(Here "good" means "the tf associated to the optical camera frame points where it should in rviz").
Hello! I've been using this tool for the past few weeks, and have to say it works quite well. However, I was realizing there is a lack of documentation on the convention for the output roll, pitch, and yaw angles. When trying to incorporate these angles into a URDF (via the rpy arg) the transform ended up being way off despite looking good during the calibration, which made me realize that two different angle conventions are likely being used.
If there is pre-existing documentation that I missed kindly point me in that direction. Thank you!
The text was updated successfully, but these errors were encountered: