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

Usage without prior ego-motion estimate #11

Open
Pallav1299 opened this issue Jan 19, 2024 · 0 comments
Open

Usage without prior ego-motion estimate #11

Pallav1299 opened this issue Jan 19, 2024 · 0 comments

Comments

@Pallav1299
Copy link

Hi, @HuajieWu99 @XW-HKU @Ecstasy-EC. Kudos for the great work.

Supplementary Information document states that:

For input, M-detector accepts either an individual point or a frame of
points, with the sensor ego-motion compensated in advance. The result of ego-
motion compensation can be provided by a LiDAR-based odometry or a full
Simultaneous localization and mapping (SLAM) system.
  • If that is the case, won't the ego-motion estimate from LiDAR-based odometry/SLAM be untrustworthy due to dynamic objects in the raw pointcloud data?
  • What's the impact of additional uncertainity in position estimate from LiDAR-based odometry/SLAM due to dynamic events on M-detector's performance?
  • Can we use M-detector without prior ego motion information(e.g. from FAST_LIO)? Or, Use it as a preprocessing module which removes dynamic events from the pointcloud given to LiDAR-based odometry/SLAM?
  • Is robust localization also a use case? Or, mapping only?
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