Skip to content

Commit 5581b26

Browse files
authored
Clarify publishing behavior when no header timestamp is present (ros2#823)
Signed-off-by: Devin Bonnie <[email protected]>
1 parent ee76ed2 commit 5581b26

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

source/Concepts/About-Topic-Statistics.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -60,10 +60,10 @@ The data is published as a `statistics_msg/msg/MetricsMessage
6060
at a configurable period (default 1 second) to a configurable topic (default ``/statistics``).
6161
Note that the publishing period also serves as the sample collection window period.
6262

63-
Since received message period requires a message timestamp in a header field, empty data is published
64-
if no timestamp is found.
65-
This behavior avoids the absence of a signal problem and is meant to explicitly show that a measurement
66-
could not be made.
63+
Since received message period requires a message timestamp in a header field, empty data is published.
64+
That is, all statistics values are NaN if no timestamp is found.
65+
Publishing NaN values instead of not publishing at all avoids the absence of a signal problem and is
66+
meant to explicitly show that a measurement could not be made.
6767

6868
The first sample of each window for the received message period statistic does not yield a measurement.
6969
This is because calculating this statistic requires knowing the time the previous

0 commit comments

Comments
 (0)