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

Run ct_icp on Jetson Nano #53

Open
Cristian-wp opened this issue Nov 14, 2022 · 3 comments
Open

Run ct_icp on Jetson Nano #53

Cristian-wp opened this issue Nov 14, 2022 · 3 comments

Comments

@Cristian-wp
Copy link

Hello, I would like to run this slam on my Jetson Nano 4Gb.
I have manage to install and build on it, but even if I use Ceres as solver, I can not manage to run the solver on the board GPU.
I know that only some type of Ceres option are currently supperted by CUDA:

"CUDA If you have an NVIDIA GPU then Ceres Solver can use it accelerate the solution of the Gauss-Newton linear systems using the CMake flag USE_CUDA. Currently this support is limited to using the dense linear solvers that ship with CUDA. As a result GPU acceleration can be used to speed up DENSE_QR, DENSE_NORMAL_CHOLESKY and DENSE_SCHUR. This also enables CUDA mixed precision solves for DENSE_NORMAL_CHOLESKY and DENSE_SCHUR. Optional."

So, I would like to know which dense linear solver have you use.

@pdell-kitware
Copy link
Collaborator

Hello,

So we use the default Ceres solver (which should be DENSE_QR).
To be honest, I doubt that this will speedup significantly the process, as the linear system solved if of small size (6 or 12 parameters, thus the matrix to invert is of size up to 12x12).

What is costly in our method is the construction of the neighborhoods (and the point associations),
As well as the evaluation of the residuals, rather than solving the Linear Problem.

@Cristian-wp
Copy link
Author

Hello @pdell-kitware thank you for your answer.
In fact I have notice that even on my Deskot PC the slam is a little slow to give the correct output, but in my dataset on a straight path of 250m inside a raillway tunnel it gives 20m of error that is a really good result in this type of test field (concrete flat walls, no signal, no marker,ecc...).

When you run it on a real hardware (in my case is an Ouster OS0-1) do you subsample the pointcloud to speed up?

Another thing, I have see that I can use GTSAM or CERES as solver, based on your experience which is the best in term of solving speed?

Is mandatory to use DENSE_QR as solver or I can try with DENSE_NORMAL_CHOLESKY and DENSE_SCHUR?

Last thing, I am doing these experiments because I wish to run your slam on a drone inside tunnels to make a 3D reconstruction. Have you ever test the slam performance on a real hardware with real sensors(even not on a derone)? For example I am planning to run the slam on the jetsnon and all the other thing on an i7 intel nuc. Do you think is a good choiche?

@Cristian-wp
Copy link
Author

What do you suggest to speed up the lidar odometry?

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