-
Notifications
You must be signed in to change notification settings - Fork 104
VLP-16 horizontal resolution and rate on submitted models #753
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
Conversation
…nsor. Removed a handful of unnecessary comments from other model.sdfs as it pertains to the 160,000 ray limit.
Build finished. 15 tests run, 0 skipped, 0 failed. |
As pointed out in #691, shouldn't this also affect the default X1-X4 robots? |
https://bitbucket.org/ignitionrobotics/ign-sensors/issues/8 --> | ||
<samples>10000</samples> | ||
<samples>1800</samples> | ||
<resolution>0.1</resolution> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest increasing horizontal resolution to 1 as well. Otherwise I guess accuracy could become far inferior to physical sensor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest increasing horizontal resolution to 1 as well. Otherwise I guess accuracy could become far inferior to physical sensor.
I agree that the parameter should be 1.0 however whenever I experimentally tested the impact of changing resolution
I could not find any difference between. This could be indicative of a larger problem with horizontal LIDAR ray resolution.
Experimentally I tested values of 1.0, 0.1, and 0.01 in the resolution
parameter for horizontal returns without luck.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably you are right. May be gpu ray sensor doesn't even use that parameter. (Just a thought need to check code to confirm) Or the way we think what that parameter is for, is incorrect.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does not currently factor in that parameter. I'm looking into the issue a bit more before submitting an issue on the Ignition repositories.
As @peci1 pointed out models of default X1-X4 robots would also need update. But I guess they are in a private repo. |
The X1-X4 vehicles are version controlled through Ignition fuel as opposed to through this repository. A separate request has been put in to update those models directly on Ignition fuel. |
The models on Fuel have been updated. |
These changes only apply to models in the
submitted_models
folder.I tested all changes to LIDAR parameters by checking the
points
topic withrostopic echo <topic_name> --noarr
and visual inspection in RViz.