hdl_graph_slam icon indicating copy to clipboard operation
hdl_graph_slam copied to clipboard

Run Error : rostopic is un normal

Open why-freedom opened this issue 4 years ago • 0 comments

Environment:

Ubuntu 16.04 PCL 1.8 g2o(hdl-graph-slam)

run code:roslaunch hdl_graph_slam hdl_graph_slam_501.launch

Error??:

auto-starting new master process[master]: started with pid [28508] ROS_MASTER_URI=http://localhost:11311

setting /run_id to 300b76a8-a4c9-11ea-ae47-7085c2882345 process[rosout-1]: started with pid [28524] started core service [/rosout] process[lidar2base_publisher-2]: started with pid [28541] process[prefiltering_nodelet-3]: started with pid [28542] process[scan_matching_odometry_nodelet-4]: started with pid [28550] process[floor_detection_nodelet-5]: started with pid [28555] process[hdl_graph_slam_nodelet-6]: started with pid [28564] process[map2odom_publisher-7]: started with pid [28575]

rostopic list:(only)

/hdl_graph_slam/odom2pub /rosout /rosout_agg /tf

But When i Run in Docker,it is ok。

/clicked_point /clock /colored_points /filtered_points /floor_detection/floor_coeffs /floor_detection/floor_filtered_points /floor_detection/floor_points /floor_detection/read_until /gpsimu_driver/imu_data /hdl_graph_slam/map_points /hdl_graph_slam/markers /hdl_graph_slam/odom2pub /hdl_graph_slam/read_until /initialpose /move_base_simple/goal /odom /rosout /rosout_agg /scan_matching_odometry/read_until /scan_matching_odometry/transform /tf /tf_static /velodyne_nodelet_manager/bond /velodyne_points

why-freedom avatar Jun 02 '20 07:06 why-freedom