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

Investigate adding an optional tile mapper to the capturer #195

Open
jackjansen opened this issue Oct 30, 2024 · 1 comment
Open

Investigate adding an optional tile mapper to the capturer #195

jackjansen opened this issue Oct 30, 2024 · 1 comment
Assignees

Comments

@jackjansen
Copy link
Collaborator

Right now, with 4 cameras we get 15 tiles. That's overkill, as most will be empty. It's better to have 9 tiles (8 compass directions, and one "other" that combines the rest of the tiles).

The "other" tile could have a direction of "up" or "down" that should work fine with the selection algorithm.

Linked to https://github.com/jvdrhoof/mmsys_2025/issues/19

@jackjansen jackjansen self-assigned this Oct 30, 2024
@jackjansen
Copy link
Collaborator Author

Integrating the tilemapper turns out to be more work, because we have to recompute the new tileconfig and this is not trivial.

Also, it should ideally be done at the source, so in the native code and when we create the tiled point clouds (so we don't pay an extra performance penalty).

Leaving this for now.

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

No branches or pull requests

1 participant