Prasad,
I routinely run with a map of size 4000x4000 pixels on an i7 920 with 6gb of RAM. I do have to set the publish_frequency to 0 and the update_frequency to 1 in order to avoid loop rate warnings for the global costmap. I've never actually seen the large costmap hang the system, just generate a lot of warnings.
Try setting the publish_frequency to 0 for the global costmap on a larger map. I've found that, because the voxel grid doesn't seem to track unknown space by default (or at all?), publishing the obstacles for the 4000x4000 map is intensive, as the majority of the map is marked as unknown and is published as an obstacle. Perhaps Eitan has some ideas about the unknown space being published as an obstacle with voxel grids and how to avoid that?
- Eric
On Mon, Sep 20, 2010 at 1:26 AM, Prasad Dixit
<abhimohpra@gmail.com> wrote:
The above issue was solved after changing a map with size and resolution from
4000 X 4000 (at 0.0500) to 200 X 200 (at 0.1)
That means it works seamlessly in my case with small maps but larger map is
slows down and finally hangs the system.
Am is suppose to upgrade my hardware? or is there any setting to make map
compatible with the navigation stack?
--
View this message in context: http://ros-users.122217.n3.nabble.com/Navigation-stack-not-working-tp1519053p1527160.html