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

Bring back optional publishing of lidar and imu packets to new single nodelet driver #251

Open
skohlbr opened this issue Nov 8, 2023 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@skohlbr
Copy link

skohlbr commented Nov 8, 2023

Is your feature request related to a problem? Please describe.
We recently upgraded to use the new single nodelet driver (started via driver.launch as described in https://github.com/ouster-lidar/ouster-ros#sensor-mode ). This shows significantly reduced CPU consumption on Jetson embedded systems compared to the "old" multi-nodelet setup. However, it appears the support to simultaneously publish the lidar and imu packets has been dropped. This is a problem because for data recording purposes, those are the most useful data to record (as also remarked by others in #110 ).

Describe the solution you'd like
It would be great to have the single driver nodelet also optionally (i.e. if numSubscribers() > 0 ) publish the raw packets, so they can be recorded for later postprocessing/analysis.

Describe alternatives you've considered
An alternative is using the old multi-nodelet setup, but that one causes high CPU load on Jetson embedded systems, so not a good option.

Targeted Platform (please complete the following information only if applicable, otherwise dot N/A):

  • ROS1, but likely applies to ROS2 also (?)
@skohlbr skohlbr added the enhancement New feature or request label Nov 8, 2023
@Samahu Samahu self-assigned this Nov 8, 2023
@Samahu
Copy link
Contributor

Samahu commented Nov 8, 2023

Same as #238

@skohlbr
Copy link
Author

skohlbr commented Feb 20, 2024

@Samahu can you provide an indication if this is in the works or what the plans are wrt this feature?

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

2 participants