Visual walkthrough — Optimal guidance — ZEM - ZEV formulation
3.5.52 · D2· Physics › Guidance, Navigation & Control (GNC) › Optimal guidance — ZEM - ZEV formulation
Hum poore time exactly teen characters use karenge. Chalo inhe ek baar saaf saaf draw karte hain, kisi bhi maths se pehle:
- — abhi vehicle kahan hai (space mein ek dot, origin se dot tak ek arrow).
- — abhi kis direction mein aur kitni tez move kar raha hai (dot se attached ek arrow).
- — woh push jo hum control karte hain (thrust arrow — ek aur sirf ek cheez jo hum choose kar sakte hain).
Bold-face ka matlab bas itna hai ki "yeh ek arrow hai, iske paas direction hai, sirf size nahi." Ek samajhdar 12-saal-ka bachcha sochega: position ek jagah hai, velocity ek speed-arrow hai, acceleration ek dhakka hai. Bas yehi hain ka matlab.
Step 1 — Duniya draw karo: ek dot jo gravity ke neeche coast karta hai
KYA. Kuch bhi steer karne se pehle, vehicle ko kuch nahi karte hue dekho — engine off. Sirf gravity act karta hai. Yeh "kuch-nahi-karna" wala future hi poori trick hai.
KYUN. ZEM/ZEV ki genius yeh hai ki poochhte hain "agar main abhi steering band kar dun, toh main kahan pahunchta hoon?" Jawab dene ke liye pehle hume jaanna padega ki ek coasting dot kaise move karta hai. Woh motion hai double-integrator dynamics: acceleration ko ek baar integrate karo toh velocity milti hai, do baar integrate karo toh position milti hai.
PICTURE. Figure dekho. White dot par speed-arrow ke saath start karta hai. Engine off hone par woh pale-yellow dashed curve ke saath drift karta hai, jhukta hua kyunki gravity neeche ki speed add karti rehti hai.

Coasting dot (deadline par) ek aisi jagah aur speed par land karta hai jo hum countdown use karke school kinematics se predict kar sakte hain:
Har term ek picture hai: hai "speed times time = distance," classic straight coast; hai woh extra downward sag jo gravity produce karta hai.
Step 2 — Do errors ko naam do: ZEM aur ZEV
KYA. Compare karo jahan coasting dot pahunchta hai aur jahan hum chahte hain woh pahunche: target place aur target speed . Yeh gaps hamare do errors hain.
KYUN. Agar woh gaps zero hain, toh hume kuch karne ki zaroorat nahi — coasting already jeet gayi. Toh fuel jalaane ki sirf ek wajah hai in gaps ko close karna. Unhe naam dene se hum engine ko exactly us cheez ki taraf aim kar sakte hain jo galat hai.
PICTURE. Figure mein do arrows: chalk-blue arrow ZEM coast-landing spot se target spot ki taraf point karta hai (ek position gap). Chalk-pink arrow ZEV coast-arrival speed se target speed ki taraf point karta hai (ek velocity gap, speed-diagram inset mein drawn).

ZEM formula ko term by term padho: target se shuru karo, phir subtract karo woh sab kuch jo free coast already deta hai (, drift , sag ). Jo bacha woh gap hai jo engine ko fill karna hai.
Step 3 — Sachcha ending likho, engine included
KYA. Ab engine on karo. Commanded acceleration baaki seconds mein koi bhi wiggle ho sakti hai. Hum isse likhte hain, jahan ek dummy time variable hai jo flight ke across sweep karta hai — yeh abhi se, , deadline tak, , yaani chalta hai. Final speed aur final place par iska effect add karo.
KYUN. Hum ek achha choose nahi kar sakte jab tak hume pata na ho ki pushing ka har instant endpoint ko kaise change karta hai. Toh hum true dynamics integrate karte hain. Symbol ka matlab bas hai "abhi se deadline tak har instant ka contribution add karo."
PICTURE. Figure baaki time ko thin bars mein slice karta hai. Har bar ek chhoti push hai. Pehle ki gayi push (left bars) ki ek lambi lever-arm hai — woh position ko kaafi der tak move karti rehti hai. Baad mein ki gayi push (right bars) position ko mushkil se nudge karti hai. Bar heights times unki lever arms woh picture hai jo integral ke peeche hai.

Step 4 — Constraints "do gaps fill karo" ban jaate hain
KYA. Maango ki sachcha ending target ke barabar ho: aur . Coast parts ko doosri taraf move karo.
KYUN. Left par coast parts exactly wahi cheezein hain jo hum ZEM aur ZEV define karne ke liye subtract karte the. Toh boundary conditions do clean statements mein collapse ho jaate hain pushes ke baare mein.
PICTURE. Figure mein do "buckets." Velocity bucket ZEV level tak pushes ke raw sum se fill hona chahiye. Position bucket ZEM level tak fill hona chahiye, lekin har push apni lever-arm se scaled hokar pour hoti hai.

Infinitely many push-profiles hain jo dono buckets fill karti hain. Kaun si best hai?
Step 5 — "Best" ka matlab least effort → ek straight-line push profile
KYA. Un saari profiles mein se jo dono buckets fill karti hain, woh choose karo jo least effort spend kare. Hum effort measure karte hain Calculus of variations ko do Lagrange multipliers ke saath use karne par, jawab remaining time mein linear hone par majboor ho jaata hai.
KYUN profile linear aati hai (ek-picture-mein-proof). Yeh key result hai, toh chalo ise assert karne ki jagah earn karte hain. Lagrange ka recipe kehta hai: ko do bucket constraints ke subject mein minimise karne ke liye, har constraint ko ek unknown constant multiplier se subtract karo aur combined quantity ko freely minimise karo: Yahan position bucket ke liye pay karta hai (toh yeh lever weight multiply karta hai) aur velocity bucket ke liye pay karta hai (weight ). Ab crucial idea yeh hai: kyunki integral ke andar alag se appear karta hai, hum har instant par apne aap minimise kar sakte hain — uss ek instant ke liye best choose karo. Bracket ke andar ki cheez, ek single instant ke liye, mein ek plain upward parabola hai: A parabola ka bottom wahan hai jahan slope zero ho. Slope (gradient) hai , toh minimum yahan baithta hai Yeh remaining time mein ek straight line hai — ek constant plus slope times — precisely isliye kyunki cost ek parabola (quadratic) thi aur constraint weights ( aur ) hi sirf -shapes the jin par lean kiya ja sake.
PICTURE. Figure candidate profiles (wiggly, chalk-blue) dikhata hai jo sab buckets fill karti hain, aur winner (straight pale-yellow line). Straight line required amounts deliver karne ka sabse flat tarika hai — least squared area.

Yahan line ko tilt karta hai aur use raise karta hai. Abhi hume unki values nahi pata — buckets unhe pin down karenge.
Step 6 — Wapas substitute karo aur chhota system solve karo
KYA. Straight-line ko do bucket-equations mein dalo. (remaining time) substitute karo taaki integrals ki clean powers ban jayein.
KYUN. Ab unknowns bas do constant vectors hain. Do vector equations, do vector unknowns — plain algebra kaam khatam karti hai.
PICTURE. Figure do moment integrals ko aur ke neeche coloured areas ke roop mein plot karta hai, aur factors dete hue jo tum literally triangle/curve areas ke roop mein read karte ho.

Do equations ko naam dete hain taaki algebra track karna aasaan ho:
eliminate karo. (I) ko se aur (II) ko se multiply karo taaki dono mein same coefficient aaye:
hatane ke liye pehli scaled line ka second se subtract karo:
Back-substitute karo scaled pehli line mein :
Step 7 — Command abhi apply karo
KYA. Hum push sirf current instant par apply karte hain, yaani par, jahan . Toh evaluate karo.
KYUN. Guidance feedback ke roop mein run hoti hai: abhi command use karo, phir next cycle mein fresh ZEM/ZEV recompute karo. Hum kabhi poora profile store nahi karte — sirf "abhi" par uski value.
PICTURE. Figure straight-line profile ke left endpoint (at ) ko highlight karta hai — woh single dot woh number hai jise thruster is instant obey karta hai.

