This is part of the Robotics in Concert project. |
Only released in EOL distros:
Package Summary
Includes tools for handling solutions, linking and app distribution.
- Maintainer status: developed
- Maintainer: Daniel Stonier <d.stonier AT gmail DOT com>, Jihoon Lee <jihoonlee.in AT gmail DOT com>
- Author: Daniel Stonier <d.stonier AT gmail DOT com>, Jihoon Lee <jihoonlee.in AT gmail DOT com>
- License: BSD
- Bug / feature tracker: https://github.com/robotics-in-concert/rocon_concert/issues
- Source: git https://github.com/robotics-in-concert/rocon_concert.git (branch: groovy-devel)
Package Summary
Includes tools for handling solutions, linking and app distribution.
- Maintainer status: developed
- Maintainer: Daniel Stonier <d.stonier AT gmail DOT com>, Jihoon Lee <jihoonlee.in AT gmail DOT com>
- Author: Daniel Stonier <d.stonier AT gmail DOT com>, Jihoon Lee <jihoonlee.in AT gmail DOT com>
- License: BSD
- Bug / feature tracker: https://github.com/robotics-in-concert/rocon_concert/issues
- Source: git https://github.com/robotics-in-concert/rocon_concert.git (branch: hydro)
Package Summary
The concert framework modules.
- Maintainer status: developed
- Maintainer: Daniel Stonier <d.stonier AT gmail DOT com>, Jihoon Lee <jihoonlee.in AT gmail DOT com>
- Author: Daniel Stonier, Jihoon Lee
- License: BSD
- Bug / feature tracker: https://github.com/robotics-in-concert/rocon_concert/issues
- Source: git https://github.com/robotics-in-concert/rocon_concert.git (branch: release/0.6-indigo)
The Concert
Overview
The concert is a multimaster framework running on top of the interactions, appable robot and gateway components that tries enable a centralised workspace on the network (usually LAN) from which to co-ordinate and manage a group of robots, devices involved in some kind of scenario. This can be used standalone, or it can be further developed as a useful bridge to the cloud1. Some features:
Wireless Connectivity : technology for robust handling of wirelessly connected robots.
Multi-Service Handling : services as parallelisable orchestration blocks at a higher level
- Think services running on a web server, but here we have teleop, make a map, annotate a map, foo...
Robot Scheduling : expose robots as retaskable resources that can be requested by concert services.
Software Sharing : spawn and share access to software instances across concert services.
Human Interactions : infrastructure for coercing humans as interactive participants of concert services.
More detailed concept notes can be found if you go walkabout from our Terminology page on the rocon wiki.
Tutorials
Quick Demos
- Chatter Concert
An example concert demonstration, talker-listener style.
- Chatter Concert - Distributed
Distributing chatter concert on multiple machines
- Chatter Concert - Wireless
Wireless handling of distributed chatter concerts
- Turtle Concert
An example concert demonstration, turtlesim style.
- Turtle Teleop Concert
The concert teleop service with simulated turtles.
Create Your own Solution
- Create Your Own Solution
how to create your own solution
- Bring up a Concert
how to start the concert
- Customise Service Configurations
how to create your own solution
- Enable Web Interactions
how to access and interact with concert via web
- Advanced Solution Customisation
describes what arguments concert provides
Make Your Robot To Join Concert
- Concert Client Preparation
what to install and todo for concert mode preparation
- Create Concert Mode Launcher
how to prepare your robot to use in your concert
- Join Concert as a Client
describes how to join a concert as a client
- Teleop a robot via Concert
describes how to capture a robot and teleop via concert
Create Your own Service
- Create Your Own Service
how to create your own service
Gazebo Concert
- Concert Service Gazebo Overview
Describes design flow of concert service gazebo
- How to add a new robot type
How to add a new robot type to use in concert service gazebo
- How to spawn robots in concert gazebo
how to spawn robots in concert gazebo
Putting the concert on a pc that resides on the ethernet backbone to gather and process incoming/outgoings can be alot more practical than pushing everything from every wirelessly connected robot to the cloud. (1)
