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
With a queue size of 1 it appears that the messages are being stored in a buffer and the buffer will continue to fill up so instead of taking in the most recent message we begin reading in older messages first, even though newer ones are available.
From my understanding, that is not the intended behavior of ROS. In my case, I only really care about the latest measurement, so I had the queue size set to 1 so that I would never receive an old measurement if a newer one existed (as described here).
My current workaround is to add a check to see if the time that the message was received was greater than some threshold (meaning the message was too old) and if that is the case then I just ignore the message and read the next one. Not a long term general solution.
The text was updated successfully, but these errors were encountered:
With a queue size of 1 it appears that the messages are being stored in a buffer and the buffer will continue to fill up so instead of taking in the most recent message we begin reading in older messages first, even though newer ones are available.
From my understanding, that is not the intended behavior of ROS. In my case, I only really care about the latest measurement, so I had the queue size set to 1 so that I would never receive an old measurement if a newer one existed (as described here).
My current workaround is to add a check to see if the time that the message was received was greater than some threshold (meaning the message was too old) and if that is the case then I just ignore the message and read the next one. Not a long term general solution.
The text was updated successfully, but these errors were encountered: