Possible features

Table of Contents Configuration file Repo server twisted implementation of ROS interfaces Interfaces Questions / Tasks Possible test case Nodes

Configuration file

• Use YAML or something similar (JSON is to simple)
• Feature to "load"/"save" configuration using a client

Repo server

• check this

twisted implementation of ROS interfaces

• based on txrospy (probably without the @inlineCallbacks)
• (also have a look at buffering)

Interfaces

• Review interface of Endpoint Interfaces (e.g. how to pass necessary parameters)
• simplify addition of Endpoint Interfaces (i.e. some kind of plugin system)
• (also have a look at buffering)

Questions / Tasks

• Specify type of interface & validate selection
• Manage interfaces in a generic way (i.e. they all have to be a subclass of rce.slave.interface.Interface)
• Configure/select what type of interfaces are available

Possible test case

• Use echoserv.py from twisted's examples as a very basic "ServiceInterface"
• Use google's protocol buffers as a "Converter"

Nodes

• Review interface to launch executables (nodes)
• move launch code into separate process to allow running executables as a different user