Use a "steady clock" when measuring time differences #427
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've found out recently the difference between the default rclcpp clock (a
system clock
) versus asteady clock
. The steady clock is monotonically increasing, meaning it can't go backward in time. So it is more suitable for measuring time differences.Making this type of change fixed the flakiness of some of our MoveIt CI tests, so I hope it helps here.
Reference reading: https://design.ros2.org/articles/clock_and_time.html#time-abstractions