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

Wrong Lidar Point Height when Tilt Angle is Non-Zero. #37

Open
DavidMansolino opened this issue Dec 7, 2018 · 4 comments
Open

Wrong Lidar Point Height when Tilt Angle is Non-Zero. #37

DavidMansolino opened this issue Dec 7, 2018 · 4 comments
Labels
bug Something isn't working
Milestone

Comments

@DavidMansolino
Copy link
Member

DavidMansolino commented Dec 7, 2018

Describe the Bug
When the tilt angle of a lidar is not 0, it may happen that the lidar points are 'too high'.

Steps to Reproduce

  1. Can easily be reproduce with the Velodyne HLD64 and a flat ground.
  2. Or with this world: test0.zip

Expected behavior
The lidar point should all be at the same height than the floor.

Screenshots
lidar

System
System: Windows 10 64-bit
Processor: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Number of cores: 4
OpenGL vendor: NVIDIA Corporation (0x10de)
OpenGL renderer: GeForce GTX 970/PCIe/SSE2 (0x13c2)
OpenGL version: 4.6.0 NVIDIA 416.94

@DavidMansolino DavidMansolino added the bug Something isn't working label Dec 7, 2018
@DavidMansolino DavidMansolino added this to the R2019a milestone Dec 7, 2018
@DavidMansolino DavidMansolino self-assigned this Dec 7, 2018
@DavidMansolino
Copy link
Member Author

Without tilt angle:
lidar_2

With a title angle of -0.2:
lidar_1

@DavidMansolino
Copy link
Member Author

The bug is present only for spherical cameras.

@DavidMansolino
Copy link
Member Author

I found the exact reason, the problem is at the merge_spherical shader level.
Indeed because of the spherical deformation, the wrong vertical pixel is selected, in case of lidars we should perform the deformation only horizontally but not vertically.

@DavidMansolino
Copy link
Member Author

DavidMansolino commented Dec 11, 2018

Tilting the camera doesn't seem to be a good idea, in case of spherical camera, it is really a mess if the cameras are tilted (sub-cameras border don't coincide anymore).
Instead of tilting the sub-cameras, it seems safer to create a bigger field of view and use only the interesting part (so that the orientation of all the sub-cameras is conserved), but this will require some re-factorization.

@DavidMansolino DavidMansolino modified the milestones: R2019a, R2019a.rev1 Dec 13, 2018
@DavidMansolino DavidMansolino modified the milestones: R2019a.rev1, R2019b Feb 4, 2019
@DavidMansolino DavidMansolino modified the milestones: R2019b, R2020a May 27, 2019
@DavidMansolino DavidMansolino modified the milestones: R2020a, R2020b Dec 2, 2019
@DavidMansolino DavidMansolino modified the milestones: R2020b, R2021a Apr 27, 2020
@omichel omichel modified the milestones: R2021a, R2021a.rev1 Nov 30, 2020
medrimonia added a commit to medrimonia/webots that referenced this issue Apr 19, 2021
@stefaniapedrazzi stefaniapedrazzi modified the milestones: R2021a.rev1, R2021b.rev1 May 26, 2021
@omichel omichel modified the milestones: R2021b-rev1, R2021c-rev1 May 26, 2021
@omichel omichel modified the milestones: R2022a-rev1, R2022b Jun 13, 2022
@omichel omichel removed this from the R2022b milestone Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

5 participants