Skip to content
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

ROS-350[NOETIC]: 't' timestamp field content is not plausible #386

Merged
merged 4 commits into from
Oct 11, 2024

Conversation

Samahu
Copy link
Contributor

@Samahu Samahu commented Oct 9, 2024

Related Issues & PRs

Summary of Changes

  • Don't apply offset to destaggered timestamps within the point cloud
  • Make sure the the timestamps align correctly when destaggerd is option is OFF
  • Misc: update bug/question templates

Validation

  • run the driver with default option (destaggered=ON, organized=ON)
    • observe that the timestamps are consistent
  • run the driver with default option (destaggered=OFF, organized=ON)
    • observe that the timestamps appear staggerd

@Samahu Samahu added the bug Something isn't working label Oct 9, 2024
@Samahu Samahu self-assigned this Oct 9, 2024
@Samahu Samahu changed the title ROS-350: 't' timestamp field content is not plausible ROS-350[NOETIC]: 't' timestamp field content is not plausible Oct 9, 2024
@Samahu Samahu merged commit 92ab33d into master Oct 11, 2024
1 check passed
@Samahu Samahu deleted the ROS-350_t_timestamp_field_content_is_not_plausible branch October 11, 2024 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

't' timestamp field content is not plausible
2 participants