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
For depth camera of relatively high resolution and high frame rate, or for computing platform which have limited resources, the pointcloud data is generated direcly from camera/depth/image_raw(or other raw depth images), which would cause the pointcloud data is relatively huge.
During my test with Astra Pro with rqt_topic (topic monitor), /camera/depth/points could reach 80M/s data rate. To generate this message consume a lot of CPU.
So I'm wondering if there is a possible way to configure processing.launch.xml, so that the package could generate pointcloud from topics like /camera/depth/image_raw/compressed?
The text was updated successfully, but these errors were encountered:
For depth camera of relatively high resolution and high frame rate, or for computing platform which have limited resources, the pointcloud data is generated direcly from camera/depth/image_raw(or other raw depth images), which would cause the pointcloud data is relatively huge.
During my test with Astra Pro with rqt_topic (topic monitor), /camera/depth/points could reach 80M/s data rate. To generate this message consume a lot of CPU.
So I'm wondering if there is a possible way to configure processing.launch.xml, so that the package could generate pointcloud from topics like /camera/depth/image_raw/compressed?
The text was updated successfully, but these errors were encountered: