Skip to content

Use frame-id of EgoData message in getFrameId for EgoData - #23

Merged
lreiher merged 1 commit into
mainfrom
fix-ego-data-transform
Aug 26, 2026
Merged

Use frame-id of EgoData message in getFrameId for EgoData#23
lreiher merged 1 commit into
mainfrom
fix-ego-data-transform

Conversation

@gkueppers

@gkueppers gkueppers commented Aug 10, 2026

Copy link
Copy Markdown
Member

getFrameId and getTimestamp were previously implemented inconsistently, as we used the timestamp of the EgoData.header field but the frame_id from the state.header field.

In addition, an unset state.header in a message caused transform calls to fail.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

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 aligns tf2::getFrameId(const EgoData&) with tf2::getTimestamp(const EgoData&) by consistently using the top-level EgoData.header fields, and avoids failures when ego.state.header is unset during tf2 transform operations.

Changes:

  • Update getFrameId(const EgoData&) to return ego.header.frame_id instead of ego.state.header.frame_id.
  • Removes dependency on ego.state.header being populated for frame resolution.

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

@lreiher
lreiher merged commit 960be51 into main Aug 26, 2026
9 checks passed
@lreiher
lreiher deleted the fix-ego-data-transform branch August 26, 2026 12:53
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.

3 participants