Understand the source
- 01
Run the working cube-pickup example
- 02
Understand the simulated robot, object, and actions
Public research sourceUC San DiegoHao Su Lab / SAPIEN
First understand what UC San Diego researchers are trying to learn through Hao Su Lab / SAPIEN, why the question matters, how they test it, and what the result cannot prove. Let many simulated robots practise picking up a cube at once and compare how training conditions change the result. The student then completes A robot-learning experiment dashboard that batch-tests training conditions and compares failure scenes. For a college application or interview, the student separates the source research from their feature, interface, tests, failures, and revisions. Available online or in person in Apgujeong, in one-to-one or small-group formats.
University and lab names show where each public project came from. CIT independently designed these courses; they are not official university courses, partnerships, or endorsements.
Primary routes
CIT keeps the international-school route first, followed by the separate science and gifted-school route.
CIT lessons can run online across Korea and overseas or in person in Apgujeong. The student owns the question, code, tests and explanation; classes do not guarantee admission, selection or awards, and online delivery never changes an institution's submission rules.
Train many simulated robots at the same time and compare how object size, friction, and goal position affect what they learn.
Students first use a small working example to understand the researchers' question, method, and evidence. A controlled change helps identify what the student's extension must solve. The student then implements a useful feature, connects an operator interface, and tests the integrated application in normal, boundary, and failure cases.

A robot-learning experiment dashboard that batch-tests training conditions and compares failure scenes
The final package includes runnable instructions, the feature and interface design, normal and failure tests, one documented revision, and a three-minute explanation in the student's own words.
Eight introductory sessions
The 20 courses are eight-session CIT studios in which students understand a public university or lab project, confirm a working example, and then turn it into a small robotics application with a useful feature and an operator interface. Selected courses add an optional LLM explanation tool that can read run records but cannot control the robot. RoboMaster has 28 sessions, and implementation scope is adjusted to each student's experience and computer access.
Run the working cube-pickup example
Understand the simulated robot, object, and actions
Compare numeric information with camera images
Compare a fixed rule with random actions
Change object size, friction, and goal position
Implement the student-owned feature: A feature that creates and tests batches of object-size, friction, and goal-position combinations to find the weakest condition
Build the operator interface: An experiment dashboard comparing training settings, practice count, success rate, and failed scenes side by side. Add the bounded assistant: Optional: an LLM proposes a next experiment using only selected graphs and run records, without changing training settings automatically.
Integrate, test, and demonstrate: A robot-learning experiment dashboard that batch-tests training conditions and compares failure scenes
Public project used in class
Public projects can change over time. To keep the class example consistent, CIT uses version 62ff3a5896b4 of mani-skill/ManiSkill. CIT checked it on 2026-08-14; it was created on 2026-08-02. Usage-rights note: Apache-2.0.
62ff3a5896b4The student changes only the number of practice scenes and checks whether faster also means better. In class the project is separated into five boxes (input, memory, process, output, control). The lesson opens one of them, changes one value, and leaves the rest closed.
The task definition that says what counts as success, and what the cameras send back
The state where hundreds of scenes' positions and speeds sit together in one array
Turning a command into motion, then scoring how close the result came to the task
The observation, the score and the success flag that come back for each scene
What decides how many scenes run together, and when a failed scene is reset
The files the lesson opens, by name. The course is not a walk through the repository; it opens a chosen few and says which.
One value moves and everything else stays. The right-hand column is the prediction written before the run, not a result; the work is reconciling the two.
On a narrow screen, swipe the picture sideways.
The universities and labs named here made the open projects this course reads. CIT designed the course independently; it is not an official, affiliated, or endorsed course.
Clear answers about what students do, what they need, and where the project came from.
University and lab names show where each public project came from. CIT independently designed these courses; they are not official university courses, partnerships, or endorsements.
Not required. The course starts with a robot on the computer or a saved recording of a completed run. Computer guidance: CPU simulation possible, GPU recommended for parallel training.
Recommended level: Beginner-intermediate, advanced for training. Students should be able to follow a guided Python example, test one controlled change, and then build and explain a small feature and interface.
The completed project is A robot-learning experiment dashboard that batch-tests training conditions and compares failure scenes. The student implements A feature that creates and tests batches of object-size, friction, and goal-position combinations to find the weakest condition and An experiment dashboard comparing training settings, practice count, success rate, and failed scenes side by side. Optional: an LLM proposes a next experiment using only selected graphs and run records, without changing training settings automatically.
Explain the source research question, method, evidence, and limits first. Then separate the student's own feature and interface decisions, normal and failure tests, revisions, and next question. The source institution's name does not imply affiliation or guarantee admission.
CIT reviewed version 62ff3a5896b4 of mani-skill/ManiSkill on 2026-08-14. That version was created on 2026-08-02. We keep this version during class so the example does not change unexpectedly, and we check the setup again before teaching.
Yes. This course is offered online and in person at CIT in Apgujeong, Gangnam-gu, Seoul, with one-to-one and small-group options. Placement and current availability are confirmed after a readiness consultation.
Before placement, we check the student's coding and math experience, available computer, interests, and ability to explain what happened.
Request a course consultation