Assumes that there is a single topological navigation instance available at /topological_navigation when instantiating the go_to_node service.
When running multiple robots, a possible configuration is running the topo_nav_global to manage the map which the robots will use for navigation, but each one has its own topological_navigation instance to actually traverse the map. If visualise_map is run without the -e or -edit args, only the edge, marker and zone interactive markers will be available (i.e. the editable ones), and the non-editable lines and waypoint markers will not show up because goto.py will wait on the topological_navigation actionserver which will never become active.
Add an arg to launch files where visualise_map is being used so that the -edit arg can be added and skip the go_to_node service creation.
This would also require a separate go_to_node script so that the service can be started for each topological_navigation instance, but this is a tiny script (probably):
#!/usr/bin/env python
import rospy
from topological_navigation.goto import *
if __name__ == '__main__':
rospy.init_node("go_to_node")
goto_cont = go_to_controllers()
rospy.spin()
Currently running the topological map visualisation as in
topo_nav_global.launch
Assumes that there is a single topological navigation instance available at /topological_navigation when instantiating the
go_to_node
service.When running multiple robots, a possible configuration is running the topo_nav_global to manage the map which the robots will use for navigation, but each one has its own topological_navigation instance to actually traverse the map. If visualise_map is run without the
-e
or-edit
args, only the edge, marker and zone interactive markers will be available (i.e. the editable ones), and the non-editable lines and waypoint markers will not show up becausegoto.py
will wait on thetopological_navigation
actionserver which will never become active.There two obvious solutions:
-edit
arg can be added and skip the go_to_node service creation.This would also require a separate go_to_node script so that the service can be started for each topological_navigation instance, but this is a tiny script (probably):
This would be run something like
or
from a launch file
This is a relatively small issue but at the moment it's not obvious why the visualisation doesn't appear.