Thanks for the suggestion. For those of you who haven't seen it @BrannonKing put together a PR for the ROS2 Time design document.
https://github.com/ros2/design/pull/128
If you're interested in this topic I've replied in detail at:
https://github.com/ros2/design/pull/128#pullrequestreview-35463951
At a high level I don't think that we want to overload the simulation `/clock` abstraction to support system time synchronization as well. Clock synchronization is something that is quite specialized and there are many mature mechanisms for doing that already. We don't want to have to provide our own implementation when we can leverage existing technologies such as Network Time Protocol.
For the use case of a system that starts without a system clock. It's relatively straight forward to have it run ntpdate or chrony on startup to get it to the right system time.
---
[Visit Topic](
https://discourse.ros.org/t/of-clocks-and-simulation-betimes-and-otherwise/1587/6) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)