Skip to content
This repository has been archived by the owner on Apr 16, 2021. It is now read-only.

Team contest

Ugo Pattacini edited this page Jul 9, 2017 · 7 revisions

Dear @vvv-school/vvv17-students, after several days of hard work ๐Ÿ’ช you reached the final frontier ๐Ÿ’ฅ๐ŸŒŸ

As a final task, we would like you to develop a complete demo to run on the robot that requires reusing all the components you have studied at the VVV17 school, regarding Kinematics, Dynamics, Computer Vision and/or Event Based Vision, Machine Learning.

You will be working in 3 teams that will compete to win the first prize for the most awesome and effective demo. You are free to choose what your demo will be about, but we give you below an example you might want to consider. Bear in mind that you need to achieve a trade-off design between your great ideas and the limited time you have.

๐ŸŽฎ Let's start the competition ๐ŸŽฎ

Example of Demo

A possible demo could showcase the following capabilities:

  • The robot perceives an object using stereo-disparity and/or neuromorphic cameras and track it using the gaze controller.
  • The trajectory in the 3D space of the tracked object is learned on the fly and used to predict a suitable position ahead in time.
  • Then, the robot uses such an information to move its hand towards the predicted location.
  • If, while moving, an unforeseen contact with the environment is detected relying on force estimation, then the robot will react safely undertaking proper countermeasures (e.g. just stop and go back home).

Team Leaders

  • ๐Ÿบ๐Ÿป๐Ÿฏ Three team leaders will be identified resorting to the final ranking. With more than three possible candidates, we will proceed with drawing.
  • ๐Ÿ‘‰ The team leaders have to choose the color ๐Ÿ“˜๐Ÿ“—๐Ÿ“™ and the members ๐Ÿ‘ฅ of their team. The selection will take place according to the ranking and/or the drawing order, one member per team at time.
  • โœจ Team leaders are also GitHub team maintainers with these permissions. In particular, they will start the activities by adding their members to the team.
  • ๐Ÿ‘ท They have to coordinate the team tasks with the help of their assistants.
  • ๐Ÿ“ˆ They have to present the final demo the last day, with a brief talk, on behalf of the team.

โš ๏ธ Don't worry, leaders can delegate these activities to other team members ๐Ÿ˜‰

Teams

Repositories

Each team has write access to its own private repository ๐Ÿ”’ (no way to steal competitors' technology then ๐Ÿ˜):

โš ๏ธ Please, use your team repository to collect the whole amount of work you are going to produce in terms of code, documentation, issues, wiki, diagrams, discussions, website front-end...

At the end of the contest, the repositories will be made public ๐Ÿ”“:globe_with_meridians:

Robots Characteristics

We have two robots you can book for your tests. They are mostly equivalent, except for the following peculiarities:

๐Ÿค– Blacky โšซ ๐Ÿค– Lily ๐Ÿ’œ Reference People
Cameras Standard Neuromorphic @vtikha / @ChiaraBartolozzi @arrenglover
Dynamics Estimation only Full Torque Control @DanielePucci @francesco-romano @traversaro @iron76

Evaluation Criteria

In descending priority order:

  1. How many topics (i.e. Kinematics, Dynamics...) your team has addressed.
  2. How the ๐Ÿค– behaves (e.g. efficiency, stability, robustness) on the whole in response to @vvv-school/vvv17-teachers' inputs.
  3. How the repository is organized in terms of code and documentation.
  4. Possibly, @vvv-school/vvv17-teachers will review your team's code.

Why not publishing a paper?

Lately, we have called for a special research topic on Frontiers in Robotics and AI that is specifically devoted to code papers to build the iCub mindware. Then, why don't you consider submitting your original work?

Find out more about the topic call, deadlines, templates...

Instructions

Material

Team contest

Services

AOB

Clone this wiki locally