-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
geometry2/tf2 warning TF_REPEATED_DATA #1555
Comments
stribor14
pushed a commit
to romb-technologies/cartographer_ros
that referenced
this issue
Nov 10, 2020
…tographer-project#1555 Signed-off-by: stribor14 <[email protected]>
stribor14
pushed a commit
to romb-technologies/cartographer_ros
that referenced
this issue
Nov 10, 2020
…tographer-project#1555 Signed-off-by: stribor14 <[email protected]>
stribor14
pushed a commit
to romb-technologies/cartographer_ros
that referenced
this issue
Nov 11, 2020
…tographer-project#1555 Signed-off-by: stribor14 <[email protected]>
MichaelGrupp
pushed a commit
that referenced
this issue
Nov 13, 2020
… (#1556) Signed-off-by: stribor14 <[email protected]> Co-authored-by: stribor14 <[email protected]>
WLwind
pushed a commit
to WLwind/cartographer_ros
that referenced
this issue
Jan 5, 2021
…tographer-project#1555 (cartographer-project#1556) Signed-off-by: stribor14 <[email protected]> Co-authored-by: stribor14 <[email protected]>
doisyg
pushed a commit
to wyca-robotics/cartographer_ros
that referenced
this issue
Nov 18, 2021
…tographer-project#1555 (cartographer-project#1556) Signed-off-by: stribor14 <[email protected]> Co-authored-by: stribor14 <[email protected]> Signed-off-by: Guillaume Doisy <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Git commit hash:
2712067e0563229248ac60c3e7be9b55c462bdce
(and all previous)This issue is linked with the following issue: ros/geometry2#467
A change in geometry2 package was introduced where there is a warning when multiple transforms between the same frames are published with the same timestamp.
This happens in simulation, but I did not test it on the robot yet, but from looking at the source code, I think the problem is specifically with the simulation at the following lines:
cartographer_ros/cartographer_ros/cartographer_ros/node.cc
Lines 258 to 263 in 2712067
My guess: if using the pose_extrapolator, simulated time can(?) trigger the timer event multiple times if
trajectory_publish_period_sec
is sufficiently small which results in repeated TF publishing (because in the first iteration extrapolator advances which results instamped_transform.header.stamp
being the same in the next iteration)The resulting repeated transform is ignored by the tf2 buffers (new standard behavior in ROS noetic), so the only consequence is a lot of generated warnings (which makes the roslog unreadable)
The text was updated successfully, but these errors were encountered: