ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I believe the canonical way to do this -- even from a roscpp application -- would be to use Topic statistics (and the support in rqt_graph.

This comes with a bit of overhead though: ros/ros_comm#1626.

The advantage would be this requires no additional subscribers (@drone_lab: the "computational cost" is not in spinning, it's in serialising the messages to an additional subscriber).

I believe the canonical way to do this -- even from a roscpp application -- would be to use Topic statistics (and the support in rqt_graph.).

This comes with a bit of overhead though: ros/ros_comm#1626.

The advantage would be this requires no additional subscribers (@drone_lab: the "computational cost" is not in spinning, it's in serialising the messages to an additional subscriber).

I believe the canonical way to do this -- even from a roscpp application -- would be to use Topic statistics (and the support in rqt_graph).

This comes with a bit of overhead though: ros/ros_comm#1626.

The advantage would be this requires no additional subscribers (@drone_lab: (@drone_lab : the "computational cost" is not in spinning, it's in serialising the messages to an additional subscriber).

I believe the canonical way to do this -- even from a roscpp application -- would be to use Topic statistics (and the support in rqt_graph).

This comes with a bit of overhead though: ros/ros_comm#1626.

The advantage would be this requires no additional subscribers (@drone_lab ( @drone_lab : the "computational cost" is not in spinning, it's in serialising the messages to an additional subscriber).