The Core

Your first complete robot-learning project.

The planned 12-week ON Robotics Core is for high-school students who want to understand how AI connects to real machines. The starting point is a controlled robot-arm task—not an expectation that beginners immediately program a humanoid.

Learn the project cycle: write and review code, collect demonstrations, prepare a dataset, train a model with guided tools and evaluate its behavior on a physical robot.

Program facts

Planned Core description.

Confirmed cohort facts are published when registration opens.

Student level
High-school students, typically ages 14–18; local grade equivalents accepted.
Duration
12 teaching weeks. Holidays and recovery sessions may extend the calendar.
Weekly effort
Approximately 5–6 hours, including teaching, practice and a team lab session.
Teaching
Two 90-minute live classes per week.
Lab format
A planned 60-minute team booking, normally shared by four students with rotating roles.
Readiness
A short assessment; prior robotics experience is not required.
Preparation
An optional two-week bridge, approximately four hours per week.

A typical week

Learn a new idea in the first live class. Practice it and review mistakes in the second. Prepare independently before your laboratory booking. During the team session, rotate through operating, reviewing code, recording data and evaluating results. Each student completes an assessed contribution and explains their own work.

Equipment and language

The planned delivery model uses a laptop, browser, tested internet connection and hosted coding resources. Review the final technical checklist before buying equipment. Students should not purchase a robot or high-performance computer unless the written cohort requirements call for one.

Teaching language, available language support and class times will be stated for each cohort.

Curriculum

Twelve weeks of progressively deeper work.

Each weekly module is designed to end with a physical mission and evidence of learning.

Data collection and evaluation may require additional scheduled team time.

The cohort offer will explain physical-session recovery arrangements.

  1. Week 01

    Python and robot safety

    Mission or evidence

    Inspect status, execute approved movements and demonstrate the stop procedure.

  2. Week 02

    Joints and coordinates

    Mission or evidence

    Visit fixed targets and record repeatability.

  3. Week 03

    Remote operation

    Mission or evidence

    Move a lightweight object into a tray and explain a failed attempt.

  4. Week 04

    Cameras and observations

    Mission or evidence

    Use live views to select an object and document the decision.

  5. Week 05

    Demonstration quality

    Mission or evidence

    Record consistent examples and identify unusable data.

  6. Week 06

    Robot datasets

    Mission or evidence

    Inspect synchronized data and prepare a team dataset card.

  1. Week 07

    Learning from examples

    Mission or evidence

    Prepare guided training and explain model inputs and outputs.

  2. Week 08

    Supervised deployment

    Mission or evidence

    Test an approved model and record all trial outcomes.

  3. Week 09

    Evaluation

    Mission or evidence

    Measure success, timing and failure types with a defined test.

  4. Week 10

    Improvement

    Mission or evidence

    Collect targeted examples, retrain and compare versions fairly.

  5. Week 11

    Capstone integration

    Mission or evidence

    Connect task, code, data, model and evaluation.

  6. Week 12

    Demo Day

    Mission or evidence

    Demonstrate the project and explain contributions and limitations.

Portfolio and completion

Finish with evidence you can explain.

Your portfolio records the task you investigated, your contribution, code and dataset references, experiment results, and what you would improve. It includes a short demonstration and an individual explanation.

Completion is based on assessed work, required safety checks and individual understanding—not attendance alone. A well-analyzed failed experiment can show meaningful learning. An ON Robotics completion record will identify the assessed skills and hardware actually used.

The planned Core uses the open-source LeRobot ecosystem as a teaching tool. ON Robotics supplies the curriculum, supervised remote-lab delivery and assessment. Tool use does not imply a partnership or endorsement by its creators.

Tuition

Next-cohort tuition will be published when registration opens. Before any payment, families will receive the total price and a written description of what is included. Advanced programs and future travel opportunities will be priced separately unless expressly included in the offer.

Register Interest