Ask Your Question
0

Why is the default update rate for costmap2d only 5Hz, not the sensor rate?

asked 2015-09-17 08:45:59 -0600

ingo gravatar image

The default costmap configuration in the ROS navigation stack updates the costmap every 200ms (at 5Hz). I wonder why it is not updated at the sensor's rate, or at least at the local planners rate (which is 10Hz by default). Wouldn't this make the robot react faster to new obstacles?

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
2

answered 2015-09-19 11:54:21 -0600

David Lu gravatar image

It's a tradeoff of reaction time and amount of work. The time required to update the costmap does not scale exactly linearly with the amount of sensor data. Updating more frequently involves overhead. You are free to configure it to be faster.

edit flag offensive delete link more

Comments

I guessed it is to reduce work, but I've been wondering about this particular number. Did anybody do experiments and/or optimizations to arrive at the figure of 5Hz, or is it just a number chosen from experience?

ingo gravatar imageingo ( 2015-09-21 01:51:45 -0600 )edit

The general rule for the nav stack is that the decisions were made to fit the PR2.

David Lu gravatar imageDavid Lu ( 2015-09-21 07:38:59 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

2 followers

Stats

Asked: 2015-09-17 08:45:59 -0600

Seen: 134 times

Last updated: Sep 19 '15