We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Trying to find out the feasibility of teleop service scenario described in the linked issue.
robotics-in-concert/rocon_demos#9
Does conductor or concert_role notifies the join/leave of HIA? If yes, how?
The text was updated successfully, but these errors were encountered:
I don't think detecting an android's joining teleop is useful. Typically the android is the initiator of a workflow, not the service.
It may be useful in esoteric use cases I can't think of though. And notification of leaving may be essential in helping cleanups.
For this, it would be useful to provide a similar handle on the role manager like conductor's concert clients messages.
Changing the name of this to reflect that.
Q) Do we need before the demo?
Sorry, something went wrong.
Not necessarily before the demo
Currently weakly publishing. Two problems:
Closing this - will continue in the two listed issues above.
publishes interactions, #141.
0394c75
stonier
No branches or pull requests
Trying to find out the feasibility of teleop service scenario described in the linked issue.
robotics-in-concert/rocon_demos#9
Does conductor or concert_role notifies the join/leave of HIA? If yes, how?
The text was updated successfully, but these errors were encountered: