-
Notifications
You must be signed in to change notification settings - Fork 248
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
[Epic] Rosbag2 playback time control and simulation time #696
Comments
This issue has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/tooling-wg-breakout-session-rosbag2-playback-time-control/19711/1 |
Once ros2/rclcpp#1452 is in, I'd take the refactoring of removing the |
I think that would be fine - I don't see it interfering very much with most of the existing line items. Most of the changes now should be very focused, and not be near the direct usage of |
Ok, I was just afraid that I would overlap with @MichaelOrlov's last task: "Split Rosbag2Transport into separate Player and Recorder classes" |
Yes, that one could overlap, it would probably be good to stage those serially. |
But - maybe it won't be too bad! Perhaps you can stage it as "replace rosbag2::generic with rclcpp::generic" - which definitely will have little to no conflict - then do "remove the rosbag2node" as a second stage |
@Karsten1987 Yeah I think it would overlap. |
I don't see this awesome feature in the list of new features here: https://docs.ros.org/en/foxy/Releases/Release-Galactic-Geochelone.html#timeline-before-the-release Is it still planned to be released for galactic? |
Yes - everything that is currently checked off will be in Galactic (and maybe a couple more small things). None of the rosbag2 changes are listed on that page. |
I hope you mean "yet" 😄 . It would be awesome to have a high-level overview of the (massive) changes to rosbag2 listed on that page. |
Yes, yet. Should we open a PR against the page source for it? |
Yes, whenever you are ready, please feel free to open a PR and I'm happy to review it. |
Closing this issue, we don't need it anymore. It's a huge amount of work that we did! The only thing really remaining is use-sim-tim, which can be tracked via its own issue #694 |
Description
Tracking issue for the group of features (planned for Galactic) around control of the flow of time during rosbag2 playback. See "Completion Criteria" for full feature list
Design
play_next
Add play_next() API to design document #708Feature List / Completion Criteria
Design at https://github.com/ros2/rosbag2/blob/master/docs/design/rosbag2_playback_time.md is fully implemented including all of the following features (names tagged where items are known to be work-in-progress):
PlayerClock
integration intoPlayer
(@emersonknapp)PlayerClock
implementation: PlayerClock initial implementation - Player functionally unchanged #689ros2 bag play
with keyboard controls #55 (@emersonknapp)ros2 bag play
with keyboard controls #55 (@MichaelOrlov)/clock
during playback play - publish /clock topic #99 (@emersonknapp)play
torosbag2_py
to make it easier to add new playback options: Add rosbag2_py::Player::play to replace rosbag2_transport_python version #693/clock
during playback (use-sim-time
) "use-ros-time" - Drive rosbag2 playback via /clock time source #694 (@emersonknapp )Clock::sleep_for
andClock::sleep_until
rclcpp#1730Code cleanup / tech debt / rearchitecture
record
torosbag2_py
rosbag2_py pybind wrapper for "record" - remove rosbag2_transport_py #702rclcpp
's GenericPub/Sub, remove from rosbag2 (followup to Add rclcpp_generic, a publisher and subscription for serialized messages rclcpp#1452) (@Karsten1987) use rclcpp::Node for generic pub/sub #714Rosbag2Transport
into separatePlayer
andRecorder
classes Split Rosbag2Transport into Player and Recorder classes - first pass to enable further progress #721Player
andRecorder
as NodesThe text was updated successfully, but these errors were encountered: