Understand the source
- 01
Run the first public robot-arm example
- 02
What the robot sees and how success is measured
Public research sourceStanfordSVL / ARISE Initiative
First understand what Stanford researchers are trying to learn through SVL / ARISE Initiative, why the question matters, how they test it, and what the result cannot prove. Run a simulated robot arm picking up an object and see how the camera and starting position change its success rate. The student then completes A robot-arm pickup app with a retry feature, experiment controls, and an evidence-grounded explanation tool. 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.
Run a simulated robot arm that lifts an object or opens a door. Change the camera position and movement method to compare why it succeeds or fails.
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-arm pickup app with a retry feature, experiment controls, and an evidence-grounded explanation tool
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 first public robot-arm example
What the robot sees and how success is measured
Read camera and distance information
Compare three ways to move the arm
Change only the object's starting position
Implement the student-owned feature: A retry feature that selects another camera view or grasp point when the object is hidden or the first grasp fails
Build the operator interface: An operator screen for choosing the object, camera, and starting position and viewing success rate, collision replay, and retry reason. Add the bounded assistant: Optional: an LLM explanation tool reads only saved run records and summarizes possible failure causes with run IDs. It cannot send robot commands.
Integrate, test, and demonstrate: A robot-arm pickup app with a retry feature, experiment controls, and an evidence-grounded explanation tool
Public project used in class
Public projects can change over time. To keep the class example consistent, CIT uses version 5ce6643f3092 of ARISE-Initiative/robosuite. CIT checked it on 2026-08-14; it was created on 2026-07-11. Usage-rights note: MIT.
5ce6643f3092The student changes the control rate in a robot-arm simulator and explains why the same commands give a different result. 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 setup plus the motion a person enters through a control device, or the action a policy emits
The objects and robot models that make up the scene, and the current state the physics engine holds
The controller that turns an action into joint torques, and the physics that advances the scene one step
The observation dictionary and reward, and the scene sent to a viewer or a video
The fact that the control rate differs from the physics rate, and the part that decides how many physics steps fit inside one env step
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 start, GPU optional.
Recommended level: Beginner to intermediate. 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-arm pickup app with a retry feature, experiment controls, and an evidence-grounded explanation tool. The student implements A retry feature that selects another camera view or grasp point when the object is hidden or the first grasp fails and An operator screen for choosing the object, camera, and starting position and viewing success rate, collision replay, and retry reason. Optional: an LLM explanation tool reads only saved run records and summarizes possible failure causes with run IDs. It cannot send robot commands.
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 5ce6643f3092 of ARISE-Initiative/robosuite on 2026-08-14. That version was created on 2026-07-11. 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