2.1.10 · D5Analytical Mechanics

Question bank — Constraints using Lagrange multipliers

2,049 words9 min readBack to topic

Before the traps, we pin down every symbol and picture — everything on this page leans on these.


True or false — justify

Multipliers let you keep the constraint force instead of throwing it away.
True — the embedded (reduced-coordinate) method makes constraint forces do zero virtual work and vanish, whereas the multiplier is that force, kept on purpose (see figure s02).
If you use good generalized coordinates, still gives you the tension.
False — once you eliminate the constraint you no longer have an in those coordinates, so and there is no to read a force from.
The multiplier is always dimensionless.
False — must have units of generalized force, so 's units are set by ; if has length units, is a force.
is a single fixed constant for the whole motion.
False — is a function of time; the constraint force changes as the motion proceeds (e.g. varies with and ).
The constraint force always points along the direction of motion.
False — it points along (i.e. ), which is perpendicular to the allowed motion (the surface ); that is exactly why it does no virtual work under embedding.
With constraints and coordinates (as defined above) you still have exactly as many equations as unknowns.
True — you get Euler–Lagrange equations plus constraint equations, for the coordinates plus multipliers: .
A holonomic constraint reduces the degrees of freedom by one; the multiplier method reduces them by zero.
True in bookkeeping — the multiplier method keeps all coordinates (dependent ones included) and adds , trading a smaller coordinate count for direct access to the constraint force. See Generalized Coordinates and Degrees of Freedom.
Non-holonomic (velocity) constraints can always be handled by writing some and taking its gradient.
False — a genuinely non-holonomic constraint is non-integrable, so no position function exists; you must use the velocity form directly. See Holonomic vs Non-holonomic Constraints.
The sign of carries physical information.
True — its sign tells you the direction of the constraint force (e.g. a rope can only pull, so a wrong sign flags the constraint about to be violated / object leaving the surface). See the sign-convention figure s04.

Spot the error

"Under a constraint we can set each bracket of the d'Alembert sum to zero, just like the free case."
Error — the virtual displacements (imagined time-frozen nudges along the surface) are no longer independent; they must satisfy , so a weighted sum being zero does not force each term to zero.
"I eliminated by setting first, then added to find the normal force."
Error — after substituting the coordinate is gone and identically; there is no free to vary, so you cannot recover . Keep free until after differentiating.
"For a mass hanging from a string wound on a cylinder ( = drop, constraint ), the tension equals itself, so I report ."
Error — the generalized force on is , which equals because the string pulls opposite to the drop-coordinate ; the physical tension is (see the sign diagram s04).
"I found the Euler–Lagrange equations but is undetermined — the method failed."
Error — you forgot the th equation, the constraint itself; that closes the system and pins down .
"The gradient and the friction force point along the incline, so friction is tangential and handles it as usual."
Subtle — for rolling, the constraint is whose gradient lives in the coordinate space, not physical space; the resulting correctly delivers the tangential friction because that is the force enforcing no-slip. See Normal Force and Tension as Constraint Forces.
"Since a normal force does no work, must be zero."
Error — doing no virtual work means the force is perpendicular to allowed displacements, not that its magnitude is zero; is precisely the nonzero magnitude of that perpendicular push.
"I can use the reduced Euler–Lagrange equations from Euler-Lagrange Equations and still read off ."
Error — reduced equations have already used up the constraint; appears only when the redundant coordinate and its term are retained.

Why questions

Why does a multiplier appear at all, geometrically?
The EL-bracket vector is the collection of left-hand sides stacked into one vector, one entry per coordinate. The allowed nudge is perpendicular to both this bracket vector and (figure s03); by the linear-algebra fact above (two arrows perpendicular to the same line are parallel), bracket for some scalar .
Why do we multiply the constraint variation by and add it, rather than substitute?
Adding a zero (since ) changes nothing physically but lets us choose to kill the one dependent coordinate's bracket, after which the remaining are independent. This is the same trick as d'Alembert's Principle and Virtual Work.
Why is the direction of the constraint force and not something else?
The gradient of points perpendicular to the surface , and a constraint force is exactly what pushes a body off/onto that surface — perpendicular to it — so the force must be proportional to .
Why can the embedded method never tell you when the bead leaves the hoop?
Leaving the hoop is the event ; the embedded method has discarded entirely, so it has no expression to set to zero.
Why does the multiplier method give equations for a single constraint?
EL equations (one per retained coordinate) plus the constraint equation , matching the coordinates plus the extra unknown .
Why is Lagrange-multiplier mechanics conceptually the same idea as constrained optimization?
Both enforce a constraint by adding and stationarizing; the multiplier measures sensitivity to the constraint. See the inequality-constraint generalization in KKT Conditions — and the concrete mechanical analogue in the edge cases below.
Why must the constraint be differentiable in the coordinates for this to work?
We need to exist to form the constraint-force direction; a non-smooth constraint has no well-defined gradient and the method breaks at the kink.

Edge cases

At the instant for the bead, what does do?
It passes through zero and would go negative if the hoop could only push inward; the sign flip signals the bead physically separating, so the model is only valid up to (this is exactly a mechanical KKT "inactive constraint": the one-sided contact drops out when would change sign).
What happens to for a pull-only string when the computed would make the string push?
The constraint is no longer active — the string goes slack — and you must drop the constraint (set ) rather than trust a nonphysical negative tension; this is the mechanics version of a KKT constraint switching off (see figure s04).
If the moment of inertia in the rolling/pulley problem, what does the tension do?
; a massless cylinder offers no rotational inertia to react against, so no tension builds and the mass falls at .
If (infinitely heavy cylinder), what is and ?
and ; the cylinder won't turn, so the mass hangs essentially in static equilibrium with tension balancing gravity.
What if the constraint is time-dependent, (a moving support)?
The surface itself sweeps in time, so the constraint force now acts on a moving wall and can do real work; energy is not conserved and tracks a moving push (see figure s05 — the wall displaces the bead as it slides).
For a bead free on a frictionless straight wire (a one-line constraint that removes all curvature), what is the transverse ?
It equals whatever transverse force keeps the bead on the line (e.g. supporting its weight component); if no transverse applied force exists, — a degenerate but perfectly valid answer.
If two constraints become parallel (their gradients ), what breaks?
The two constraint surfaces touch tangentially so their normals coincide (figure s06); the combination can be split infinitely many ways, so and are individually undetermined — a badly posed (redundantly constrained) problem.
Recall One-line summary to keep

is the honest constraint force: keep the coordinate, add the constraint, read the push — and watch its sign to know when the surface lets go.