The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
It means that your pc is attempting to update the map every 0.2 seconds (5 Hz), but it's actually taking 10x as long. This means you're likely saturating your system's processing capability, and need to reduce the load somewhere.
From a practical point of view, it means that the costmap will have a 2 second delay before it contains data representing the latest sensor information.
| | 2 | No.2 Revision |
It means that your pc is attempting to update the map every 0.2 seconds (5 Hz), but it's actually taking 10x as long. This means you're likely saturating your system's processing capability, and need to reduce the load somewhere.
From a practical point of view, it means that the costmap will have a 2 second delay before it contains data representing the latest sensor information.
To prevent the error, you can go into the costmap's parameters, and reduce the update rate to something smaller.
| | 3 | No.3 Revision |
It means that your pc is attempting to update the map every 0.2 seconds (5 Hz), but it's actually taking 10x as long. This means you're likely saturating your system's processing capability, and need to reduce the load somewhere.
From a practical point of view, it means that the costmap will have a 2 second delay before it contains data representing the latest sensor information.
To prevent the error, warning, you can go into the costmap's parameters, and reduce the update rate to something smaller.
| | 4 | No.4 Revision |
It means that your pc is attempting to update the map every 0.2 seconds (5 Hz), but it's actually taking 10x as long. This means you're likely saturating your system's processing capability, and need to reduce the load somewhere.somewhere. The load could be coming from the costmap itself, from other costly operations such as SLAM, or just a limitation in your hardware.
From a practical point of view, it means that the costmap will have a 2 second delay before it contains data representing the latest sensor information.
To prevent the warning, you can go into the costmap's parameters, and reduce the update rate to something smaller.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
