"Abstract" >> Contains what you will learn and general summary, what the tutorial about

"CUSTOM"

"Summary"

1. Workflow outline - Basics develop and running components [Thomas]

a. create library (producer / consumer): two classes, one generates a string with timestamp and the other one displays it. Two separate packages. Integration in the build system.

b. create corresponding orogen tasks. Two separate packages.

c. Start script with Ruby. Integration in the build system.

d. embed configuration

provide source files for the tutorial

2. Logging and replay [Alex]

a. enable logging

b. replay, log replay

c. rock-display

explain the mapping between stream names and the Ruby code. Add a short explanation on "pocolog logfile" to inspect what is in a logfile.

3. Visualization and data analysis [Alex/Janosch]

a. display log data

b. ui files, gui development vizkit widget

c. 3D-data vizkit plugins (Janosch)

4. Plotting Data (Jakob)

a. gnu plot

5. Rolling Rock - holistic example/showcase [Janosch]

a /b. writing "control component" and its deployment (MotionCommand => Pose). Integration in build system. Run it while sending command from ruby script. Visualization (pose and motion command) using vizkit plugin in the ruby script.

c. Integration of Joystick into Showcase

d. Use a GUI to steer the rock e.g. the Virtual Joystick widget.

document the Rock CMake macros

documentation / tutorials / examples on specific "issues"

using envire

system distribution (CORBA vs. avahi)

styleguide documentation, where to put and where to reference (can we actually publish the adapted google-styleguide)

publish on gitorious

integrate in documentation building and link from guidelines

Tools

create rock-inspect (Alex)

displaying available widgets vizkit/vizktit.rb

rename rock-create-vizkit-widget to rock-create-vizkit3d-plugin

create the real rock-create-vizkit-widget

"how do we relate to ROS" page

write a page about the base types

improve autoproj workflow for creating new package sets

MEDIUM PRIORITY TASKS

Will have to be done before the release

publish a small camera log file

publish the new rock.base with updated master/next/stable

check the body frame convention in code that should be released

manifest.xml > what policy on using depend vs. rosdep

make a guideline out of it

move some more packages from DFKI internal servers to gitorious (list which ones, cleanup, publication)

documentation / tutorials / examples on specific "issues"

how to write a device driver

documentation on taskmon (top-like visualization ?)

LOW PRIORITY TASKS

Nice to have, but not release showstoppers

"systems using Rock" page => detailed examples / use cases

need clearing it with DFKI management

add runtime dependencies to autoproj, e.g. dependencies that are build but do not trigger a rebuild, to fix the orogen project => orocos.rb dependency problem

website search: search input should be at the right of the toplevel main menu