Revision history [back]

I concede that integration with move_base wasn´t a top priority with hector_exploration. There currently is no code to directly write out a generated target pose, but you can just take the last pose in the generated nav_msgs/Path message and forward that to move_base. The nice thing about the way hector_exploration works is that along with the generated exploration pose, it also produces a path to it. This is pretty hard to leverage with the way move_base works, however.