-
Notifications
You must be signed in to change notification settings - Fork 1
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
About the legged-odom timestamp #3
Comments
The legged-odom msgs were not precisely time synchronized because the unitree_legged_msgs/HighState msgs provided by unitree_legged_msgs do not have header/timestamp. If you want to use legged-odom's timestamps in robot state estimation, we recommond using the time when unitree_legged_msgs/HighState msgs were recorded in rosbag as timestamps or simply using the time when subscriber recieves the msgs after setting --clock when playing rosbag. |
您好,想请问您有没有这方面的问题?关于IMU的内参问题。我使用了calibration/imu.yaml中的4个imu噪声参数,在sequense 8上去运行vins-mono算法,但是发现使用这里imu.yaml文件中的imu噪声参数,算法运行有问题,表现是机器人走一小段路,算法已经走了很长一段。网上有人说vins-mono的配置文件中,imu需要使用离散噪声,我猜测imu.yaml中提供的4个噪声参数是连续噪声,所以我对白噪声和随机游走分别 /0.01^0.5、*0.01^0.5。这里因为imu频率是100hz,所以采样时间是0.01s.然而还是无法正确运行。 |
我对VO没有研究,由于四足离散的运动方式,所以IMU噪声可能较大,你可以试试低通滤波,或者调大下IMU的噪声。 |
The original unitree_legged_msgs/HighState msg does not have timestamp information, how to synchronize the time of the data or how can i get the leggedodom timestamp?
The text was updated successfully, but these errors were encountered: