-
Notifications
You must be signed in to change notification settings - Fork 261
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
Merge "Add additional mode of publishing sim time updates (#1036)" to rolling #1050
Conversation
Signed-off-by: Kyle Marcey <[email protected]>
…dates triggered by replayed messages Signed-off-by: Kyle Marcey <[email protected]>
…clock updates. An additional mode of operation has been added to the Player class to allow for /clock updates. When this mode is active, /clock updates are triggered whenever messages are replayed rather than at a fixed rate. Optionally, a list of triggering topics can be set so that only a subset of replayed messages will trigger the /clock update. This mode is most useful when replaying applications which do some sanity checking or correlation of message data to system timestamps. If the application does not need the sim time to be updated at a consistent rate, this mode can substantially reduce the overhead of having sim time enabled in rosbag2. Signed-off-by: Kyle Marcey <[email protected]>
Running CI: |
|
@MichaelOrlov I tried to reproduce the |
CI passed after second iteration. |
This pull request has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/ros-2-tsc-meeting-minutes-8-18-2022/27050/1 |
Original PR #1036 targeted
master
and was overwritten by fa60ff7