• Students are expected to work in teams by two (exceptions allowed after consultation with teacher).
• Each group is expected to work with a real robot.
• Majority of the work is planned as an individual work of the group (you can work anytime the room is available).
• Students are expected to ask - ask early, ask often.
• Teachers will be personally available during the regularly scheduled hours, otherwise over the e-mail (but don't expect answers in order of minutes)
• Charge the robot every time you stop working with it.
• Keep all source codes on CSV (SVN or GIT). The disk on the on-board computer can be erased anytime (No complains - you were warned).
• You are sharing the robots with others, keep it clean (physically as well as the disk space). Don't mess with others' stuff.
• Create your own ROS workspace. Use a naming convention mkr_<group_name>_ws.

• slides

• Each team is asked to implement selected algorithms presented on lectures:
  • Multi-robot motion coordination
    • slides
    • Code
  • Kalman filter and Extended Kalman filter for localization
    • Slides
    • Code
  • Particle filter for global localization
    • Motion model code
    • Particle filter code
    • Particle filter code for ROS
    • Slides
    • Video with motion model demonstration

To get the seminar credit, student must:

• Participate and actively work at all seminars (up to 2 absences without excuse will be tolerated),
• Create a working algorithms solving *all* the tasks,
• Present a well-written and documented source code,
• Understand the presented solution and source code (each team member).

Back to the course page.