bild
School of
Electrical Engineering
and Computer Science

Robotics and autonomous systems

Teaching team

  • Patric Jensfelt - lecturer, responsble for the course
  • Fernando Jose Iglesias Garcia- teaching assistant
  • Andrzej Pronobis - teaching assistant
  • Alper Aydemir - teaching assistant

Intro

This course is an advanced course in computer science focusing on the broad, inter-disciplinary field of robotics where the students build and program an autonomous robot.

The KTH robotics course webpage

Aim

After completing the course the student should be able to
  • design and implement an autonomous robot, including mechanics, computer software and hardware as well as programming
  • explain basic concepts and technologies in the broad and interdisciplinary field of robotics
  • identify the possibilities and limitations for robot technology of today.
  • analyze a technical problem holistically
  • develop strategies for solving and then solve a problem with limited information and resources
  • integrate knowledge from different domains and source for designing and building a complete system
  • make decisions based on acquired knowledge
  • acquire new knowledge when needed
  • assess the quality of his/her own work and that of others
  • working, communicating and solving problems in an international project group under pressure
  • document and present results, conclusions and arguments supporting these in written and oral form
in order to
  • be able to work with autonomous and other complex systems in research and/or development
  • become better at planning and executing develop work in project groups

Course description

The course is divided into two parts, one that covers theory (lectures and lab) and one for practice (project). The course runs over two periods which rought cover one of these parts each. The majority of the work will be done in period 2 (the project).

Lectures

The theoretical part of the course deals with fundamental concepts in robotics, kinematics and navigation. This part of the course consists mainly of the lectures and a lab assignment.

We will try to avoid too much of the normal teacher-speaks, students-listen paradigm for the lectures and instead discuss the different topics in the book together. The lectures will therefore more be like a combination of seminar and workshop. There are several reasons for this. The assumption is that everyone has read the material before each meeting and thus comes prepared. The goal with each meeting is that everyone gets a chance to get their questions answered so that we leave knowing what is required to know about that topic in the course. This promotes a deeper approach to learning and allows us to use the time together more efficiently than simply reciting the book.

The lecturer will present the material in a condensed form for about 45 min approximately (instead of 90 minutes as before). As you can imagine 45min is not that much and there is no way that all the material can be covered in that time. Every student attending the lecture is supposed/assumed to have read the material dealt with. You should also collect the questions that you got when reading the material and write these down so that they can be discuessed during the lecture.

After the lecture you will be divided into groups and you will be given about 30min to discuss the material within the group. This is an excellent time to try to get your questions answered with the help of follow students. A number of questions will be handed out to the groups to discuss around.

At the end of the lecture we will discuss the findings of each group in full class again.

Note that the lectures are supposed to be an instrument for learning and not assessment. You should participate actively in the lectures and related activities but what you do does not affect your grade. The lectures situtation is thus a "safe" environment where no question is too simple or stupid and learning is the only goal.

Lab assignment

The lectures and the project will mostly deal with mobile robotics. However, a large part of industrial robotics today deals with industrial robots, i.e. manipulators. There will be one lab during the course where you will gain some experience with working a simulated robot arm. If you complete this lab on time you can earn some bonus points on the exam. There will be two sessions in computer rooms (Spelhallen) followed by some additional timeslot to present the results of the lab.
  Date Time Place
Lab Sept 14 15-18 Spelhallen
Lab Sept 21 15-18 Spelhallen

Learning statement

Before the project part of the course each student is required to produce a document where s/he discusses what s/he wants to learn more by the end of the course. Again this is to make you actively think about the learning. Each student come into the course with a different background, different skills and thus it is likely that you will want to learn different things. After the course you will produce a document where you reflect one what you did learn and how that relected to what you wanted to learn.

Project

During the course a small, mobile, autonomous robot for performing a certain task is built. This work is carried out as a project. The participants in the course work in groups on the practical implementation of a specific behaviour of this simple robot by integration of mechanisms for sensing, perception, planning and control of actions on the robot. At the end of the course there is a contest between the robots that the participants have constructed to assess the strength and weaknesses of different approaches.

