Ctrl+K

Robot Programming syllabus

Robot Programming syllabus#

2 SWS, 3 ECTS, in degree program KI as PLV 2 and in AIN Bachelor as IAC 2

Intended learning outcomes#

The purpose of the course is for you (the student) to learn to:

  • design and compare different solutions for a robotics problem

  • model and implement a solution in a given robot programming framework

  • relate the behavior of an implementation in simulation and real world

  • structure their ideas and document their solutions in a reproducible way using a modern documentation framework

Prerequisites#

  • Fundamental programming tools (e.g, control flow, data structures, functions)

  • Beneficial: experience with Python or C++

Content (What we do to reach the learning outcomes)#

  • Programming using ROS (Robot Operating System) framework and Turtlebot3

  • Various mini projects including navigating through a maze

  • Documentation using Sphinx

Didactic methods#

Seminar-like with mini projects each solving a different problem.

  • The instructor gives the required introductions during the contact hours (typically the first contact hour of the day).

  • The students self-study the tutorials and work on the mini projects.

  • The results are demonstrated and discussed during contact hours (typically the second contact hour of the day).

Grading#

The examination is based on the intended learning outcomes.

Project work comprising:

  • setting up the CI/CD pipeline on Gitlab to deploy the Sphinx template to the given web server

  • the solutions (code) to the mini projects with documentation

  • project report on using Sphinx

  • solution presentations (you should be ready to present your result on the deadline)

There will be a deadline for each project. Every project must be completed before the deadline to pass the course. You can only pass or fail.

Requirement for passing a mini project (also called challenge. Including Sphinx deploy CI setup):

  1. You demonstrate the mini project to your classmate who checks if your solution meets the requirements of a challenge.

  2. Your classmate writes their name as the reviewer and your name as the reviewee to the corresponding worksheet on the spreadsheet project completion

  3. All above happens before the deadline

Note that the review for some mini projects may be carried out using a trust tree. Trust tree means that everyone must be reviewed by someone who already has been reviewed. The instructor will create the first reviewers (by reviewing the first students who have finished their mini project).

Collaboration#

Everyone works on the projects alone. The goal is that every student goes through the process of problem solving. At the end of the day you are encouraged to exchange ideas to help others come forward.

Each student writes a separate report so that every student can practice writing.

The submitted projects may be checked with a plagiarism software by the instructor.

Literature#

Time & Room#

For details refer to Moodle.

Presence is required for the sessions where we work with physical robots.

Contents