Skip to article frontmatterSkip to article content
Site not loading correctly?

This may be due to an incorrect BASE_URL configuration. See the MyST Documentation for reference.

4.9 Continuous and Discrete Architecture Variables

Parameter design assumes the architecture exists

Changing a gear ratio or controller gain is parameter design. Deciding whether a gearbox, encoder, current sensor, or communication link exists is architecture design. Let aa represent discrete architecture choices:

a=[ag,aq,ai,av]T{0,1}4,a=[a_g,a_q,a_i,a_v]^T\in\{0,1\}^4,

where the entries select a gearbox, position sensor, current sensor, and velocity sensor. Categorical variables may select among component types or topologies.

Architecture changes equations, dimensions, available information, and feasible controllers. If av=0a_v=0, direct velocity feedback is unavailable unless an estimator reconstructs velocity. If ag=0a_g=0, gear-ratio variable NN should not remain active. The formulation must enforce such logical consistency.

Continuous architecture relaxations

Some architecture-like decisions are continuous: actuator placement coordinates, sensor orientation, material distribution, or communication bandwidth. Binary variables are sometimes relaxed to [0,1][0,1] to support gradient-based exploration. The relaxed result is a computational aid, not a fractional physical component, unless the variable has a valid mixture interpretation.

Conditional models

An architecture-dependent model may be written

fa=f(t,x,z,u,p,c,d;a),ym=S(as)x+n,f_a=f(t,x,z,u,p,c,d;a),\qquad y_m=S(a_s)x+n,

with component cost Ca(a)C_a(a) and logical constraints. Big-MM, complementarity, convex-hull, enumeration, and generative representations are possible implementation strategies; their numerical treatment is deferred to Chapter 8.

Activity 4.9: enforce architectural consistency