Closed ghost closed 3 months ago
Hi @AJsamk
I answered your related issue on RGL repository.
This will be solved in the future (at the earliest in June).
@AJsamk considering the feature was added, are we ok to close the task?
Hi @adamdbrw , can you point me to the PR/commit that adds the feature please? I have added with a lot of changes on my fork but would like to see if I can use the upstream version.
@AJsamk @adamdbrw We have added an intensity feature to our native library in version 0.14.0. However, the integration with Gazebo Plugin still needs to be done.
I suppose we can close the task on the RGL repository, but this task is still open.
Had to change accounts, I am still active :)
The issue has already been resolved with https://github.com/RobotecAI/RGLGazeboPlugin/pull/34 Thank you @ajsampathk for your assistance in completing this feature :+1:
Feature request
The plugin only supplied the x,y and z fields to the message. Refer this line.
The resulting message fields look like this:
But for reference, the Gazebo GPU Lidar supplies the following fields,
The ring field might not be that necessary, but the intensity field is. And it does look like the field might be available in the API core.h.
I understand this might make filling the message data a little more complicated and inefficient, since this will mean doing a strided copy of the intensity field into the data array, which is not as elegant as using memcpy here, but the intensity field is an important features that many projects rely on.
I will be looking at verifying that the intensity field is in fact calculated and reliable in the API.
Please let me know your thoughts.