Skip to content

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

Merged
matlabbe merged 1 commit intointrolab:masterfrom
borongyuan:master
Sep 2, 2024
Merged

Fixed node ID=0 issues as msgs may not have seq.#1202
matlabbe merged 1 commit intointrolab:masterfrom
borongyuan:master

Conversation

@borongyuan
Copy link
Copy Markdown
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
Copy Markdown
Member

matlabbe commented Sep 2, 2024

Great, thanks!

@matlabbe matlabbe merged commit 3eb0b47 into introlab:master Sep 2, 2024
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