[pointcloud_to_laserscan] publish rate higher than scan_time

asked 2021-01-29 03:58:14 -0600

felixN
108 ●15 ●20 ●25

Hi, I'm having a bit of trouble understanding the "scan_time" parameter from poincloud_to_laserscan package.

I was supposing that it was the publish rate of the output (laser_scan). However, I have it set at 0.333 seconds (so 3Hz), but the publishing frequency of the scan is nearly 10Hz (as the pointcloud topic).

Do I misunderstand the meanning of this parameter?

Thanks a lot in advance

Felix

The launchfile for the laser scan :

<?xml version="1.0"?>
<launch>

    <arg name="camera_name"          default="zed2" />

    <node pkg="pointcloud_to_laserscan" type="pointcloud_to_laserscan_node" name="pointcloud_to_laserscan" >
        <remap from="cloud_in" to="$(arg camera_name)/zed_node/point_cloud/cloud_registered" />
        <remap from="scan" to="$(arg camera_name)/zed_node/scan" />
        <rosparam>
target_frame: base_link
transform_tolerance: 0.01
min_height: -0.7
max_height: 0.3
angle_min: -M_PI/2
angle_max: M_PI/2
angle_increment: M_PI/360/2
scan_time: 0.333
range_min: 0.2
range_max: 40.0
use_inf: true
inf_epsilon: 1.0
concurrency_level: 1
</rosparam>
        </node>
</launch>

Sample output of rostopic hz for the scan:

$ rostopic hz /zed2/zed_node/scan 
subscribed to [/zed2/zed_node/scan]
average rate: 9.285
    min: 0.097s max: 0.121s std dev: 0.00687s window: 9
average rate: 9.358
    min: 0.097s max: 0.121s std dev: 0.00480s window: 18
average rate: 9.354
    min: 0.097s max: 0.121s std dev: 0.00470s window: 27
average rate: 9.360
    min: 0.097s max: 0.121s std dev: 0.00401s window: 37
average rate: 9.338
    min: 0.096s max: 0.121s std dev: 0.00448s window: 46
average rate: 9.330
    min: 0.096s max: 0.121s std dev: 0.00413s window: 55

and for the pointcloud

$ rostopic hz /zed2/zed_node/point_cloud/cloud_registered 
    subscribed to [/zed2/zed_node/point_cloud/cloud_registered]
    average rate: 9.806
        min: 0.065s max: 0.133s std dev: 0.01900s window: 8
    average rate: 9.898
        min: 0.065s max: 0.133s std dev: 0.01296s window: 18
    average rate: 9.891
        min: 0.065s max: 0.133s std dev: 0.01087s window: 28

edit retag flag offensive close merge delete

add a comment

Comments

Thanks a lot.

I was unederstanding "used to populate" in the sens that the message was populated (in the sens created and sent) at this frequency (and that this parameter could therefore be used for downsampling).

But the source code seems to confirm your version.

Did it seem clear to you at first reading that it was only used to populate that field? If not, it might be interresting to change the documentation, for exemple replacing it by :

scan_time (double, default: 1.0/30.0) - The scan rate in seconds. Only used to populate the scan_time field of the output laser scan message.

felixN ( 2021-01-29 08:51:40 -0600 )edit

I can definitely see both ways of reading it. I'd say more clarity is better, and it wouldn't take much effort to change the wording. It's even less clear on the wiki:

~scan_time (double, default: 1.0/30.0) The scan rate in seconds.

Can't hurt to express your thoughts to the maintainer(s).

tryan ( 2021-01-29 09:13:39 -0600 )edit

Thanks, I just created an issue on git to propose the change

felixN ( 2021-01-29 10:16:15 -0600 )edit

add a comment

[pointcloud_to_laserscan] publish rate higher than scan_time

1 Answer

Comments

Question Tools

Stats

Related questions

[pointcloud_to_laserscan] publish rate higher than scan_time edit

1 Answer

Comments

Question Tools

Stats

Related questions

[pointcloud_to_laserscan] publish rate higher than scan_time