Course labs:
1535 (Computers and test environment)
1621 (small workshop)

The project task will be described in more detail on BILDA

The task to perform may vary from year to year. Over the last years the groups have build robots that play hockey and football and navigate through a maze to do search and rescue. You will most likely spend most time during the course working on the project. For many students this is the first time that they get to apply a lot of the knowledge that they have acquired over the years at KTH or elsewhere. The project also offers a chance to work with an open-ended problem that offers a challenge beyond that of a typical lab or project. You need to plan the work, build the mechanics, design the algorithms, program low and high level and evaluate the result. The project thus gives you a chance to see something come to life from the drawing board to an experimental prototype. You will be divided into groups by the course team.

During the project work each group should submit a brief progress report every week and each individual students should also submit a brief actuvity report.

After the contest where the groups compete get to show what there robot can do there will be a debriefing seminar. Each group should present their project and discuss, for example, things they did well and things they learned. The groups should think about what they would want to hear/learn from the other groups and use that as a guide for what to talk about. The presentation is not graded in itself, but it is a chance to draw attention to solutions/functionality/innovations that might affect the grade. Each group gets 5 min for the presentation so focus on the important stuff. The aim is not that you explain everything about the robot (you cannot!). After the presentation the audience can ask questions to get more information. The seminar is intended to be of workshop nature with a lively discussion and not at all formal. You can use whatever means you want for the presentation (slides, handouts, videos, demos, etc). In 5 min you do not have time to draw that much on a board so some form of preparation is wise.

Towards the end of the course the project work should be documented in a project report. The report should be written as a technical report. It should be submitted as a pdf.

At the end of the course each student is also required to hand in a self-reflection that discusses her/his work in the project. What did you spend time on? Did it take as much time as planned? Did you learn what you set out to learn? The aim again is to make you think about the learning. This document should also contain what you think is an appropriate grade for your own work in the course with a motivation. See assigments in BILDA for more info.

You are also required to produce a document where you reflect on the work by the group. How did the group work together? Did you follow the project plan? If not why? Was something harder/easier than planned? See assigments in BILDA for more info.

Course book

The course book is "Introduction to Autonomous Mobile Robots" by Roland Siegwart et al" published by the MIT Press.

Requirements

The requirements for passing the course are
  • Individual
    • Write a (approx 0.5-1 page) statement about what you hope to learn in the course (submit to BILDA).
    • Work report after each week of the project to document what you did that week. These reports will not be looked at unless there is a conflict in the group at the end about the grade.
    • A reflection (1 page typically) on your work in the course. Did you learn what you wanted? What did you spend time on (account for the time you spent)? (Submit to BILDA)
    • A reflection (1 page typically) on the work within the group. What worked within the group? What did not? Could you have planned something differently? (Submit to BILDA)
  • In groups of two
    • Complete a lab assignment about manipulators
  • In project groups
    • Write weekly status reports
    • Solve the project task (See BILDA)
    • Write a report (Submit to BILDA)
    • Present the project work in debriefing meeting after the competion

Grading

See BILDA for more information The grade on the course is given by the exam (25%) and your work in the project (75%). Exam and projects are given a score between 0 (just passing) and 10 (max). You get 1 point extra added to the exam result if you complete and present the manipulator lab assignment at the bonus date at the latest (i.e. max 11 in this case). Note that it is not only the result of the project work that counts but also the process of how you got there, the report, etc. The grade is often not the same for all member in the project groups. It is fine if different group member have different leves of ambition, that will always be the case to some extent, you need to discuss this in the group openly to reduce friction. The mapping from score to grade is given by the table below
Score Grade
>=8 A
>=6 B
>=4 C
>=2 D
>=0 E

Important Dates

Event Date
Bonus for LAB Sept 28
Exam Oct 22, 15-18
Contest Dec 6, 9-15
Debrief Dec 13, 13-16

Contact

If you have any questions regarding the course you can contact
Copyright © Published by: Patric Jensfelt <patric@nada.kth.se>
Updated 2011-12-08