You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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!
The text was updated successfully, but these errors were encountered: