Open IIIIllllIllI opened 1 month ago
The velodyne_points in the mapping should work if you change them to the ouster point topic and also change the frame ID of velodyne in tf to the frame ID of the ouster point topic.
Thank you for your answer. Now, I can use your package. However, I have two more questions.
When I launched this package and played the bag file, I couldn't see the /modified_path and /modified_map. When I echoed the topics, no information came out. I think there might be an issue with the graph-based-slam node.
I didn't change any parameters without ndt_num_threads. I changed ndt_num_threads to 4. While it works well in simple environments, it doesn't perform as expected in more complex environments. How can I adjust the parameters in this situation.
This is the result of driving with cones placed on both sides.
It is the result of driving around a building.
Graph-based SLAM will not publish trajectories and maps unless a loop closure is performed or you execute "ros2 service call /map_save std_srvs/Empty". If a loop closure is not performed, please execute "ros2 service call /map_save std_srvs/Empty".
The point cloud map in the image does not seem to have any obvious problems, but what is the issue?
Generally, you need to adjust parameters such as ndt_resolution and vg_size_for_input depending on whether the environment is indoors or outdoors.
Thanks, I understand the problem.
I'm ros2 noob. I use ouster lidar for slam. I want to know what I have to change to use this package.