Loading system evidence
Loading system evidence
Learn where AI speeds up ROS 2 work and where it will crash your robot, by fixing the code an LLM actually gets wrong.
Sign in to start - freeOutcome
Build
An AI-assisted ROS 2 node (business logic from the model, real-time and safety structure owned by you) repaired concept by concept.
Sample incident
Fix the QoS the LLM left off so the sensor publisher matches its subscriber.
Full syllabus
An LLM writes plausible rclpy fast, but it drops the ROS 2 specifics (QoS, executors, lifecycle) that decide whether nodes actually talk.
AI is fastest at boilerplate (launch files, URDF, .msg) but it hallucinates physics values and reaches for deprecated Gazebo Classic tags.
MCP servers let an LLM agent call ROS tools directly. That is dangerous when a tool publishes without validating what it sends.
AI reads logs and explains tf, QoS, and lifecycle errors well. You close the loop by verifying its fix against the running system.
Un-grounded LLMs hallucinate APIs and mix Humble and Jazzy. Retrieval over the actual docs kills both.
LLMs write code that runs, not code that meets a deadline. In a control loop, that difference is a crash.
LLMs and VLMs plan well but hallucinate perception. Close the loop with real sensors before you act.
Put it together: an AI-assisted node with a persisted checkpoint and a safe, idempotent recovery path.
Playgrounds
Small, functional experiments that reveal the math and evidence behind this course’s failures. Open them alongside the labs.
Add up system, history, and user tokens against the context window, leaving room for the reply, and see when a request overflows.
context window / token budget / LLM prompt
Live controlsValidate a model's tool call against a JSON schema: required parameters, argument types, extra properties, and malformed JSON.
tool use / JSON schema / function calling
Live controlsTune chunk size, overlap, and top-k over a document and see how a boundary-spanning answer is lost when the overlap is too small.
RAG / chunking / retrieval recall