Skip to content
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

Provide a way to clear tf2 buffers when the clock is reset #64

Closed
trainman419 opened this issue May 16, 2014 · 5 comments
Closed

Provide a way to clear tf2 buffers when the clock is reset #64

trainman419 opened this issue May 16, 2014 · 5 comments

Comments

@trainman419
Copy link
Contributor

When running a simulation or playing back a bag file with --clock, I often try to leave most of my nodes running, and only restart the thing that is publishing to /clock

Unfortunately, the tf2 internal buffer does not reset when /clock jumps backwards, and the tf2 subscribers don't have a manual mechanism to tell them that the clock has been reset, and they should clear their buffers.

See http://answers.ros.org/question/164026/how-can-i-reset-the-simulated-clock/ for more information.

@jbohren
Copy link
Member

jbohren commented May 16, 2014

+100

@v4hn
Copy link
Contributor

v4hn commented Jun 12, 2014

+1 In theory there should be a mechanism in place to automatically clean the buffers when a loop is detected. I know this worked with tf by EOL in fuerte because I fixed it myself.
Also, I remember, @tfoote afterwards pushed some related changes for tf2.
I didn't investigate, but I currently have problems with tf2 and rosbag play --loop as well (current hydro).

@ZdenekM
Copy link

ZdenekM commented Aug 15, 2014

+1

1 similar comment
@skohlbr
Copy link

skohlbr commented Sep 17, 2014

+1

@tfoote
Copy link
Member

tfoote commented Sep 18, 2014

duplicate #43

@tfoote tfoote closed this as completed Sep 18, 2014
clalancette pushed a commit to lucasw/geometry2 that referenced this issue Nov 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants