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

Team contest

Vadim Tikhanoff edited this page Feb 13, 2018 ยท 23 revisions

Dear @vvv-school/vvv18-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 VVV18 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.

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

Demo Requirements

The project should include most of the topics that you have studied during your days @ the winter-school. As a shared topic, we chose to have an interactive recycling scenario where i) the user shows two objects to the robot and asks him to indicate one (this can be done either by spoken command - Vadim will help - or simply via rpc), ii) the robot classifies them and points to the correct object, iii) in order to get the feedback from the user, the robot performs a high-five or low-five gesture. If the user taps correctly, the answer the robot gave was correct, otherwise the answer was incorrect. At this stage the robot could manifest some behaviour to simulate happiness or sadness.

  • Vision: segment object in scene. Here you can use either the assignment from the Vision day (Black iCub) or the one from the event-driven day (Purple iCub)
  • Object classification: classify object provided by the user
  • Kinematics: point to its correct recycle bin.
  • Dynamics: use torque control (Purple iCub) or impedance control (Black iCub) to produce the following two behaviours:
    • low-five
    • high-five
  • Create various behaviours for correctness of results.

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:

Booking system

We have made available a booking system where teams can reserve 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, teachers will review your team's code.

Instructions

Material

Team contest

Services

AOB

Clone this wiki locally