Visual walkthrough — Constraints using Lagrange multipliers
2.1.10 · D2· Physics › Analytical Mechanics › Constraints using Lagrange multipliers
Shuru karne se pehle, ek honest promise: neeche sab kuch geometry hai. Poori derivation arrows aur un flat sheets ki kahaani hai jinpe woh slide kar sakte hain. Yeh image apne dimag mein rakho.
Step 1 — Ek configuration ek made-up space mein ek single point hai
KYA: hum "ek chalti system" ko "coordinate space mein ek chalte dot" se replace karte hain.
KYU: kyunki jab sab kuch ek space mein dot ho jaata hai, toh constraints shapes ban jaate hain aur forces arrows ban jaate hain. Isse physics, geometry mein badal jaati hai — jise hum draw kar sakte hain.
PICTURE: figure do axes draw karta hai (hum use karte hain taaki paper pe fit ho) aur ek orange dot — poori machine, abhi is waqt.
Step 2 — Ek constraint ek curve hai jis par dot rehna chahiye
KYA: humne equation ko plane ke through ek green curve ke roop mein draw kiya.
KYU: is method ka poora point yahi hai ki constraint ko visible rakha jaaye, use clever coordinates ke andar chhupaane ke bajaye. Toh hume literally woh surface dekhni chahiye jis par dot trapped hai.
PICTURE: green curve = . Orange dot us par baitha hai. Curve se bahar jaana forbidden territory hai (shaded gray). Dimag mein rakho: radius ka hoop, toh — curve khud circle hai.
Step 3 — Gradient: surface ke seedha bahar jaata ek arrow
KYA: dot par, humne red arrow draw kiya.
PERPENDICULAR KYU? Surface ke saath ek tiny step lo — nahi badlega, toh us direction mein iska slope zero hai. Nonzero slope wali ek hi direction hai woh hai surface ke across. Gradient slopes collect karta hai, toh woh us across-direction ke saath align ho jaata hai. Yahi poora reason hai ki normal force sirf ek hi direction mein point kar sakti hai.
PICTURE: green curve, red gradient arrow perpendicularly bahar shoot karta hua, aur ek faint blue arrow curve ke saath flat leta hua (allowed direction — Step 4).
Recall "
" kyun, "" kyun nahi? Kyunki ek saath kai 's par depend karta hai. ka matlab hai "sirf ko wiggle karo, baaki ko freeze karo." Yeh single-variable wiggle exactly wahi hai jo " direction mein slope" chahiye. ::: partial derivative = ek axis ke saath slope jab baaki held still hain.
Step 4 — Allowed wiggles: virtual displacements jo surface ke tangent hain
KYA: humne ko green curve par flat lete hue ek chhote blue arrow ke roop mein draw kiya.
TIME FREEZE MOVE KYU? Real motion surface ko idhar-udhar khich sakti hai; hum test karna chahte hain "abhi is waqt available moves mein se, kaun si legal hain?" ko freeze karna geometry ko clock se alag karta hai.
PICTURE: blue curve ke tangent; red perpendicular. Woh par milte hain — woh right angle agle step ka key fact hai.
Step 5 — d'Alembert hume ek doosra perpendicular arrow deta hai
KYA: hum poore bracket ko naam dete hain — equations of motion ka "leftover". Unhe ek arrow mein stack karo.
YEH ZERO KYU HOTA HAI? Ek free system ke liye har independent hota, toh har khud hi vanish karna padta — woh ordinary Euler–Lagrange equation hai. Lekin ek constraint ke neeche chained hote hain (Step 4), toh hum sirf yeh conclude kar sakte hain ki poora sum zero hai.
YEH KAISA DIKHTA HAI: sum ka zero hona hai — arrow bhi blue allowed direction ke perpendicular hai.
Step 6 — Same line ke ⟂ do arrows parallel hone chahiye — aur paida hota hai
KYA: hum set karte hain, component by component.
YEH FORCED KYU HAI (CHOOSE NAHI KIYA): parallelism yahan ek theorem hai, assumption nahi. Ek hi freedom bachi hai woh hai length ratio, aur woh single unknown number Lagrange multiplier hai.
PICTURE: red aur thoda lamba red same line par draw kiye gaye; ek bracket unke length ratio ko label karta hai.
Step 7 — Counting: equations, unknowns — constraint rent pay karta hai
KYA: hum green curve ki apni equation wapas pile mein add karte hain.
KYU: har unknown ko ek equation chahiye. Extra unknown jo humne banaya woh exactly us extra equation se balance hota hai jo hum sab along carry kar rahe the. Balanced ledger.
PICTURE: ek chhota tally — EL rows blue mein, constraint row green mein, coordinate unknowns + multiplier unknown — arrows unhe match up karte hue.
Step 8 — Edge & degenerate cases (reader ko kabhi stranded mat chhodna)
Case B — gradient vanish ho jaata hai (). Tab "off-surface" direction undefined hai — constraint us point par degenerate hai (jaise at ). Method ke paas kuch point karne ko nahi, toh aur wahaan koi force recover nahi ki ja sakti. Fix: ko rewrite karo taaki uska gradient nonzero ho ( use karo, nahi).
Case C — tumne already coordinate eliminate kar liya. Agar tumne constraint ko independent coordinates mein embed kar liya, toh (koi redundant nahi bachi differentiate karne ke liye), zero se multiply ho jaata hai aur meaningless hai. Fix: redundant coordinate rakho jab bhi constraint force chahiye.
Case D — velocity-only (non-holonomic) constraints. Agar constraint hai aur kisi bhi mein integrate nahi ho sakti, toh koi surface nahi aur koi gradient nahi. Tum velocity form use karte ho jahan coefficients woh role play karte hain jo gradient ne play kiya. Dekho Holonomic vs Non-holonomic Constraints.
Recall "gradient = λ · gradient" pehle kahaan dekha hai?
Yeh constrained optimization ka exact skeleton hai: constrained extremum par, . Woh equality constraints ke saath KKT Conditions hai. Mechanics aur optimization geometry share karte hain: leftover constraint ke normal ke parallel hai. ::: same parallel-gradients picture, alag words.
Ek-picture summary
Upar sab kuch yeh ek image hai: ek green surface, us ke tangent ek blue allowed-direction, aur do red arrows ( physics se, geometry se) jo same perpendicular line par lie karne ke liye forced hain — unka length ratio hai, aur woh push hai jo surface deliver karta hai.
Recall Feynman: 12-saal ke bacche ke liye poora walkthrough
Ek curved rail mein marble socho. Rail ek green line hai jise marble kabhi nahi chhodh sakta. Abhi marble sirf rail ke saath slide kar sakta hai — use blue direction kaho. Do alag arrows seedhe rail ke across point karte hain: ek hai "physics leftover" (jo marble ki motion demand karti hai), doosra rail ka apna "mujhse door kaun si taraf hai" arrow. Flat 2D mein rail ke seedhe across sirf ek direction hai, toh dono arrows use par lie karne chahiye — unke sirf alag lengths hain. Woh length ratio ek chhota honest number hai. Aur yahan payoff hai: rail marble ko sirf sideways push kar sakti hai, seedhe apne aap ke across — same red direction — toh literally rail kitna hard push karta hai woh hai. dekho: jab woh zero hota hai, rail pushing band kar deti hai aur marble ud jaata hai.