-
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
/clock publisher in Player #695
Conversation
6fe7642
to
c5a0c06
Compare
c563f42
to
009c60d
Compare
f06836e
to
bc24c53
Compare
7492fa2
to
9e5ffec
Compare
5e1012c
to
20f37f3
Compare
ce6db18
to
4b35b13
Compare
08e530d
to
daadf5b
Compare
e69696b
to
478285a
Compare
9eb778e
to
2001d5f
Compare
2001d5f
to
daa6f04
Compare
cb3386f
to
e2ab944
Compare
daa6f04
to
55502f9
Compare
9e76353
to
8f21997
Compare
cad4618
to
bddf622
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this generally looks good to me. As mentioned in the comments, I don't think we can so easily just fire up an executor in the play function, but we can address this in a follow up PR.
Testing is indeed a bit tricky, but maybe an end-to-end test in which you test that you get at least a non-zero amount of /clock
callbacks and all these timestamps are in the appropriate time range?
@emersonknapp can we officially put this up for review and run CI on it? I've also noticed a few |
It looks like it!
I was just waiting to have a reasonable test - which it looks like I have now. I'll push it in a couple minutes. |
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
302a763
to
a37da03
Compare
Gist: https://gist.githubusercontent.com/emersonknapp/8785419a3ef05c024b54657b89f76d54/raw/d318e3e26f06cb8534b480ec3dffcf7dcb64e942/ros2.repos |
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, I just had one remark towards the test. I am ok to move on with the rest.
rosbag2_transport/test/rosbag2_transport/test_play_publish_clock.cpp
Outdated
Show resolved
Hide resolved
53c111b
to
6faa696
Compare
Also check that rate is respected Signed-off-by: Emerson Knapp <eknapp@amazon.com>
6faa696
to
7a896d5
Compare
Not sure exactly why this test works so poorly on OSX/Win - trying a OSX build locally to investigate |
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
* Add /clock publishing to Player Signed-off-by: Emerson Knapp <eknapp@amazon.com>
* Add /clock publishing to Player Signed-off-by: Emerson Knapp <eknapp@amazon.com>
* Design for rosbag2 handling of clock/simtime (ros2#675) * Add a design dock for rosbag2 handling of clock/simtime Signed-off-by: Emerson Knapp <eknapp@amazon.com> * PlayerClock initial implementation - Player functionally unchanged (ros2#689) * Initial PlayerClock integration - functionality unchanged * Create PlayerClock, a pure virtual interface with `now()`, and `sleep_until()` for Player to use to control timing of message playback * TimeControllerClock implementation of PlayerClock * Removes time handling from `Player` in favor of using this new class Signed-off-by: Emerson Knapp <eknapp@amazon.com> * /clock publisher in Player (ros2#695) * Add /clock publishing to Player Signed-off-by: Emerson Knapp <eknapp@amazon.com> * fix for foxy abi Signed-off-by: mitsudome-r <ryohsuke.mitsudome@tier4.jp> * fix bug Signed-off-by: mitsudome-r <ryohsuke.mitsudome@tier4.jp> Co-authored-by: Emerson Knapp <537409+emersonknapp@users.noreply.github.com>
Closes #99
Design: #675
Add a
rosgraph_msgs/Clock
publisher to thePlayer
- that usesPlayerClock::now()
to publish current time.Expose this publish frequency to the CLI