You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In other depth camera nodes the publishers written in a fashion where there aware whether the topics they're publishing to have any subscribers.
For example iai_kinect kinect2_bridge pays attention and only starts publishing message when a subscriber is connected. In my initial work with the 435, it appears that the rgbd node is constantly publishing, consuming resources when other consuming processed aren't attached or listenting.
Can someone confirm this is the behavior? it sure does consume a lot of CPU just running the node.
The text was updated successfully, but these errors were encountered:
In other depth camera nodes the publishers written in a fashion where there aware whether the topics they're publishing to have any subscribers.
For example iai_kinect kinect2_bridge pays attention and only starts publishing message when a subscriber is connected. In my initial work with the 435, it appears that the rgbd node is constantly publishing, consuming resources when other consuming processed aren't attached or listenting.
Can someone confirm this is the behavior? it sure does consume a lot of CPU just running the node.
The text was updated successfully, but these errors were encountered: