Yeh page ek toolbox hai. Lambert's problem ya parent Gauss's method note padhne se pehle, tumhe neeche diye har ek symbol ki zaroorat hai. Hum har cheez scratch se build karenge: plain words → ek picture → topic ko yeh kyun chahiye. Skip mat karna; baad ke har symbol ka base koi pehle wala symbol hai.
Central body ek special point par hoti hai jise focus kehte hain. Hamare har ek orbit mein central body apni ellipse ke ek focus par hoti hai — yeh Kepler's first law hai, aur hum ise yahan given maante hain.
Picture: figure s01 dekho. Orange dot focus hai. Do magenta arrows, r1 aur r2, spacecraft ki do positions tak pahunchte hain — ek pehli aur ek baad wali.
Topic ko yeh kyun chahiye: Lambert's problem in do arrows ke terms mein stated hai. Yeh known data hain. Baaki sab kuch inhi se nikala jaata hai.
Symbol ν (Greek "nu") true anomaly hai — apni orbit mein spacecraft ka angle measure kiya jaata hai. Toh Δν (true anomaly mein change) aur θ same cheez hain: swept angle.
Picture: figure s01 mein do magenta arrows ke beech wala violet wedge θ hai.
Topic ko yeh kyun chahiye:θ bataata hai ki do points central body ke around kitne "spread out" hain. Chhota θ matlab woh almost line mein hain; bada θ matlab spacecraft zyaadatar poora chakkar laga ke aayi.
Hum do arrows jaante hain, lekin abhi tak unke beech ka angle nahi. Woh tool jo do arrows se angle nikalti hai woh dot product hai.
cos (cosine) yahan cosine function hai: ek angle ke liye, yeh −1 aur +1 ke beech ka number hai jo bataata hai ki do arrows direction mein kitna "agree" karte hain. cos0∘=1 (same direction), cos90∘=0 (perpendicular), cos180∘=−1 (opposite).
Do spacecraft positions ko seedha connect karne wali straight line kheencho. Woh straight segment chord c hai.
Picture: figure s02. Focus, r1 ki tip, aur r2 ki tip milkar ek triangle banate hain. Do arrows do sides hain; chord c teesri side hai (orange straight line).
c kyun chahiye: yeh "do endpoints kitne door hain" ka ek pure-geometry summary hai. chord har serious Lambert solver mein aata hai.
Topic ko triangle kyun chahiye: yeh us curved region ka flat stand-in hai jise planet actually sweep karta hai. Gauss curved region ko is flat wale se compare karta hai.
Planet straight chord ke along travel nahi karta. Woh curved orbit ke along travel karta hai. Toh woh region jo woh actually sweep karta hai wo do arrows aur curve se bounded hota hai — ek "pie slice." Wahi elliptic sector hai.
Picture: figure s03. Violet region true elliptic sector hai (curved orbit se bounded). Magenta dashed region flat triangle hai (chord se bounded). Sector hamesha triangle se thoda mota hota hai kyunki curve baahir ki taraf bulge karta hai.
Dono kyun chahiye: Gauss ka poora trick ek number hai,
y≡area of trianglearea of sector.
Jab orbit muskil se bend karti hai (chhota θ), curve almost chord jaisi hai, sector ≈ triangle, toh y≈1. Yahi sensible first guess hai jahan se algorithm shuru karta hai.
Yahan h specific angular momentum hai — ek given orbit ke liye ek fixed number jo bataata hai area kitni tezi se sweep ho raha hai. Yeh orbit shape se h=μp ke through relate karta hai (dono symbols aage define hain).
Kyun chahiye: orbit ki shape aur us par speed dono depend karte hain ki central body kitni strong pull karti hai. Parent note mein canonical units mein μ=1 set kiya jaata hai arithmetic clean rakhne ke liye.
Kahan enter karta hai: time constant m∝μΔt2 ke andar — zyada gravity planet ko zyada tezi se ghuma deti hai, toh time budget badal jaata hai.
Kyun chahiye: jab Gauss ki iteration sahi geometry par land karti hai, p woh number hai jo hum extract karte hain, aur p se Lagrange f and g functions aate hain jo velocities wapas dete hain. Yeh poori method ka "answer knob" hai.
Section 2 se true anomaly νreal, physical angle hai. Lekin timing ko cleanly solve karne ke liye ek alag bookkeeping angle chahiye, eccentric anomaly E — woh angle jo tum measure karte agar ellipse ko stretch karke circle bana dete. Yeh Kepler's equation mein appear karta hai, woh equation jo orbit par angle ko time se link karti hai.
Picture: figure s03 mein wapas, curve ka zyada bend = zyada bada x = fatter sector = zyada bada y. Yeh saath rise karte hain.
Yeh do sirf pre-computed numbers hain jo data se build hote hain, taaki iteration mein har loop mein inhe recompute na karna pade.
Notice karo ki dono denominators mein cos(θ/2) hai. Jab θ→180∘ (do points focus ke almost opposite), θ/2→90∘ aur cos(θ/2)→0 — toh ℓ aur m infinity tak blow up karte hain. Yahi exact jagah hai jahan Gauss's method fail karta hai, aur isliye near-antipodal transfers ko Universal variable formulation ya Izzo Lambert solver ki zaroorat hoti hai.