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

High CPU Usage with navsat_transform Node in ROS 2 Jazzy #890

Open
porizou opened this issue Jun 22, 2024 · 4 comments
Open

High CPU Usage with navsat_transform Node in ROS 2 Jazzy #890

porizou opened this issue Jun 22, 2024 · 4 comments

Comments

@porizou
Copy link

porizou commented Jun 22, 2024

I am experiencing an issue where the navsat_transform node in ROS 2 Jazzy consistently causes the CPU usage to exceed 100%. This occurs during normal operation and significantly impacts system performance. Here are the details of my setup:

System Information:

  • OS: Ubuntu 24.04LTS
  • ROS 2 : Jazzy
  • navsat_transform package version: 3.8.0

parameter of navsat_transform_node

navsat_transform_node:
  ros__parameters:
    frequency: 10.0
    delay: 3.0
    yaw_offset: 1.57
    magnetic_declination_radians: 0.0
    zero_altitude: true
    broadcast_utm_transform: false
    publish_filtered_gps: false
    use_odometry_yaw: false
    wait_for_datum: false

image

@ayrton04
Copy link
Collaborator

Thanks for the report. Is this with no messages publishing from any other nodes, i.e., you are just running this in isolation?

@porizou
Copy link
Author

porizou commented Jul 1, 2024

Thank you for your response. Here are some additional details regarding my setup:

  • I am running the navsat_transform_node in combination with the ukf_node.
  • The GPS NavSatFix topic is being obtained from Gazebo Sim through the gz_bridge.
  • When I run only the navsat_transform_node using the command "ros2 run robot_localization navsat_transform_node", the CPU usage does not reach 100%.

This is rqt_graph.
CPU usage of navsat_transform is at 100%, but the node itself is functioning normally.

image

@ayrton04
Copy link
Collaborator

If you could provide a full config and bag file (i.e., everything I'd need to replicate the issue), that would be helpful, thank you.

@porizou
Copy link
Author

porizou commented Sep 18, 2024

Hi,
The default value of transform_timeout was 0.0, so setting a value other than 0.0 solved the problem.

navsat_transform_node:
  ros__parameters:
    frequency: 5.0
    delay: 3.0
    yaw_offset: 0.0
    magnetic_declination_radians: 0.0
    zero_altitude: true
    broadcast_utm_transform: false
    publish_filtered_gps: false
    use_odometry_yaw: false
    wait_for_datum: false
    transform_timeout: 0.5

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