Ab bas add karo. Pehle ko se scale karo:
Phir term by term add karo, pieces aur pieces group karte hue:
Har bracket ab bas same denominator wale fractions add karna hai — koi ellipsis nahi, koi guesswork nahi:
Step 8 — Interception law: coefficient ki jagah kyun hota hai
KYA. Missile ke liye hum sirf target ki position hit karne ki parwah karte hain; hum nahi chahte ki hum kis velocity se pahunchein. Toh hum velocity constraint poori tarah drop kar dete hain — fill karne ke liye koi ZEV bucket nahi hai.
KYUN coefficient badalti hai. Yeh woh subtle point hai jise reviewer ne flag kiya tha. Tum simply soft-landing law se ZEV term erase nahi karte; woh chhod deta, jo galat hoga. ek do-constraint problem ka jawab tha. Sirf ek constraint ke saath hum algebra redo karte hain: sirf position bucket bachta hai, aur optimal profile ke paas lean karne ke liye koi velocity bucket nahi.
PICTURE. Figure single-bucket problem dikhata hai: ab sirf position bucket exist karta hai, toh optimal straight line sirf ek condition se pin hoti hai.

Lagrange redo karo ek multiplier ke saath single position constraint ke liye. Combined quantity hai aur har instant par parabola minimise karne par (slope zero) milta hai Notice karo yeh deadline par zero se pass karta hai (): match karne ke liye koi velocity nahi hone se, optimal push naturally end mein kuch nahi ho jaati hai. Ab single (position) bucket fill karo, Step 6 jaisi substitution use karke: Abhi apply command hai :
Step 9 — Edge case: aur negative
KYA. Coefficients aur ko dekhte raho jaise clock khatam hoti hai, aur poochho ki negative ka kya matlab hoga.
KYUN. Real thrusters saturate ho jaate hain; ek command jo infinity ki taraf jaaye woh ek design red flag hai. Aur ek countdown jo zero cross kar chuki hai woh ek mission state hai jise hume pehchanna chahiye, formula mein silently feed nahi karna.
PICTURE. Figure dono coefficients ko ke against plot karta hai: do chalk curves jo jaane par ceiling ki taraf rocket karti hain. curve (ZEM) (ZEV) se tez chadhti hai.

Ek-picture summary

Ek image, poori kahaani: dot coast karo (yellow), do gaps ZEM (blue) aur ZEV (pink) read karo, straight-line optimal push se buckets fill karo, "abhi" par evaluate karo — aur nikal aata hai.
Recall Feynman retelling — plain words mein wapas bolo
Socho tum ek ball target par phenk rahe ho aur mid-flight mein use nudge karte reh sakte ho. Teen clocks dimag mein rakhna: abhi (), deadline (), aur unke beech countdown (). Pehle, pretend karo ki nudging band kar do: sirf gravity neeche kheench raha hai, ball kahan drift karta hai, aur kitni tez? Do gaps dikhte hain — jagah ka gap (ZEM) aur speed ka gap (ZEV). Ab, un saari tareekon mein se jo dono gaps close karti hain, tum sabse aalsi chahte ho — least total shove-squared (jahan "squared shove" bas arrow ki length times itself hai). Math kehta hai ki sabse aalsi nudge ek straight-line schedule hai, aur hum ne ise prove kiya: har instant par cost mein ek simple upward parabola hai, aur parabola ka bottom remaining time mein straight line par baithta hai. Do facts woh line pin karte hain: raw nudges speed gap ke barabar add hone chahiye, aur early-weighted nudges jagah ke gap ke barabar add hone chahiye. Time variable ko "remaining time" mein flip karo, do areas read karo, chhota two-by-two solve karo — dhyaan se, har fraction same denominator ke saath — aur ek rule milta hai jo tum isi instant use karte ho: jagah ke gap times six-over-time-squared push karo, minus speed ke gap times two-over-time. Agar tum gently pahunchne ki parwah nahi karte (missile), toh speed bucket phenk do aur Lagrange step ek multiplier ke saath redo karo — profile ab deadline par zero ho jaati hai, aur "six" "three" ban jaata hai, kyunki ek single area one-third deta hai coupled answer ki jagah. Woh three-over-time-squared rule exactly Proportional Navigation hai ek costume mein, uski navigation ratio teen par pin hoti hui. Aur agar time almost khatam ho gaya hai lekin gap bacha hua hai, toh rule infinite thrust maangta hai — yahi wajah hai ki tum ise constant feedback ke roop mein run karte ho aur countdown zero hit karne se pehle ise freeze karo, errors jaldi maar do jab abhi bhi gentle rehne ka time ho.
Quick self-check
Ex1 landing values
Why the ZEV term is subtracted
What makes the optimal profile a straight line
Why interception uses not
What to do when
Related tools: Optimal Control — LQR · Lambert's Problem · Time-to-go estimation · Double Integrator Dynamics.