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

[Epic] Rosbag2 playback time control and simulation time #696

Closed
48 of 50 tasks
emersonknapp opened this issue Mar 26, 2021 · 13 comments
Closed
48 of 50 tasks

[Epic] Rosbag2 playback time control and simulation time #696

emersonknapp opened this issue Mar 26, 2021 · 13 comments
Assignees
Labels
enhancement New feature or request

Comments

@emersonknapp
Copy link
Collaborator

emersonknapp commented Mar 26, 2021

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

Feature 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):

Code cleanup / tech debt / rearchitecture

@emersonknapp emersonknapp added the enhancement New feature or request label Mar 26, 2021
@emersonknapp emersonknapp self-assigned this Mar 26, 2021
@ros-discourse
Copy link

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

@Karsten1987
Copy link
Collaborator

Once ros2/rclcpp#1452 is in, I'd take the refactoring of removing the rosbag2_node and replace it with the new rclcpp one. Does this sound ok or do I disturb other people's workflow with this?
I feel that the task list above might lead to quite a few conflicts as they massively overlap.

@emersonknapp
Copy link
Collaborator Author

emersonknapp commented Apr 2, 2021

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 GenericPublisher. I added it to the "Code cleanup" section

@Karsten1987
Copy link
Collaborator

Ok, I was just afraid that I would overlap with @MichaelOrlov's last task: "Split Rosbag2Transport into separate Player and Recorder classes"

@emersonknapp
Copy link
Collaborator Author

Yes, that one could overlap, it would probably be good to stage those serially.

@emersonknapp
Copy link
Collaborator Author

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

@MichaelOrlov
Copy link
Contributor

@Karsten1987 Yeah I think it would overlap.
Please go ahead first. I can try to tackle another tasks for a while. Such as jump, play_next and keyboard handling.

@Kaju-Bubanja
Copy link
Contributor

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?

@emersonknapp
Copy link
Collaborator Author

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.

@clalancette
Copy link
Contributor

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.

@emersonknapp
Copy link
Collaborator Author

I hope you mean "yet" smile . 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?

@clalancette
Copy link
Contributor

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.

@emersonknapp
Copy link
Collaborator Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants