Skip to content

Team contest

Ugo Pattacini edited this page Nov 30, 2017 · 28 revisions

Dear participants, after one day 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 during this intensive crash course, regarding YARP, PID Control, Computer Vision.

You will be working in teams of up to 5 members that will compete to win the first prize for the most awesome and effective demo.

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

Demo Requirements

The demo shall showcase the following capabilities:

  • The robot detects the closest object using the stereo disparity provided by SFM.
  • The robot performs continuous tracking of the detected blob.
  • Optionally, as response to external stimuli, the robot can also express its internal state by uttering distinct sentences using iSpeak and/or producing distinct head movements (e.g. nodding/shaking).

Team Leaders

Teams have to appoint one of their members as Team leader.

  • ๐Ÿ‘ท Team leaders have to coordinate the team tasks with the help of their assistants.
  • ๐Ÿ“ˆ They have to present the demo at the end of the second day, with a brief talk, on behalf of the team.
  • โœจ Team leaders are also GitHub team maintainers with these permissions. In particular, they will start the activities by adding their members to the team.

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...

Booking system

We have made available a poll where teams can book time slots to test their code on the ๐Ÿค–

Evaluation Criteria

In descending priority order:

  1. How the ๐Ÿค– behaves (e.g. efficiency, stability, robustness) on the whole in response to mentors' inputs.
  2. How the repository is organized in terms of code and documentation.
  3. Possibly, mentors will review your team's code.

Instructions

Team contest

Services

Clone this wiki locally