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

Fixed node ID=0 issues as msgs may not have seq. #1202

Merged
merged 1 commit into from
Sep 2, 2024

Conversation

borongyuan
Copy link
Contributor

(cherry picked from commit 097cab0)
This issue also appears in ros1. For example, when RGBDImage message is published directly, only its header's seq is automatically filled. The header's seq of sub-messages, such as CameraInfo, is not automatically filled.

@matlabbe
Copy link
Member

matlabbe commented Sep 2, 2024

Great, thanks!

@matlabbe matlabbe merged commit 3eb0b47 into introlab:master Sep 2, 2024
1 check passed
matlabbe added a commit that referenced this pull request Sep 4, 2024
…ed) (#1206)

* Fixed odometry latency

* Fixed node ID=0 issues as msgs may not have seq. (#1202)

(cherry picked from commit 097cab0)

* Odom: removed long processing from ros callbacks (decreasing delay, also making delay independent of the message filters topic_queue_size and sync_queue_size parameters)

* Changed a log from info->debug

* Changed a log from info->debug

* Updated default topic and sync queue_size inside nodes. Exposing topic and sync queue size params in warning when cannot synchronize. Added zed and depthai examples. Odom: Fixed imu callback group, added multi-threaded executors for all odometry nodes.

* fixed merge

* Include everything needed in example launch files for simple launch. Small fixes.

---------

Co-authored-by: Borong Yuan <yuanborong@hotmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants