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

Merger for clouds of several lidars #62

Open
ShepelIlya opened this issue Feb 21, 2023 · 3 comments
Open

Merger for clouds of several lidars #62

ShepelIlya opened this issue Feb 21, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@ShepelIlya
Copy link
Contributor

As i mentioned in this comment we use some other features for our work with ouster ros driver.
The main feature is os_cloud_merger_nodelet. This nodelet can merge clouds from several os_cloud_nodelets with standart ROS ApproximatePolicy Synchronizer. Also we can transform this cloud to preferred frame and use box filter on it. We use it on our robot with 2 ouster sensors on it, may be other users with multi-lidars setup need something like this

I can make a PR if you interested in this functionality.

@Samahu Samahu self-assigned this Feb 21, 2023
@Samahu Samahu added the enhancement New feature or request label Feb 21, 2023
@Samahu
Copy link
Contributor

Samahu commented Feb 21, 2023

That would be useful but I wouldn't be able to support with merge currently since I am occupied with ROS2 driver stability and optimization work, so it won't be until next quarter that I can take a look at this. I will keep this ticket open and we can circle back on it.

@stephen-derosa
Copy link

Curious if there has been any update on this - has time opened up for this ?

@Samahu
Copy link
Contributor

Samahu commented Aug 15, 2023

Nope, not yet. But thanks for asking as this helps us with planning for future releases.

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

3 participants