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

Parallelising LIO-mapping #58

Open
lsdta opened this issue Feb 13, 2020 · 1 comment
Open

Parallelising LIO-mapping #58

lsdta opened this issue Feb 13, 2020 · 1 comment

Comments

@lsdta
Copy link

lsdta commented Feb 13, 2020

Hi @hyye ,

Have you attempted to parallelise your mapping algorithm at all? I see you have linked to nvidia-docker so I imagine you have run this on the jetson TX2 or similar? Is there any reason why a GPU board is useful, or have you found that SLAM is inherently mostly sequential? (and thus CPU-dominant).

It seems that SLAM can be improved with a GPU, but by the looks of your code the GPU is only utilised for the visualisation?

Any ideas appreciated, I am planning on running this on an embedded board but not sure if it is worth utilising a GPU-accelerated board or not.

@hyye
Copy link
Owner

hyye commented Jun 19, 2020

Hi @lsdta, I think GPU can be utilized in some parts of the SLAM algorithms, like correspondence finding, residual calculation, etc., where operations are the same for each point. But meanwhile, some other data structures/algorithms may require changes.

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

2 participants