Add support for Velodyne Velarray M1600 #483
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've implemented support for the Velodyne velarray M1600, solid-state LiDAR by modifying the imageProjection.cpp and utility.h files. This pull request aims to integrate the functionality necessary for utilizing the Velarray M1600 within the existing framework.
For testing purposes, I've utilized a dataset, which includes data from a Velodyne Velarray M1600 and a 6-axis IMU, but it should work in a 9-axis-imu!
In the testing configuration, the following values were utilized:
params_m1600.txt
For the Horizon_SCAN, i consider 3077 points.
Results Snapshot:
This image showcases some of the results obtained through the integration of the Velodyne Velarray M1600.