4.11 Standard Notation Used Throughout the Course

Core symbols¶

Symbol	Meaning	Typical dependence
$t,t_0,t_f$	time, initial time, final time	independent variable
$p$	time-independent plant variables	geometry, materials, ratings
$c$	time-independent controller parameters	gains, weights, horizons
$a$	architecture variables	binary, integer, categorical, placement
$x(t)$	differential state trajectory	governed by $\dot x=f$
$z(t)$	algebraic-variable trajectory	governed by $q=0$
$u(t)$	commanded or delivered control input	optimized or generated by $\pi$
$d(t)$	prescribed environment, reference, or disturbance	not selected in the nominal problem
$y_m(t)$	measured output	sensor model plus noise
$y_p(t)$	performance output	used in objectives or constraints
$\theta$	uncertain quantities	parameters, inputs, noise, model error
$L$	running objective integrand	accumulated over time
$\Phi$	terminal or endpoint objective	evaluated at boundaries
$g$	inequality constraints	feasible when $g\le0$
$h,q$	equality and algebraic constraints	feasible when equal to zero
$b$	boundary constraints	initial, final, or linkage conditions
$\pi$	control policy	maps available information to $u$
$\mathcal I_t$	controller information available at time $t$	measurements, estimates, preview

A dependency matrix showing which CCD quantities influence major model elements.

Conventions¶

Boldface is omitted when dimensions are clear. A superscript $*$ denotes an optimized value, not necessarily a proven global optimum. Bounds use superscripts $L$ and $U$ . A hat denotes an estimate, a tilde may denote an uncertain quantity, and a subscript $k$ denotes a discrete mesh or sample index. Scenario indices use $s$ .

The symbols are stable, but their dimensions are problem dependent. For example, $u(t)$ may be scalar motor voltage or a vector of turbine pitch and torque commands. Every application must state units, scaling, sign conventions, and whether a control variable is commanded or delivered.

Chapter summary¶

The unified formulation separates time-independent decisions, time-dependent trajectories, prescribed data, uncertainty, performance, dynamics, and feasibility. Plant and control decisions interact through shared equations and limits. Architecture changes what components and information exist. A complete CCD description also reports control representation, information availability, coordination, model fidelity, uncertainty, algorithm, and validation level.

Common mistakes¶

using the same symbol for a plant decision and a time-varying state;
optimizing a state or algebraic value without enforcing its governing equation;
assuming full state or disturbance knowledge without a sensor, estimator, or preview model;
confusing command, actuator output, and generalized plant input;
checking path constraints only at coarse sample points;
comparing architectures under different objectives or information; and
calling an uncertain variable deterministic merely because one nominal value was simulated.

Exercises¶

Write the complete deterministic CCD formulation for the positioner using PD gains and a selectable velocity sensor.
Replace PD gains with an optimized voltage trajectory and list the information assumption that changes.
Add uncertain payload mass and formulate expected energy plus a terminal-error chance constraint.
Construct a dependency matrix for link length, motor rating, gear ratio, sensors, states, control, objectives, and constraints.
Classify your formulation using every axis of the master CCD taxonomy.

Principal sources¶

The formulation-to-solution organization and graphical vocabulary follow the integrative wind-turbine CCD review by Bayat and coauthors. The general dynamic-system formulation follows Allison and Herber’s dynamic-MDO and plant-control co-design work. The uncertainty notation anticipates the UCCD taxonomy developed by Azad and Herber. All diagrams here are original course figures.

Open research question¶

Can a machine-readable CCD problem specification preserve physical meaning, information assumptions, architecture logic, uncertainty, and solver interfaces well enough to make formulations portable across domains and software ecosystems?

Activity 4.11: perform a notation audit¶

Activity 4.11: perform a notation audit

Choose a controlled engineering system and assign every relevant quantity to one row of the notation table. Identify any quantity that changes role between design time and operation time.

Quantitative audit for Standard Notation Used Throughout the Course: two complete positioner formulations give the following results.

Formulation	RMS error	Peak current	Dynamic defect	Hardware cost
A	0.024 rad	11.2 A	$3\times10^{-5}$	USD 820
B	0.018 rad	13.6 A	$8\times10^{-6}$	USD 1,050

Use $J=e_{\rm rms}^2+10^{-5}C$ , require current $\leq14$ A and defect $\leq10^{-4}$ .

Calculate objectives and constraint margins.
Increase B current by 7% and RMS error by 10% in validation; reassess feasibility and ranking.
Identify which plant, control, state, information, or architecture quantity causes the numerical trade.