Skip to content

ROS2 how is header.stamp assigned in each /ouster/points message? #89

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
JeffR1992 opened this issue Mar 29, 2023 · 1 comment
Closed
Assignees
Labels
question Further information is requested

Comments

@JeffR1992
Copy link

JeffR1992 commented Mar 29, 2023

I wanted to ask how the ROS2 driver calculates the header.stamp field for each /ouster/points PointCloud2 message. Is this field set to the timestamp of the first point in the cloud, the last point in the cloud, or is it assigned in some other way (e.g. header.stamp is set to the time just before the PointCloud2 message is published by the ROS2 driver)?

Any links to code showing where the assignment of header.stamp is being done would be appreciated. Thanks very much.

@JeffR1992 JeffR1992 added the question Further information is requested label Mar 29, 2023
@Samahu Samahu self-assigned this Mar 29, 2023
@Samahu
Copy link
Contributor

Samahu commented Mar 29, 2023

The timestamp of the point cloud message is assigned to the time of the first measurement of the scan, regardless of the size of azimuth window.

In case of packets drop at the start of the lidar scan then the value of the first measurment is imputed(using linear interpolation). For more details refer to #67

I am going to close this ticket but if you feel that I didn't address your question feel free to re-open.

@Samahu Samahu closed this as completed Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants