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

Ambiguity regarding AVIA/MID360 config and preprocessing #379

Open
JoLichtenfeld opened this issue Jan 5, 2025 · 0 comments
Open

Ambiguity regarding AVIA/MID360 config and preprocessing #379

JoLichtenfeld opened this issue Jan 5, 2025 · 0 comments

Comments

@JoLichtenfeld
Copy link

Hi, thanks you so much for this very useful implementation.

I use it mostly for our Livox MID360 lidars. However, I am somewhat confused about the names of the config file.
In mid360.yaml, the lidar type is set to "1 for Livox serials LiDAR" which translates to LID_TYPE=AVIA here. Maybe it would make more sense to rename this to LIVOX since it applies to all Livox serial LiDARs?
Then also here I see that the enum LID_TYPE has an element MID360. This in return refers to the mid360_handler in preprocessing.cpp which takes a PointCloud2 as input and assumes that no timestamps are given.

So what is the recommended way to use FAST-LIO with a MID360? To select lidar_type=1? In which case would one use lidar_type=4?

Thank you!

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