Is page par assume kiya gaya hai ki aapne kuch bhi nahi dekha. Hum har symbol build karte hain jaise parent note aap par throw karta hai, aisi order mein jahan har ek sirf usse pehle waale par depend karta hai. Upar se neeche padho.
Topic ko yeh kyun chahiye: ek spacecraft ka thrust, ek star ki direction, ek angular velocity — yeh sab arrows hain. Agar hum arrows ke baare mein baat nahi kar sakte, toh pointing ke baare mein bilkul baat nahi kar sakte.
Arrow ko numbers mein badle ke liye, pehle teen reference directions neeche rakhte hain measure karne ke liye.
Topic ko yeh kyun chahiye: ek tumbling spacecraft par bolted gyro ek tilted corner se measure karta hai; star map ek seedhe corner mein likhi hoti hai. Same star, do triples. Hume unke beech convert karna hoga.
Topic ko yeh kyun chahiye: sirf orthonormal frames ke liye hi sasta "invert karne ke liye bas transpose karo" trick (Section 8) kaam karti hai. Real spacecraft frames hamesha is tarah purpose se banaye jaate hain.
Yeh page par sabse important tool hai, isliye hum ise dhire-dhire build karte hain aur batate hain ki kyun yeh tool aur koi nahi.
Har piece ko unpack karte hain:
∥a∥ — arrow a ki length (magnitude), ek plain positive number, jaise ek stick ki length.
θ — do arrows ke beech ka angle, jahan unki tails milti hain wahan measure kiya jaata hai.
cosθ — cosine: ek number jo jawaab deta hai "yeh do directions kitni aligned hain?" Yeh +1 se chalta hai (bilkul parallel, θ=0), 0 se guzarta hai (perpendicular, θ=90∘), −1 tak (opposite, θ=180∘).
Topic ko yeh kyun chahiye: parent har component ko vxB=v⋅x^B ke roop mein derive karta hai. Woh yahi special case hai, kuch aur nahi.
Topic ko yeh kyun chahiye: parent ka proof ki RRT=I kehta hai "entry (i,j) hai e^i⋅e^j=δij" — woh exactly yahi symbol hai jo 1s-aur-0s pattern ko package karta hai.
Topic ko yeh kyun chahiye: DCM RBIaisi hi ek matrix hai; frames ke beech arrow ke numbers convert karna exactly ek matrix–vector multiply hai. Aur "RTR=I" woh property hai jo tumhe ek rotation free mein undo karne deti hai.
Sab kuch usi ek destination mein funnel ho jaata hai: ek arrow ke numbers ko body ki attitude aur fixed stars ke beech convert karna. Yahan se tum quaternions, gyro sensing, aur orbit frames ke liye ready ho.
Right side ko cover karo aur zor se jawab do. Agar koi ek bhi ruk jaaye, toh parent note se pehle us section ko dobara padho.
x^ mein hat tumhe kya bata raha hai?
Ki is arrow ki length exactly 1 hai — yeh ek pure direction hai (ek unit vector).
Ek vector ke numbers har frame mein same kyun nahi rehte?
Arrow fixed hai, lekin har frame ise alag axes ke against measure karta hai, isliye teen component-numbers differ karte hain.
Words mein, a⋅b=∥a∥∥b∥cosθ kya measure karta hai?
Ek arrow ka kitna hissa doosre arrow ki direction mein hai — unki alignment.
Projection ke liye cosine sahi function kyun hai?
Yeh arrows align hone par full value deta hai (cos0=1), perpendicular hone par zero (cos90∘=0), oppose hone par negative — exactly shadow-length behaviour.
Jab x^ ek unit axis hai toh v⋅x^ kya hai?
Yeh vx hai, v ka component x^ ke along.
Perpendicular unit axes ke liye x^⋅y^ kya hai, aur kyun?
Zero, kyunki cos90∘=0.
δij kya equal hai?
1 jab i=j, 0 jab i=j.
Matrix–vector multiply aslmein kya hai, repeated?
Har matrix row ka column ke saath dot product, teen baar.
RT ek matrix ke saath kya karta hai?
Ise diagonal ke across flip karta hai — rows columns ban jaate hain.
RBI ko plain words mein padho aur batao yeh kya karta hai.
"Body from inertial" — yeh inertial component-numbers leta hai aur body component-numbers return karta hai.
RCBRBI mein, product valid kyun hai?
Andar ke B labels touch karte hain aur cancel ho jaate hain, RCI bachta hai.