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

comparison to rf2o_laser_odometry #7

Open
robvoi opened this issue Mar 9, 2022 · 4 comments
Open

comparison to rf2o_laser_odometry #7

robvoi opened this issue Mar 9, 2022 · 4 comments

Comments

@robvoi
Copy link

robvoi commented Mar 9, 2022

Everything works now. :-)
One last question. How does thelaser_scan_match/csm compare to rf2o_laser_odometry?

I have both runnig (ROS2 fork of rf2o_laser_odometry). I wonder which one to use. Both deliver good results in my first tests.

@AlexKaravaev
Copy link
Owner

I haven't tested rf2o_laser_odometry yet, but it will be very great, if you will provide findings of the comparison here

@robvoi
Copy link
Author

robvoi commented Mar 10, 2022

From my testing yesterday, both solutions perform similar in regards to results.
rf2o uses 9% less CPU.

Still only basic testing done. No real mapping runs or anything. I’ll update as I continue testing.

@AlexKaravaev
Copy link
Owner

Have you tried to compile with the flag Release?

colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release

I haven't optimized this code of laser_scan_matcher yet, but it can be that the flag can help significantly with reducing CPU load

@robvoi
Copy link
Author

robvoi commented Mar 12, 2022

It indeed seems to have saved some % of CPU. Didn't know this argument exists. Learned something. Thanks.
I am recompiling all other nodes now. :-)

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