-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add support for Actions using actionlib #229
Comments
Then we can update the AGSE example to be more complete by having:
|
Need to find a good way to not require the user to specify the (generated) callback functions for feedback etc. when calling |
…iting of Action, Action Server, and Action Client.
…n dependency management. simplified processor to use _ library
Dependent on ros/actionlib#100 and ros/actionlib#98 for now we will use https://github.com/rosmod/actionlib until ros/actionlib#99 gets approved. |
Need to update actionlib to not create node handles by default - since right now I get an issue with |
right now this is dependent on rosmod/rosmod-comm#8 |
… RunExperiment to call "rosrun rosmod_actor rosmod_actor" instead of assuming rosmod_actor is in the PATH.
…ing - each action server will be in its own thread but the goal messages it receives will pass through the component queue. currently requires the fork of https://github.com/rosmod/actionlib and https://github.com/rosmod/rosmod-actor to function properly.
Should add support for requesting a (long running) task to execute on another component and getting feedback messages until completion using actionlib
The text was updated successfully, but these errors were encountered: