-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use the /actions_hub topic and the ActionExecution message #260
Comments
I was confused. I now see that the simple example launch file was not the one in bringup so things are working. So there is no issue with starting the system. But what I seem to be missing is some unique identifier in the ActionExecution message. How are you supposed to run two action in parallell on the same robot and the same action but maybe different arguments. Do I have to make some string of the action and arguments so get a unique identifier? Also what is the field "node_id" in ActionExecution message? What is the meaning? |
Hi @tompe17
This is the topic that implements the execution auction protocol. You should check all the topics/services/actions that the executor currently has. I would like to write my own executor that listen on the messages on /actions_hub and takes care of the execution on the robot. Is that possible? Is /actions_hub the complete API for this?
I do not understand this very well. Please, clarify.
For executing the same action in the same robot you should have two different action executors running in the robot, with different node name
It is the node name Francisco |
I would like to write my own executor that listen on the messages on /actions_hub and takes care of the execution on the robot. Is that possible? Is /actions_hub the complete API for this?
The thing I cannot find is how to start the system without some "clients". It seems that the executor is starting something that tries to run the actions. At least if I start following the first tutorials. So how do I start it so I can use my own client executor written in Python?
The text was updated successfully, but these errors were encountered: