Replies: 2 comments
-
@tomy983 thanks for the issue report - could you share a bag file that will help us reproduce this issue. If you'd like to share privately you can email directly or DM me in slack. |
Beta Was this translation helpful? Give feedback.
0 replies
-
@defunctzombie from this sentence I get the impression that costmap updates are indeed supported in Foxglove? I can't find any documentation about it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
In 3D and 3D beta panels, while visualizing move_base costmap 2D
/move_base/local_costmap/costmap
the uptades are very slow (0.02Hz). This is probably because Studio does not also subscribe to/move_base/local_costmap/costmap_updates
.Confronting Studio with RVIZ, in both adding the costmap to the scene is very similar, but rviz (without notice) also subscribe to the
/move_base/local_costmap/costmap_updates
topic and most certainly uses also this topic to update the costmap on the screen as i can see usingrosnode info move_base
Steps To Reproduce
add costmap to the 3d scene in rviz and studio.
Current Experience
In Rviz the map updates are loaded into the costmap view. In studio the costmap is not updated unless a new map is received.
Desired Experience
The costmap in the 3D panel should take in considarition the updates coming from
/move_base/local_costmap/costmap_updates
of type map_msgs/OccupancyGridUpdate(same thing for global costmap..)
Beta Was this translation helpful? Give feedback.
All reactions