You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move rosgraph_manipulator to a separate repo, because it is a metacontrol asset that should be "experiment/system" agnostic, but platform specific for ROS1
The text was updated successfully, but these errors were encountered:
We, at IPA, have a potential new use for the rosgraph_manipulator, is it possible to make it generic? For example take the list of nodes to be killed from a yaml file.
make it sense for you @marioney ? We can also support/send a suggestion as PR
is it possible to make it generic? For example take the list of nodes to be killed from a yaml file.
I think that's a good idea. And of course we would really appreciate your support on this.
We can also support/send a suggestion as PR
I think a PR will be good, so we can discuss on the details for the change there
As of now, we're only killing the move_base node, but actually, the kill_node function accepts the node name and namespace, so it's just a matter of changing the way it's used.
Move rosgraph_manipulator to a separate repo, because it is a metacontrol asset that should be "experiment/system" agnostic, but platform specific for ROS1
The text was updated successfully, but these errors were encountered: