3.5.37 · D4 · HinglishGuidance, Navigation & Control (GNC)

ExercisesH∞ control — robust to uncertainty (intro)

2,987 words14 min read↑ Read in English

3.5.37 · D4 · Physics › Guidance, Navigation & Control (GNC) › H∞ control — robust to uncertainty (intro)

Shuru karne se pehle, ek reminder un symbols ki jo hum use karenge, simple shabdon mein:


Level 1 — Recognition

Exercise 1.1 (L1)

Ek stable system ke liye hai. Ek sentence mein, yeh kya physical fact batata hai?

Recall Solution

YEH kya kehta hai: koi sinusoidal disturbance exist karta hai jiska output energy , input energy se guna hai (yaad karo = signal ki total energy, , symbols box mein define kiya gaya hai), aur koi bhi disturbance se zyada amplify nahi hoti. KYUN: — literally worst-case energy gain, output-energy aur input-energy ka biggest ratio har possible disturbance par. Toh amplification par ek ceiling hai aur ek aisi ceiling jo actually reach bhi hoti hai. In words: "sabse buri sine wave chaar guna loud ho jaati hai; koi cheez isse buri nahi hoti."

Exercise 1.2 (L1)

Inmein se kaunsa scalar stable ke liye ke barabar hai? (a) , (b) , (c) .

Recall Solution

Answer: (c). (a) DC gain hai — response sirf par (ek constant input). Yeh har doosri frequency ko ignore karta hai. (b) frequency par ek average hai. Averages peak ko smooth kar dete hain. (c) peak hai, aur peak wahi matter karta hai kyunki sabse buri disturbance apni energy exactly wahin concentrate karti hai jahan sabse bada hota hai (parent note se Parseval argument).


Level 2 — Application

Exercise 2.1 (L2)

Lightly damped mode ke liye (, ), resonant-peak formula se estimate karo:

Recall Solution

Step 0 — check karo ki formula apply bhi hoti hai. Kyun? Yeh resonant-peak formula maan leti hai ki ek genuine peak exist karta hai, jo sirf ke liye hota hai. Isse zyada damping mein magnitude sirf monotonically roll off karti hai (koi peak nahi), aur tab hota hai. Yahan , toh ek true resonant peak exist karta hai — achha hai. Step 1 — identify karo. Kyun? Standard form hai . Match karte hain: ; ; DC gain . Step 2 — plug in karo. Peak formula kyun? Kyunki , ka peak hai, aur lightly damped second-order mode ke liye peak ke paas hota hai jiska height hota hai. Toh : rad/s par ek resonant disturbance lagbhag paanch guna amplify hoti hai. Figure mein kya dekhna hai: lavender curve hai. Notice karo yeh low frequency par ke paas rehti hai (mint dotted DC line), phir par ek sharp coral dot tak rise karti hai — us dot ki height () poora H∞ norm hai. Sab kuch left aur right mein chota hai; sirf us single spike ki height matter karti hai. Isliye "peak, not average" sahi reading hai.

Figure — H∞ control — robust to uncertainty (intro)

Exercise 2.2 (L2)

Actual actuator gain hai. Uncertainty ko likho jahan , phir Small-Gain Theorem se largest nominal loop peak dhundho jo robustly stable guarantee kare.

Recall Solution

Step 1 — normalise karo. Kyun? Small-Gain Theorem uncertainty ko unit ball ke andar chahta hai, toh hum size bahar nikaalte hain: real uncertain block hai. Step 2 — small-gain apply karo. Aise sab blocks ke liye stability tabhi hogi jab loop-gain product ek se kam ho: Toh ke andar koi bhi actuator error tolerate ki jaati hai agar nominal loop ka peak gain us channel mein se kam ho. YAHAN kya mila: ek scalar inequality infinite family of plants ko certify karti hai.


Level 3 — Analysis

Exercise 3.1 (L3)

Tumne sensitivity weight place kiya aur achieve kiya. rad/s par weight ka magnitude hai. Yeh par kya ceiling force karta hai, aur us frequency par tracking error ke liye iska kya matlab hai?

Recall Solution

Step 1 — norm inequality ko unpack karo. matlab product har frequency par. Kyun har frequency? Kyunki -norm peak hai; agar peak se kam hai, toh sab frequencies se kam hain. Step 2 — ke liye solve karo. par: Interpretation: tracking error rad/s par reference/disturbance amplitude ka zyada se zyada hai. Weight literally ceiling draw karta hai jiske neeche rehna chahiye. Figure mein kya dekhna hai: coral curve ceiling hai — ek wall jise kabhi cross nahi kar sakta. Lavender curve ek feasible hai; dekho kaise yeh har jagah coral ceiling ke neeche rehti hai. Mint dot mark karta hai: wahan ceiling par hai, toh ke neeche squeeze hoti hai. Picture padhna: jahan bhi weight tall banao, ceiling low press ho jaati hai aur tight tracking force hoti hai.

Figure — H∞ control — robust to uncertainty (intro)

Exercise 3.2 (L3)

Ek colleague kehta hai: "Chalte hain ko se tak sab frequencies par se neeche push karte hain." Bode sensitivity integral (waterbed) use karke explain karo yeh kyun impossible hai.

Recall Solution

Step 0 — assumptions state karo. Pehle kyun? Identity universal nahi hai — yeh tab hold karti hai jab open-loop transfer function stable ho (koi right-half-plane poles nahi), jiska relative degree kam se kam ho (taaki itni jaldi ho ki integral converge kare), aur jisme koi right-half-plane zeros nahi hon. RHP poles right-hand side ko positive value tak raise kar dete hain, waterbed aur bura kar dete hain. Yahan hum benign stable, minimum-phase case assume karte hain toh right side exactly hai. Step 1 — integral padho. Bode Sensitivity Integral (waterbed) se, ke neeche signed area par fixed hai. Jahan wahan (negative area, "achha"); jahan wahan (positive area, "bura"). Step 2 — contradiction argue karo. Agar har jagah ho, toh har jagah hoga, toh integral ek bada negative number hoga, nahi. Toh yeh conservation law violate karta hai: yahan neeche push karo, toh kahin aur se upar pop up karna hi padega — waterbed. Tum sirf ko shape kar sakte ho, globally shrink nahi kar sakte.


Level 4 — Synthesis

Exercise 4.1 (L4)

Ek first-order sensitivity weight design karo taaki:

  • steady-state error (yaani ),
  • peak sensitivity (yaani high frequency par),
  • bandwidth rad/s.

aur dhundho, aur low- aur high-frequency ceilings state karo.

Recall Solution

Step 1 — low frequency (). Yahan kyun dekhein? Steady-state tracking DC se set hoti hai. par ceiling hai. Hum chahte hain, toh choose karo. Step 2 — high frequency (). Yahan kyun dekhein? Peak-sensitivity spec high par rehti hai. Wahan ceiling hai. Hum chahte hain, toh choose karo. Step 3 — exact crossover dhundho, phir justify karo. Kyun? Bandwidth woh jagah hai jahan weight ka magnitude se pass karta hai; humein woh frequency derive karni hai, assert nahi. set karo, yaani : Exactly solve karo: plug in karo: aur , toh Kyun pehle wala "" sirf rough tha: correction factor , ke barabar hota hai sirf ideal limit mein. ke saath term negligible nahi hai — yeh crossover ko se lagbhag upar kheencha hai. Toh honest statement hai: crossover rad/s hai, ke paas lekin equal nahi; tiny ise barely move karta hai, modest ise noticeably move karta hai. Result: Ceilings: low-freq (1% error ✓), high-freq (peak ✓). Agar ek controller achieve kare, toh teeno specs simultaneously meet hote hain. Figure mein kya dekhna hai: lavender curve ceiling hai. Yeh mint line ke paas (tracking ke liye 1% floor) se start hoti hai, ke paas se guzarti hai (butter dotted line), aur coral line (peak allowance) par flatten ho jaati hai. Isko padhna: is ceiling ki shape exactly woh performance spec hai jo ek wall ki tarah draw ki gayi hai.

Figure — H∞ control — robust to uncertainty (intro)

Level 5 — Mastery

Exercise 5.1 (L5)

Ek rocket loop mein nominal complementary sensitivity hai jiska peak hai. Plant mein multiplicative output uncertainty hai jahan aur interest ke band mein scalar weight hai. Is uncertainty structure ke liye robust-stability condition hai . (a) Kya loop robustly stable hai? (b) Sabse badi uncertainty size kya hai jo yeh loop tolerate kar sakta hai? (c) Agar hota, toh tum kya conclude karte, aur kaunsa vault tool conservatism reduce karta hai?

Recall Solution

(a) Condition check karo. kyun? Multiplicative output uncertainty ke liye ke saath feedback-mein-loop ka forward block hai; Small-Gain Theorem phir demand karta hai ki uska peak se kam ho. Kyunki yahan constant hai, Robustly stable. (b) Sabse badi tolerable uncertainty. solve karo: Toh loop in frequencies par nominal plant ki 125% tak multiplicative uncertainty tolerate karta hai guarantee fail hone se pehle. (c) Agar hota: tab hota, toh sufficient small-gain test fail ho jaata — hum ab robust stability certify nahi kar sakte. Lekin small-gain ki structure ignore karta hai aur aksar conservative hota hai; woh tool jo ise tighten karta hai guarantee rakhte hue hai μ-synthesis (structured uncertainty), jo plain peak ki jagah structured singular value use karta hai.

Exercise 5.2 (L5)

Performance aur robustness combine karo. Tumhe aur chahiye, jahan (Sensitivity and Complementary Sensitivity (S+T=1) se). Ek frequency par, maano tum demand karte ho. Sabse chota possible kya hai, aur kya yeh robustness weight ke saath compatible hai?

Recall Solution

Step 1 — algebraic identity use karo. Kyun? aur free nahi hain; har frequency par complex numbers ki tarah. Toh , aur reverse triangle inequality se magnitude neeche se bounded hai: Toh ki sabse choti possible value hai. Worst-case phase remark: value tabhi attain hoti hai jab real aur positive ho (phase ). Agar mein nonzero phase ho, toh larger ho sakta hai — jaise agar toh . Toh ek floor hai, aur honest robustness check mein worst-case use karna padega, jo se zyada ho sakta hai. Step 2 — floor par robustness test karo. Sabse chote use karke: Compatible — tightest par bhi, robustness product safely se kam hai. (Agar ka phase ko tak push karta, product hota, phir bhi se kam, toh yeh design saari phases mein robust hai.) Sabak: tiny error demand karna ( chota) ko ke paas force karta hai — tum dono ko ek hi frequency par chota nahi kar sakte. Yahan toh sabse chota bhi robustness margin chhodata hai kyunki weight sirf hai. aur chota karo aur ; agar tab se zyada ho jaaye, robustness toot jaayegi. Yahi performance–robustness trade-off quantitative roop mein hai.