Revision history [back]

I'm not 100% sure on the answer to this (my gut says no, you have to use a remapping when running multiple of them), but I think you may be able to get around the problem by just throttling sensor_msgs::PointCloud2 types. I've not looked into the code, but does it matter what data is contained in the PointCloud?

Maybe you could even extend it to a ShapeShifter type, like the node version of the generic throttle does and see about it getting into nodelet_topic_tools (not really sure why there isn't one already...).

I'm not 100% sure on the answer to this (my gut says no, "no, you have to use a remapping when running multiple of them), them"), but I think you may be able to get around the problem by just throttling sensor_msgs::PointCloud2 types. I've not looked into the code, but does it matter what data is contained in the PointCloud?

Maybe you could even extend it to a ShapeShifter type, like the node version of the generic throttle does and see about it getting into nodelet_topic_tools (not really sure why there isn't one already...).

I'm not 100% sure on the answer to this (my gut says "no, you have for example how would rostopic echo know which to use a remapping when running multiple of them"), subscribe to"), but I think you may be able to get around the problem by just throttling sensor_msgs::PointCloud2 types. I've not looked into the code, but does it matter what data is contained in the PointCloud?

Maybe you could even extend it to a ShapeShifter type, like the node version of the generic throttle does and see about it getting into nodelet_topic_tools (not really sure why there isn't one already...).