-
Notifications
You must be signed in to change notification settings - Fork 7
Team contest
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 🎮
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 scenario where:
- 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).
- The robot classifies them and points to the correct object.
- In order to get the feedback from the user, the robot performs a high-five or low-five gesture. The user should evaluate the reply given by the robot. If the answer was correct he taps the hand of the robot correctly (on the plam), otherwise he touches the hand in another direction (the back or the side). At this point, the robot manifests some behavior to simulate happiness or sadness.
To implement this scenario you can recruit:
- Vision: segment the objects in the 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 the objects provided by the user.
- Kinematics: point to the correct object.
- Dynamics: produce a low-five and/or high-five and estimate the force the user applies to the hand. The low-five and high-five do not need to be dynamical: it is sufficient if the robot goes to a predefined position. Use the dynamic libraries to compute the external force and detect the direction in which the user "taps" the robot.
- Create various behaviors for the correctness of results.
- 🐺🐻🐯 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.
Each team has write access to its own private repository 🔒 (no way to steal competitors' technology then 😏):
- 📘 💻 vvv-school/vvv18-demo-team-blue
- 📗 💻 vvv-school/vvv18-demo-team-green
- 📙 💻 vvv-school/vvv18-demo-team-orange
At the end of the contest, the repositories will be made public 🔓:globe_with_meridians:
We have made available a booking system where teams can reserve time slots to test their code on the 🤖
In descending priority order:
- How the 🤖 behaves (e.g. efficiency, stability, robustness, number of behaviors) on the whole in response to teachers' inputs.
- How every module of the architecture performs alone.
- Which technology did you use? Is it a brand new piece of software or did you learn how to re-use a pre-existing tool?
- What are the current limits? To which extent your module is supposed to work?
- Is there any contingency plan to handle unexpected failures and showcase at least single functionalities?
- Quality of introductory presentation.
- How the repository is organized in terms of code, documentation and Git workflow.
- Possibly, teachers will review your team's code.
Return to Home Page