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

Improve tf handling and support multiple disconnected tf trees #2

Open
roym899 opened this issue Apr 27, 2024 · 0 comments
Open

Improve tf handling and support multiple disconnected tf trees #2

roym899 opened this issue Apr 27, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@roym899
Copy link
Collaborator

roym899 commented Apr 27, 2024

Currently only one fully-connected tf tree is supported.

The tree parameter should be renamed to "trees" and optionally support multiple disconnected trees. These should be logged to tf/root1, tf/root2, etc. and marked as disconnected in Rerun.

The root for a given frame could be automatically resolved and the data logged to an entity path such as tf/root1/flattened-topic-name (this might require some mangling to avoid possible name clashes, e.g., odom might be a topic and an entity path following a root). There should be an option to disable the fixed frame behavior in which case the data would be logged into the tree as tf/root1/.../frame_of_data/flattened-topic-name.

Data without a frame, or a frame missing from the predefined tf tree should be logged separately to flattened-topic-name (or possibly to tf/frame_of_data/flattened-topic-name) and also be marked as disconnected.

@roym899 roym899 added the enhancement New feature or request label May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant