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

Origin of Laserscan is different from lidar position #582

Closed
3 tasks done
taikitanaka3 opened this issue Mar 25, 2022 · 1 comment
Closed
3 tasks done

Origin of Laserscan is different from lidar position #582

taikitanaka3 opened this issue Mar 25, 2022 · 1 comment

Comments

@taikitanaka3
Copy link
Contributor

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I've agreed with the maintainers that I can plan this task.

Description

currently origin of laser scan is baselink but it's origin should be a position of lidar

Purpose

consider origin of lidar position and fusion laserscans for each if multilidar is available

Possible approaches

  • multi view occupancy grid
  • something else

Definition of done

implement to improve laser scan

@taikitanaka3 taikitanaka3 changed the title Origin of Laserscan Origin of Laserscan is different from lidar position Mar 25, 2022
@taikitanaka3
Copy link
Contributor Author

this issue is solved by #624

asana17 pushed a commit to asana17/autoware.universe that referenced this issue Jul 26, 2023
iwatake2222 pushed a commit to iwatake2222/autoware.universe that referenced this issue Jan 17, 2025
Kazunori-Nakajima pushed a commit to Kazunori-Nakajima/autoware.universe that referenced this issue Feb 6, 2025
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

No branches or pull requests

1 participant