Ussama Naal

@JonasTietz thanks for the feedback, will keep the ticket open untill we have the issue fully resolved.

@Imaniac230 thanks for your detailed report, this very helpful. When porting the ROS1 driver to ROS2 and implementing the combined node I haven't tested its behavior with multiple subscribers at...

Thanks all for the valuable feedback, I have identified the problem and will be working on a fix soon. The issue stems when the buffer read operation takes more time...

Hi @Imaniac230, sorry I was busy with other tasks. I am taking a look today.

@Imaniac230 I am still evaluating your contribution, given the complexity of your solution I need a little more time before committing. Please note that I have been working on a...

@Imaniac230 I would say this PR no longer relevant since the package has progressed. We do have some follow up work to improve our packet buffering and scan batching planned....

We don't expose the ability to set azimuth window via ros launch file. We have `/ouster/set_config/` (described [here](https://github.com/ouster-lidar/ouster-ros#setconfig-experimental) which could be used for this purpose but due to sensor re-initialization...

Sure, create a config file in some known path and add the following content: ```json { "azimuth_window": [ 0, 180000 ], } ``` This config would set the azimuth window...

It will affect both simultaneously

addressed in #357 and #358