-
Notifications
You must be signed in to change notification settings - Fork 29
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
what is this situation #30
Comments
I'm using ros2 humble to simulate with gazebo for 2D radar navigation, why is this happening? |
@panyu3258221348 |
Here's my emulation gazebo urdf file Gazebo/Black / cmd_vel:=cmd_vel odom:=odom 30 left_wheel_joint right_wheel_joint 0.2 0.065 20 1.0 true true false odom base_link
|
This is my topic list hell0@hell0-virtual-machine:~/161/fishbot$ ros2 topic list |
Can you try setting the export SIMULATION=true && ros2 launch kinematic_icp online_node.launch.py lidar_topic:=/scan use_2d_lidar:=true or ros2 launch kinematic_icp online_node.launch.py lidar_topic:=/scan use_2d_lidar:=true use_sim_time:=True |
hell0@hell0-virtual-machine:~/161/fishbot$ ros2 launch kinematic_icp online_node.launch.py lidar_topic:=/scan use_2d_lidar:=true
[INFO] [launch]: All log files can be found below /home/hell0/.ros/log/2025-02-09-20-43-22-631226-hell0-virtual-machine-252066
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [kinematic_icp_online_node-1]: process started with pid [252067]
[kinematic_icp_online_node-1] [INFO] [1739105003.112531058] [kinematic_icp.online_node]: Started in 2D scanner mode with topic: /scan
[kinematic_icp_online_node-1] [INFO] [1739105003.137092286] [kinematic_icp.online_node]: Resetting KISS-ICP pose:
[kinematic_icp_online_node-1] 0.866602 -0.499001 1.44286e-05 0.287426
[kinematic_icp_online_node-1] 0.499001 0.866602 8.11212e-06 0.0993854
[kinematic_icp_online_node-1] -1.65518e-05 1.69914e-07 1 0.168
[kinematic_icp_online_node-1] 0 0 0 1
[kinematic_icp_online_node-1]
[kinematic_icp_online_node-1] [INFO] [1739105003.137198444] [kinematic_icp.online_node]: KISS-ICP ROS 2 odometry node initialized
[kinematic_icp_online_node-1] [WARN] [1739105003.137306791] [LookupTransform]: Lookup would require extrapolation at time 195.777000, but only time 195.753000 is in the buffer, when looking up transform from frame [base_footprint] to frame [odom]
[kinematic_icp_online_node-1] [WARN] [1739105003.351345230] [LookupTransform]: Lookup would require extrapolation into the future. Requested time 195.978000 but the latest data is at time 195.957000, when looking up transform from frame [base_footprint] to frame [odom]
[kinematic_icp_online_node-1] [WARN] [1739105003.557530673] [LookupTransform]: Lookup would require extrapolation into the future. Requested time 196.177000 but the latest data is at time 196.161000, when looking up transform from frame [base_footprint] to frame [odom]
[kinematic_icp_online_node-1] [WARN] [1739105003.752530894] [LookupTransform]: Lookup would require extrapolation into the future. Requested time 196.378000 but the latest data is at time 196.365000, when looking up transform from frame [base_footprint] to frame [odom]
[kinematic_icp_online_node-1] [WARN] [1739105003.953703921] [LookupTransform]: Lookup would require extrapolation into the future. Requested time 196.577000 but the latest data is at time 196.569000, when looking up transform from frame [base_footprint] to frame [odom]
[kinematic_icp_online_node-1] [WARN] [1739105004.146684940] [LookupTransform]: Lookup would require extrapolation into the future. Requested time 196.777000 but the latest data is at time 196.773000, when looking up transform from frame [base_footprint] to frame [odom]
[ERROR] [kinematic_icp_online_node-1]: process has died [pid 252067, exit code -6, cmd '/home/hell0/161/fishbot/install/kinematic_icp/lib/kinematic_icp/kinematic_icp_online_node --ros-args -r __node:=online_node -r __ns:=/kinematic_icp --params-file /home/hell0/161/fishbot/install/kinematic_icp/share/kinematic_icp/config/kinematic_icp_ros.yaml --params-file /tmp/launch_params_l5f3eyxa -r lidar_odometry:=lidar_odometry'].
The text was updated successfully, but these errors were encountered: