koide3
@saimanoj18 I'm not sure, but I guess some SSE-related optimizations in Eigen causes this problem. This seems do not happen on every PC since in my PC (and my colleagues'...
@saimanoj18 @chrisy-d1989 Let me make it sure that you tried indigo on docker, right?
Hi @ASE-HHN , Regarding the first issue, an easy solution is to create a small problem to filter out unnecessary points. Using lidar_to_pointcloud is also a good option. If you...
@QiukuZ You can use the dump service to save the mapping result in the format that interactive_slam can read. https://github.com/koide3/hdl_graph_slam#services
Hi @Jiaminchen0 , Are you using pcl-ros package? Self-built pcl sometimes causes this kind of launch failures.
This package does 3D mapping and maybe not suitable for 2D mapping. I think slam_toolbox [slam_toolbox](https://github.com/SteveMacenski/slam_toolbox) would meet your purpose.
Maybe it's dependency of PCL. If you are using ubuntu, can you try the default apt binary?
Could you check if the prefiltering nodelet is connected with the points topic using rqt_graph?
Check the points topic name in your bag and remap "/velodyne_points" of prefiltering_nodelet following "Use hdl_graph_slam in your system" in README.
Hi @arixrobotics , You may want to change the following params: - "prefiltering_nodelet/downsample_resolution" (In case resolution < 0.1, use APPROX_VOXELGRID instead of VOXELGRID) - "hdl_graph_slam_nodelet/keyframe_delta_trans" (By making the keyframe interval...