64-850-P Project Intelligent Robotics
Room: | F-326 (PR2 lab) |
Date: | Thursday, 16:00 - 20:00 |
Organizer: | Shang-Ching (Sam) Liu |
This course is a single-semester project focused on the design and implementation of intelligent robotic systems. It replaces the previous two-part Master Project format.
Course Description
This project provides students with the opportunity to design, develop, and implement scenarios for complex robotic systems to accomplish human-defined tasks. Participants may work with a variety of robots and sensors, including UR5 and UR10e robot arms, a Kuka LWR, a PA10 arm, a PR2 robot, Shadow Robotics Dexterous Hands, multiple Turtlebot2 platforms, as well as a suite of cameras, tracking systems, laser scanners, and force/torque sensors.
All robotic platforms are controlled using the Robot Operating System (ROS), which allows for seamless integration of hardware components. The course emphasizes hands-on experience with ROS (primarily in C++ and Python), robotics platforms, simulation environments, and the TAMS lab infrastructure.
Through this project, students will engage in solving real-world robotics challenges such as navigation, self-localization, object detection, manipulation, and human-robot interaction. The course is conducted in English and held in person at the TAMS lab.
Learning Objectives
- Gain practical experience using and programming state-of-the-art robotic systems
- Work with multiple sensor types and robotic platforms
- Develop complex robotic behaviors and control strategies
- Collaborate on challenging robotics problems in a lab setting
Recommended Preparation
- Proficiency in C++ or Python
- Basic Linux knowledge
- Familiarity with ROS tutorials
Relevant Topics
- ROS integration and simulation
- Sensor fusion and hardware control
- Computer vision (OpenCV, YOLO)
- RGB-D and 3D data processing (PCL)
- Motion planning and control (Behavior Trees, State machines)
- Data visualization and debugging tools (RViz, PlotJuggler, rosbag)
🎬 Previous Demos
Take a look at some of our previous student projects to see what’s possible in this course: Project Demo List
Appointments
The following schedule is tentative and will be updated according to the participants' previous knowledge and interests.
- 10.04.2025:
- 17.04.2025:
- 24.04.2025:
- Assignment #4 (Group Collaboration) [PDF]
- Project Exposé
- Assignment #4 (Group Collaboration) [PDF]
- 08.05.2025:
- Master Project Diana setup investigation and Rubik's cube solver with CV
- 15.05.2025:
Practical Implementation 1 - 22.05.2025:
Practical Implementation 2 - 05.06.2025:
Practical Implementation 3 - 12.06.2025:
Practical Implementation 4 - 19.06.2025:
Practical Implementation 5 - 26.06.2025:
Practical Implementation 6 - 03.07.2025:
Practical Implementation 7 - 10.07.2025:
Practical Implementation 8 - 17.07.2025:
Practical Implementation 9
Evaluation (100%)
To successfully pass the course, students must:
- Seminar Component (link) (30%): Deliver graded presentations at both the application level and the method level.
- Robotic Demonstration (Pass/Fail): Contribute to the final robotic demonstration.
- Public Presentation (Pass/Fail): Participate in the final public project presentation, including a demonstration of the developed system.
- Written Contribution (70%): Contribute sections to the final written submissions (see next section).
Written Submissions
At the end of the project, the group must provide complete documentation of their work. This consists of two complementary parts:
-
Source Code and Project Documentation
All final source code and project structures developed during the project must be thoroughly documented. The aim is to allow someone with no prior affiliation to the project to reproduce and further develop the final demonstration.
-
A technical overview for each component (typically provided as a
README.md
), including clear setup and development instructions. - Documentation of known issues that may affect the demonstration.
- Well-structured and commented source code, ensuring accessibility for future users.
-
A technical overview for each component (typically provided as a
-
Scientific Project Report
In addition to the technical documentation, the group must submit a scientific-style report in the format of an IEEE conference publication (6–10 pages). This report should abstract away from implementation details and instead focus on broader insights. Suggested sections include:
- Overall scope and system architecture
- Related work at both the system and component levels
- Methods and alternative approaches considered during development
- Limitations of the chosen approaches
- Evaluation of results, including conclusive analysis if experiments were conducted