Why do I see negative average delay in tf_monitor?
It seems to be only when I run simulation.
It seems to be only when I run simulation.
Negative average delay comes from the transform being timestamped in the future when sent or by network delays when running in simulation.
In simulation time is sent over the /clock topic and may arrive after transforms sent from a different node with the same time.
A few nodes stamp data in the future, most noteably AMCL. This is valid for AMCL and other similar nodes publishing a small correction transform which is expected to remain approximately static and never have inherent velocity. The value is that AMCL can update at a slow rate but does not prevent transforms through it's correction to be used at a high rate.
Please start posting anonymously - your entry will be published after you log in or create a new account.
Asked: 2011-03-18 14:51:30 -0500
Seen: 749 times
Last updated: Mar 18 '11
TF2 removed and catkin_make error.. [closed]
Transformation between two frames from unconnected trees
When using TF API in a plugin, can I specify the topic from which to listen to the transformations?
Unable to transform object from namespaced frame 'ns/base_link' to planning frame 'base_link'
About TF Transformations between /odom and /base_footprint
Writing a tf broadcaster (C++) errors
how to broadcast a tf frame? [closed]