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

rqt_runtime_monitor: items go stale when using simulated time #69

Closed
trainman419 opened this issue Aug 27, 2014 · 3 comments
Closed

rqt_runtime_monitor: items go stale when using simulated time #69

trainman419 opened this issue Aug 27, 2014 · 3 comments
Labels

Comments

@trainman419
Copy link
Contributor

When playing back log files and displaying the results in rqt_runtime_monitor, all of the diagnostics go stale when the log file is paused for a few seconds.

@ablasdel
Copy link
Contributor

Would you mind providing steps to reproduce the issue? Does this happen with all bag files?

@dirk-thomas
Copy link
Contributor

I think the runtime monitor marks entries as stale when it does not receive new data for a while. It simply does not know that the data is coming from a bag file and the user has decided to pause playback.

@trainman419
Copy link
Contributor Author

This happens with any bag file containing diagnostics information.

I think it's a bug that it falsely marks things as stale when I have /use_sim_time set and I'm playing back bag files with the --clock option.

@ablasdel ablasdel added the bug label Sep 10, 2014
@trainman419 trainman419 mentioned this issue Oct 15, 2014
ablasdel added a commit that referenced this issue Oct 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants