ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
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).
2 | No.2 Revision |
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).
3 | No.3 Revision |
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).
4 | No.4 Revision |
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).