The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
I have the same question actually. I thought that I should always process the latest message when queue_size is set to 1. But rospy actually queues up a long list of old messages.
One way to walk around is that use the pointcloud callback to update a global variable, and process this variable in another spinner.
| | 2 | No.2 Revision |
I have the same question actually. exactly. I thought that I should always process the latest message when queue_size is set to 1. But rospy actually queues up a long list of old messages.
One way to walk around is that use the pointcloud callback to update a global variable, and process this variable in another spinner.
| | 3 | No.3 Revision |
I have the same question exactly. I thought that I should always process the latest message when queue_size is set to 1. But rospy actually queues up a long list of old messages.
And roscpp and rospy seems to give different behaviors in terms of this situation.
One way to walk around is that use the pointcloud callback to update a global variable, and process this variable in another spinner.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
