3.5.53 · D5 · HinglishGuidance, Navigation & Control (GNC)

Question bankPowered descent guidance — G-FOLD algorithm (convex optimization)

2,153 words10 min read↑ Read in English

3.5.53 · D5 · Physics › Guidance, Navigation & Control (GNC) › Powered descent guidance — G-FOLD algorithm (convex optimiza

Shuru karne se pehle, do words jo tumhe pin karke rakhne chahiye (neeche sab kuch inhi par tika hai):

Recall Convex set / convex function (ek-line refresher)

Convex set woh hota hai jisme kisi bhi do points ke beech ki seedhi line andar hi rahti hai. Convex function bowl-shaped hoti hai: uska ek lowest point hota hai, koi false valley nahi. Dekho Convex Optimization aur Second-Order Cone Programming. G-FOLD ka poora point yahi hai ki dono constraints (sets) aur cost (function) ko convex banao taaki solver global minimum tak pahunche.


Sach ya jhooth — justify karo

Mass equation kehti hai ki lander engines off hone par bhi mass khoता hai.
Jhooth. Engines off hone par , isliye — koi exhaust nahi, koi mass loss nahi. Mass tabhi girti hai jab thrust nonzero ho. ( ek fixed constant hai, isliye ye akele kabhi loss nahi karta.)
Total thrust minimize karna fuel minimize karne ke barabar hai.
Sach true thrust ke liye, lekin trap ye hai ki thrust ko pointwise minimize karna (har jagah low rakhna). Ek lamba, gentle burn jo gravity se zyada der tak ladte hue karta hai, ek short hard burn se zyada total propellant burn karta hai — gravity loss. Fuel integral hai, peak nahi.
Constraint (upper bound) hi problem ko non-convex banata hai.
Jhooth. Ek sphere ka andar convex hota hai, isliye upper thrust-ceiling bound theek hai. Non-convex woh lower bound (thrust floor) hai — sphere ke bahar ka region — jo non-convex hai.
Lossless convexification ke baad solver aisa solution return kar sakta hai jisme ho (slack unused).
Optimum par Jhooth. Cost directly ko penalize karti hai, isliye optimizer ko tab tak squeeze karta hai jab tak wo ke barabar na ho jaye. wala koi bhi interior point strictly worse hai aur reject ho jata hai — yahi Pontryagin Minimum Principle ki guarantee hai.
Change of variable cost ko nonlinear banata hai.
Jhooth. Ye mass dynamics ko linear banata hai (). Cost mein linear hai aur log substitution se untouched rehti hai.
Solve karne se pehle flight time fix karna optimality kho deta hai.
Jhooth. Har fixed ke liye hume exact convex optimum milta hai; phir hum ke saath outer 1-D search karte hain. Fuel-vs- curve unimodal hai, isliye sweep sach mein best dhundh leta hai convexity tode bina.
Ek convex problem mein phir bhi kai equally-good landing solutions ho sakte hain.
Sach. Convex ka matlab hai koi worse local minima nahi, lekin optimal points ka set flat ho sakta hai (tie). Jo guarantee hai woh ye hai ki har returned optimum ka globally-best cost same hoga — tum kabhi inferior valley mein nahi phansoge.
Glide-slope constraint ki wajah se non-convex hai.
Jhooth. bas ek fixed positive number hai (ek slope), aur target frame mein position components hain. Ye constraint ek norm ek linear function hai — ek convex second-order cone. Ye SOCP mein free mein fit ho jata hai.

Error dhundho

"Humne ko tak relax kiya, isliye model real engine ko ab represent nahi karta."
Error ye hai: relaxation sirf optimum ke bahar loose hai. Optimum par inequality active hoti hai (), exactly true engine physics recover karti hai. Kuch bhi nahi khoता — isliye lossless.
" ko define kiya gaya hai, isliye ye bas state ka ek fixed function hai — real variable nahi."
Error ye hai: woh control hai jo hum choose kar rahe hain, isliye (acceleration-magnitude slack) ek genuine decision variable hai. Convexification ke baad sirf se inequality ke zariye linked hai, optimizer ko freedom deta hai jise proof phir pin kar deta hai.
" ko se divide karo aur equation mein abhi bhi hai, isliye ye abhi bhi nonlinear hai."
Error ye hai: divide karne se milta hai jahan naya control hai aur constant gravity vector hai. ko ki definition mein absorb kar liya gaya hai; equation ab chosen variables mein linear hai.
" ka Taylor expansion ek approximation hai, isliye G-FOLD ka answer sirf approximate hai."
Ye partly trap hai. Floor ko reference log-mass ke baare mein second order tak expand kiya gaya hai: . Kyunki convex hai, uska second-order Taylor polynomial ek upward parabola hai — khud convex — isliye constraint convex rehti hai. Ye ke paas tight hai, exactly wahan jahan true trajectory ka mass rehta hai, aur tighten karne ke liye re-reference kiya ja sakta hai.
"Minimum-fuel descent ko smooth landing ke liye poore raste gently throttle karna chahiye."
Error ye hai: minimum-fuel typically bang-bang hota hai — coast/min-thrust, phir end ke paas ek hard full-thrust brake ("suicide burn"). Smooth gentle throttling extra fuel burn karta hai gravity se zyada der tak ladte hue.
"Kyunki interior-point methods iterative hain, G-FOLD global optimum guarantee nahi kar sakta."
Error ye hai: ek convex program ke liye, interior-point methods guaranteed polynomial time mein global optimum tak converge karte hain. Convexity, iteration nahi, global guarantee deti hai.

Why questions

Mass ka logarithm kyun lete hain, bas use kyun nahi karte?
Kyunki log-derivative hai . set karne se messy mass dynamics bilkul linear mein badal jaati hai (jahan ) — logs division ko subtraction mein convert karte hain.
Descent ke dauran global optimum (sirf ek achha local nahi) itna important kyun hai?
Trajectory commit karne se pehle roughly ek second compute karne ke liye hota hai. Ek non-convex solver false valley return kar sakta hai ya converge karne mein fail ho sakta hai; ek convex solve reliably har baar single best answer return karta hai, jo safety demand karti hai.
Fuel cost ko small kyun "chahti" hai, aur us fact ka kya matlab hai?
Cost hai, isliye smaller (acceleration-magnitude slack) matlab kam fuel. Woh downward pressure exactly hi hai jo ko uske lower bound par drive karta hai, lossless relaxation ko true equality par wapas collapse karta hai.
Hum ke upar bahar se search kyun karte hain instead of andar optimize karne ke?
ko andar vary karne se discretized dynamics bilinear ho jate hain (unknowns ke products), convexity destroy ho jaati hai. Bahar ek unimodal curve par 1-D sweep ke roop mein rakha, har inner solve ki convexity preserve hoti hai.
Fuel-versus-flight-time curve unimodal (ek minimum) kyun hai?
Bahut chhota samay mein brake karne ke liye violent, near-max thrust demand karta hai — heavy fuel burn (aur eventually infeasibility); bahut lamba extra seconds tak gravity ke khilaf hover karne mein propellant waste karta hai. Fuel ek sweet spot ke aas-paas girta phir badhta hai, isliye curve mein ek single dip hai — 1-D search se safely bracket kiya ja sakta hai. (Ye closed form mein prove karne ki bajay numerically per problem verify kiya jata hai.)
Hum thrust kyun cap nahi kar sakte aur lower bound bhool kyun nahi jaate?
Real engines physically floor se below throttle nahi kar sakti bina flame out kiye. Ise ignore karna ek aisa solution deta hai jo hardware execute nahi kar sakta; convexification hume floor rakhne deti hai convex rehte hue.
Fuel minimize karna final mass maximize karne ke barabar kyun hai?
Fuel spent equals initial mass minus final mass, aur initial mass fixed hai. Isliye kam fuel burned ⇔ touchdown par zyada mass bacha — dono objectives same direction mein point karte hain.
G-FOLD Apollo/Falcon-style "late burn" behaviour ko bina bataye kyun reproduce karta hai?
Ye dynamics ke under minimize karne se naturally nikalta hai — thrust delay karna gravity se ladte hue time kam karta hai (gravity loss). Dekho Apollo Lunar Descent Guidance aur SpaceX Falcon 9 Landing.

Edge cases

Agar available deceleration gravity se kam ho ()?
Yahan engine ceiling hai aur gravity magnitude; best upward acceleration downward ko overcome nahi kar sakta, isliye lander apna fall nahi rok sakta — problem infeasible hai. G-FOLD ek fake landing ki jagah infeasibility report karta hai, jo sahi safe outcome hai.
Jab thrust exactly ho (engine apne floor par) us instant kya hota hai?
Throttle-box lower constraint active ho jaata hai. Ye convex box ka ek valid, feasible edge hai — solver ise kisi bhi active constraint ki tarah handle karta hai, koi special casing nahi.
Agar target lander ke directly neeche ho (purely vertical descent)?
Glide-slope cone degenerate ho jaata hai: trivially satisfied hai kyunki horizontal offset ~0 hai. Problem 1-D vertical landing mein reduce ho jaati hai — ek valid limiting case.
ka glide-slope cone ke liye kya matlab hai?
, isliye horizontal-offset bound unlimited ho jaata hai — cone fully khul jaata hai aur koi restriction impose nahi karta. Physically, "koi bhi approach angle allowed hai."
ka kya matlab hai?
force karta hai , yaani target axis ke along purely vertical descent. Cone ek line mein collapse ho jaata hai — extremely restrictive lekin abhi bhi convex.
Agar initial velocity sahi altitude aur position par already zero ho?
Trajectory already ek soft pinpoint state hai; minimum-fuel solution ko bas ek hover-then-touch ya immediate zero divert chahiye, aur cost integral essentially woh propellant hai jo zameen tak gravity ke against hold karne ke liye chahiye.
Agar do alag flight times near-identical fuel dein?
Unimodal fuel curve apne minimum ke paas flat hai, isliye kai tie karte hain. Unme se koi bhi acceptable hai; woh choose karo jo extra margin de (jaise actuator response ke liye thoda zyada time).
Recall Poore trap set ka ek-line summary

Non-convexity sirf thrust lower bound mein rehti hai; mass linearize karta hai; -relaxation lossless hai kyunki cost push karti hai; bahar rehta hai; optimum bang-bang hota hai; aur har degenerate cone/thrust case phir bhi ek convex, globally-solvable program ke andar land karta hai.