Skip to content

Gpu lidar fix#165

Merged
jonyMarino merged 1 commit into
mainfrom
fix/gpu_lidar
Jun 29, 2026
Merged

Gpu lidar fix#165
jonyMarino merged 1 commit into
mainfrom
fix/gpu_lidar

Conversation

@jonyMarino

Copy link
Copy Markdown
Contributor

Overview

This PR fixes a lidar bug related to data mapping into space coordinates.

Modifications

  • Modified lidar parameters of robot_quadrotor_fastphysics_lidar.jsonc for testing purposes
  • Implemented LidarTopDownRenderer to visualize lidar scans in ubuntu
  • Added cameras for testing in jsonc files

Shader/GPU modifications

  • Fixed GPU shader horizontal-angle convention mismatch
  • Fixed GPU shader angle mapping mismatch
  • Deprojection is no longer cam-1-centric
  • Fixed async readback/pose mismatch
  • Fixed partial FOV normalization

Before this PR

output_gpu.webm

After this PR

latest_gpu-ezgif com-crop

* Added lidardisplay for ubuntu

* organize test files

* use cylindrical gpu for test

* Match GPU lidar conventions to CPU lidar conventions

* GPU shader no longer uses the cam-1 inverse deprojection path for points

* GPU lidar readback metadata alignment. This avoids publishing stale point data with the current tick’s pose.

* gpu_cylindrical now uses the configured vertical FOV lower/upper bounds instead of assuming symmetry around zero.

* GPU lidar: replace the projection-to-pixel step with explicit perspective math.

* Fix partial FOV normalization issue in GPU lidar

* GPU lidar guard threads beyond the actual point count

* GPU lidar order ok, fixed from renderer not from lidar code

* Gpu lidar working 100%
@jonyMarino
jonyMarino merged commit fa82cd7 into main Jun 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants