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
We received odometry message, but we cannot get the corresponding TF world->camera_depth_optical_frame at data stamp 0.449000s (odom msg stamp is 0.481000s). Make sure TF of odometry is also published to get more accurate pose estimation. This warning is only printed once.
#1266
Open
aasishkc4 opened this issue
Apr 23, 2024
· 2 comments
It says "We received odometry message, but we cannot get the corresponding TF world->camera_depth_optical_frame at data stamp 0.449000s (odom msg stamp is 0.481000s). Make sure TF of odometry is also published to get more accurate pose estimation. This warning is only printed once." so noted down the time difference but which parameter I can tweak for adjusting the timestamp delay?
Checking tf at this time
Odom time
Diff
2.242
2.282
0.04
149.651
149.657
0.006
0.8
0.832
0.032
0.438
0.471
0.033
0.398
0.431
0.033
0.399
0.431
0.032
0.623
0.656
0.033
0.449
0.481
0.032
The text was updated successfully, but these errors were encountered:
That strange, it seems the odometry topic is published before the odom TF topic. That looks more an issue on the odometry plugin used by the simulator. The only downside right now is that pose of the sensors may not be accurate.
I am constantly getting this error
It says "We received odometry message, but we cannot get the corresponding TF world->camera_depth_optical_frame at data stamp 0.449000s (odom msg stamp is 0.481000s). Make sure TF of odometry is also published to get more accurate pose estimation. This warning is only printed once." so noted down the time difference but which parameter I can tweak for adjusting the timestamp delay?
The text was updated successfully, but these errors were encountered: