-
Notifications
You must be signed in to change notification settings - Fork 510
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
extrinsics parameters from euroc dataset and rovio.info are different #228
Comments
Did you take into account that in the camera yaml it's T_BS (sensor to base) while in rovio.info it's qCM (imu to camera) which is the inverse. This also accounts for why the translation is different since it's expressed in a different frame. |
Hi, thanks for your reply and helpful information. I did not notice that that should be T_BS, since I have assumed that they all follow the ASL Kalibr format, where they only use T_cam_imu to transform from IMU to camera coordinates as link. Based on your information, I created one python file, which trys to turn the T_BS to qCM, as follows: from pyquaternion import Quaternion
import numpy as np
T_bs = np.matrix([[0.0148655429818, -0.999880929698, 0.00414029679422, -0.0216401454975],
[0.999557249008, 0.0149672133247, 0.025715529948, -0.064676986768],
[-0.0257744366974, 0.00375618835797, 0.999660727178, 0.00981073058949],
[0.0, 0.0, 0.0, 1.0]])
T_sb = np.linalg.inv(T_bs)
quat_euro_ = Quaternion(matrix=T_sb[0:3, 0:3]) it turns out to be better result than before, since qCM from ROVIO config is 0.712 + 0.0067i - 0.008j -0.702k, and my calculation result is 0.712 + 0.0077i -0.010j -0.702k, the slight difference here I guess is acceptable now. However, I am not quite sure about the translation vector, if I directly taken the first three elements of the last column from the inversed transformation matrix, it should be [0.065, -0.207, -0.008], which is not quite exactly as described in ROVIO.info. Thx in advence! :) |
Did somebody eventually figure out how to transform the translation vector from euroc dataset to rovio format? |
The values in Here is my best attempt at getting the right values for the rovio.info file (for Camera0). Note that the translation should not be taken from the
This yields
|
Hi,
I noticed that extrinsic parameters from euroc dataset and rovio.info are different, of course, I have transferred the rotation matrix into the quaternion format before the comparison,
Are the differences above are acceptable?
And in my view, the translation vector should be kind of same, since they are independent of the expression format of the rotation, however,
the vector in euroc:
the vecor in rovio.info:
of course, these two set of parameters could get some kind of odometry results when online-calibration is on, but could you share some hints w.r.t these parameters?
The text was updated successfully, but these errors were encountered: