Skip to content

Publish aligned ToF output on v3 jazzy - #787

Open
jakaskerl wants to merge 1 commit into
develop-oldfrom
patch-tof-aligned-v3-jazzy
Open

Publish aligned ToF output on v3 jazzy#787
jakaskerl wants to merge 1 commit into
develop-oldfrom
patch-tof-aligned-v3-jazzy

Conversation

@jakaskerl

Copy link
Copy Markdown
Contributor

Overview

Author:

Issue

Issue link (if present):
Issue description:
Related PRs

Changes

ROS distro:
List of changes:

Testing

Hardware used:
Depthai library version:

Visuals from testing

Add screenshots/gifs/videos from RVIZ or other visualizers demonstrating the effect of the changes when applicable.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the ToF sensor node publishing path so that, when alignment is enabled, the published ToF image stream and associated metadata (frame/socket, dimensions) correspond to the aligned output rather than the raw ToF depth output.

Changes:

  • Delay setInOut() until after optional ImageAlign node creation so aligned publishing can be wired correctly.
  • Publish alignNode->outputAligned instead of tofNode->depth when i_aligned is enabled.
  • Configure the publisher’s socket/frame and width/height based on the alignment target.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +68 to +76
auto pubSocket = aligned ? getAlignedSocketID() : boardSocket;
auto tfPrefix = getOpticalFrameName(getSocketName(pubSocket));
auto pubWidth = ph->getParam<int>(ParamNames::WIDTH);
auto pubHeight = ph->getParam<int>(ParamNames::HEIGHT);
if(aligned) {
auto alignedSocketName = getSocketName(pubSocket);
pubWidth = ph->getOtherNodeParam<int>(alignedSocketName, ParamNames::WIDTH);
pubHeight = ph->getOtherNodeParam<int>(alignedSocketName, ParamNames::HEIGHT);
}
@asahtik
asahtik changed the base branch from v3_jazzy to develop-old August 17, 2026 05:40
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