Learning outcomes
- Distinguish a plant, simulator, controller, and estimator.
- Formulate a measurable regulation or tracking objective.
- Explain why simulation success alone is insufficient.
Prerequisites: Linear algebra, ODEs, and earlier lectures in this sequence.
The question a controller answers
A controller chooses an input using available information. A robot model predicts the consequences of that input. These are separate objects, even when a learning algorithm trains the controller inside a simulator. For a deterministic continuous model write
For a robot, a convenient physical state is
Regulation versus tracking
Regulation brings the system to a fixed equilibrium
Define a scalar performance measure before tuning gains. For position tracking, report RMS error in metres, peak error, control effort with units, saturation fraction, and failures. A weighted cost such as
Worked example: a disturbed mass
Consider
An open-loop force computed from the nominal model cannot react to an unexpected disturbance. Feedback can react, but a noisy measurement or a delayed loop can also inject unwanted motion. We therefore evaluate perturbations, delay, and saturation explicitly.
The experimental contract
Fix the model, initial-state distribution, controller update interval, physics timestep, termination rules, and evaluation seeds. Run a baseline with the same information and force limits. Split tuning trials from final evaluation trials. Save the configuration and software version with the output, so an attractive trajectory can be reproduced.
The first practice inspects a simple MuJoCo model, advances it without a viewer, and verifies the dynamics force balance. Later practices compare controllers under the same protocol. The external courses provide broader examples of this modeling-to-control workflow CMU optimal control Tedrake, Underactuated Robotics.
Classroom exercise
A controller reports low average tracking error, but clips its torque in 40% of steps. What evidence is missing before claiming robustness?
Discussion guide: inspect peak errors, constraint violations, failure cases, disturbance response, and the tested operating region. Average error alone can hide rare loss of control. A finite test suite establishes empirical performance within that suite, not a global stability proof.