Visual walkthrough — Observability — when KF can estimate state
3.5.23 · D2· Physics › Guidance, Navigation & Control (GNC) › Observability — when KF can estimate state
Hum sirf ek kahani apne paas rakhte hain: tum ek signal dekh sakte ho, aur tum uss chhupi hui starting condition ka andaaza lagaana chahte ho jisne use produce kiya. Bus itna hi. Neeche ka sab kuch usi ek wish se nikalta hai.
Step 1 — Chhupi hui state aur chhhoti si window
KYA. Ek box ka picture banao. Andar numbers ki ek list hai jo time ke saath badlti rehti hai — yeh state hai, jise likhte hain. Agar box mein ek ghoomta hua satellite ho, toh ho sakta hai "current angle" aur "current spin rate." Tum box nahi khol sakte. Tumhare paas sirf ek chhhoti si window hai jo tumhe ek combined reading dikhati hai.
KYO. Estimation exactly yahi situation hai: sensors tumhe kabhi bhi poori internal sach nahi dete, sirf ek filtered jhaaank milti hai. Kisi bhi maths se pehle, humein yeh tay karna hoga ki hum kya dekh sakte hain aur kya nahi.
PICTURE. Figure mein, violet cloud woh sab kuch hai jo box ke andar rehta hai (state). Orange window sirf ek patli beam bahar aane deti hai — woh beam hai. Magenta gear ko dekho jo wall ke peeche poori tarah chhupi hai: hum poora page yeh poochte hue bitaayenge ki "kya hum phir bhi us chhupi hui gear ko figure out kar sakte hain?"

Step 2 — Chhupi hui numbers kaise chalti hain, aur window unhe kaise padhti hai
KYA. Do rules hamare box ko govern karte hain.
- State apne aap evolve hoti hai: . Dot ka matlab hai "rate of change per second." Matrix kehti hai ki har chhupi hui number doosron ko kaise nudge karti hai.
- Window ek fixed lens hai: . Matrix kehti hai ki chhupi hui numbers ka kaun sa combination bahar leakta hai.
Sirf yeh do matrices kyon aur kuch nahi? Humne full state-space form se input term hata diya. Reason: inputs woh cheezein hain jo tum command karte ho, isliye tumhe unka effect pehle se pata hai aur tum use subtract kar sakte ho. Sirf unforced motion () test karta hai ki kya window khud kaafi achhi hai. Observability pair ki property hai — mixing rule plus window — ki kabhi nahi.
PICTURE. Figure mein ko violet arrows ke roop mein dikhaya gaya hai chhupi hui gears ke beech (kaun kise push karta hai) aur ko single orange arrow ke roop mein gears se window tak. Agar kisi gear ka koi path nahi hai — na arrows, na window — jo orange beam tak pahunche, toh problem aane waali hai.

Step 3 — Film ko aage chalana: time par state
KYA. Starting list di hui ho, toh rule ka exactly ek solution hai: Object propagator hai: ise start do, yeh film ko time tak fast-forward kar deta hai.
Exponential kyon aur koi simple cheez kyon nahi? Ek single number ke liye, solve hoke deta hai — exponential woh function hai jiska growth rate apne aap ka times hai. Matrices bhi same tarah behave karti hain jab define kar lo. Hum yeh tool isliye choose karte hain kyunki yeh "kaunsa function hai jiska slope times khud hai?" ka unique answer hai — jo exactly equation hai.
Ab window upar se lagao. Sensor actually jo record karta hai woh hai:
PICTURE. Figure mein same starting dot (magenta) ko ek curved violet trajectory par ke saath le jaate hue dikhaya gaya hai, aur har instant par orange window ek point sample karti hai curve banane ke liye jo right side par hai.

Step 4 — Derivatives se aur equations nikalna
KYA. Ek snapshot aksar bahut kam hota hai. Toh hum dekhte hain ki kaise badlta hai — uska slope, uski curvature, aur aage bhi — exactly start par:
Har line same unknown mein ek fresh linear equation hai.
Derivatives kyon? Derivative poochti hai "signal abhi kis direction mein aur kitni tezi se ja raha hai?" ko differentiate karne par har baar ek factor of neeche aata hai (kyunki ka slope hai), aur par propagator cleanly vanish ho jaata hai. Toh -th derivative crisp row deti hai. Hum derivatives isliye use karte hain kyunki yeh time ke saath signal ki shape ko static equations ki stack mein convert karne ka natural tarika hai.
PICTURE. Figure curve par par zoom karta hai: orange dot (height) hai, magenta tangent line (slope) hai, violet curving arc (bending) hai. Har geometric feature = ek equation = ke baare mein ek aur clue.

Step 5 — Hum kyon rukते hain: Cayley–Hamilton pile ko cap karta hai
KYA. Hum forever differentiate karte reh sakte the: . Lekin hum par ruk jaate hain. Cayley–Hamilton theorem kehta hai ki har matrix apni khud ki characteristic equation satisfy karti hai, jo rearrange hoke deta hai: Toh sirf earlier powers ka recipe hai. se multiply karo: row woh rows ka blend hai jo tum pehle se likh chuke ho.
Yeh kyon matter karta hai. Yeh promise karta hai ki test finite hai. Iske bina, "forever differentiate karo" kabhi terminate nahi hoti. Cayley–Hamilton guarantee karta hai: rows ke baad, koi naya direction of information kabhi appear nahi ho sakta. Row , row , infinity tak — sab redundant.
PICTURE. Figure rows ko horizontal bars ke roop mein stack karta hai. Pehli bars fresh colours hain; jis moment hum pahunche, bar ko earlier bars ka shadow blend dikhaya gaya hai — literally same colour mix — yeh dikhate hue ki yeh kuch naya nahi add karta.

Step 6 — Ek matrix mein stack karna
KYA. Saari useful equations ko ek single tall matrix equation mein line up karo:
Term by term. Har block ek "clue lens" hai: raw window hai, aur har extra ka matlab hai "aur dynamics ko dekhne se pehle baar pot hilane do." Right-hand column pure recorded data hai ( ki values aur derivatives par). Sirf unknown hai.
Stack kyon karo? Ek single lens state ke directions miss kar sakta hai. Bahut saari lenses stack karna (har ek se alag tarah se stirred) humara best possible combined view hai. Agar yeh stack phir bhi pin down nahi kar sakti, toh koi cheez kabhi nahi kar sakti.
PICTURE. Figure literally orange-tinted lens rows ko tall violet block mein stack karta hai jise label kiya gaya hai, magenta unknown right par hai aur data column neeche.

Step 7 — Verdict: full column rank ka matlab "solvable" hai
KYA. Ab hamare paas hai. Iska ke liye exactly ek answer kab hoga?
Rank count karta hai ki ki rows kitne truly independent directions cover karti hain. Agar (hidden states ki sankhya jitna wide), toh equations har direction pin down karti hain — unique solution. Agar , toh ek leftover direction hai jo lenses ne kabhi touch nahi kiya.
Rank kyon, "number of rows" kyon nahi? Tum sau sensors pile kar sakte ho, lekin agar woh sab same combination report karte hain, toh woh height add karte hain aur zero new independent directions — koi new rank nahi. Yahi exact trap hai jiske baare mein parent note warn karta hai.
PICTURE. Figure do cases side by side dikhata hai. Left (observable): state-space ko ek single point par collapse karta hai → ek answer. Right (unobservable): starting states ka ek poora magenta arrow sab map karte hain → window unhe distinguish nahi kar sakti.

Step 8 — Degenerate cases jo tumhe skip nahi karne chahiye
KYA. Teen edge scenarios real GNC designs decide karte hain. Har ek figure mein apna tiny panel hai.
(a) Ek completely decoupled, unmeasured state. Agar mein ek hidden number hai jo na koi visible cheez push karta hai aur na use dekhti hai, toh har block mein uska column zero hai. Lens beam kabhi us tak nahi pahuncha. → unobservable (parent ka Example 2).
(b) Ek hidden state jo ek visible ko push karta hai. Position–velocity with only a position sensor: velocity directly invisible hai, lekin ka matlab hai velocity position drive karti hai, toh yeh mein leak ho jaati hai. → observable (parent ka Example 1). Yeh gear-pushing-a-gear ki jeet hai.
(c) Full rank lekin barely — weak observability. technically rank tak pahunchi, lekin ek direction almost kuch contribute nahi karta (uska beam ek whisper hai). Measurement noise phir use duba deta hai. Yeh rank se akele nahi pakda jaata; tumhe strength grade karne ke liye observability Gramian chahiye, aur yeh explain karta hai kyon detectability woh softer fallback hai jo Riccati steady state actually require karta hai.
Teeno kyon cover karo? Rank test binary hai, lekin reality "blind" se "crystal clear" tak ek spectrum par rehti hai. Ek designer jo sirf rank check karta hai woh case (c) se blindsided ho jaayega.
PICTURE. Teen stacked panels: (a) ek sealed box mein gear — koi beam nahi; (b) ek hidden gear jiska motion lit gear mein ripple karta hai; (c) ek faintly lit gear — barely observable, noise-vulnerable.

Ek-picture summary
Is page ka sab kuch ek flow mein compress ho jaata hai: dekho → derivatives lo → lenses ko mein stack karo → uska rank check karo → ek unique milta hai (ya nahi milta).

Recall Feynman: poora walkthrough simple words mein
Tumhare paas spinning gears ka ek locked box hai aur ek chhhoti si window. Tum kuch der ke liye window film karte ho. Pehla frame thoda batata hai. Picture kaise move karti hai (uski speed) aur batata hai. Woh motion kaise curve karti hai aur bhi zyada batata hai — har ek ek fresh clue hai. Lekin tum hamesha ke liye clues gain nahi karte reh sakte: ke baad (Cayley–Hamilton ka promise) har naya clue sirf ek purana clue ek disguise mein hai. Toh tum exactly clues gather karte ho, unhe called ek badi clue-sheet mein stack karte ho, aur poochते ho: kya yeh clues, milke, har gear ki starting position nail down karte hain? Agar haan — full rank — box observable hai aur ek Kalman Filter sirf window se poori inside rebuild kar sakta hai. Agar kisi gear ne clues mein kahin koi fingerprint nahi chhhoda, woh mein chhupta hai, aur duniya ka koi filter use dhundh nahi sakta. Aur even jab har gear koi kuch mark chhhode, noise ke through padhne ke liye bahut faint mark (weak observability) woh trap hai jo tumhe Gramian aur detectability ki taraf bhejti hai.