Worked examples — General relativity — equivalence principle, curved spacetime (overview)
2.3.33 · D3· Physics › Modern Physics › General relativity — equivalence principle, curved spacetime
Koi bhi symbol aane se pehle, yeh raha toolbox — har woh quantity jo hum use karenge, plain words mein:
Parent se do master results, dobara likhe gaye taaki hum har piece ko point kar sakein:
The scenario matrix
Is topic ka har problem in cells mein se ek (ya combination) hai:
| Cell | Case class | Kya badalta hai | Example |
|---|---|---|---|
| A | (clock zyada upar) | GR: upar wali clock faster, light upar jaate redshifts | Ex 1 |
| B | (clock neeche) | GR: neeche wali clock slower, neeche jaate light blueshifts | Ex 2 |
| C | (same height) | Degenerate: koi GR shift nahi | Ex 3 |
| D | Pure velocity, koi height nahi | SR only: moving clock slower | Ex 3 |
| E | Dono effects competing (GPS) | GR , SR , kaun jeetega? | Ex 4 |
| F | Strong-field / exact potential | use karo, nahi | Ex 5 |
| G | Limiting behaviour (, , weak field SR) | Formula ki edges par sanity checks | Ex 6 |
| H | Real-world word problem | Mountain-vs-valley aging | Ex 7 |
| I | Exam twist — light bending, clocks nahi | Free-fall / deflection reasoning | Ex 8 |
Neeche ke aath examples har cell ko cover karte hain.
Example 1 — Cell A: ek clock ko tower ke UPAR le jaana ()
Forecast: Abhi andaza lagao — nanoseconds, microseconds, ya seconds per day? Aur kya light upar jaate redder hogi ya bluer?
Steps
-
Fractional rate difference. . Yeh step kyun? (roof zyada upar hai) hume seedha Cell A mein rakhta hai, isliye hum GR engine ko plus sign ke saath use karte hain — zyada upar matlab zyada fast.
-
Compute karo: (pure number). Yeh step kyun? Yeh ratio batata hai "har second, roof kitne extra seconds gain karti hai." Hum ise real time se multiply karne se pehle dimensionless rakhte hain.
-
Ek din se multiply karo: . Yeh step kyun? Ek rate tab hi duration banti hai jab use elapsed time se multiply karo.
-
Light direction: light UPAR jaate energy khoती hai girta hai redshift (). Yeh step kyun? Photon "well se bahar climb" kar raha hai, upar jaate energy kharach karta hai — exactly formula ka sign.
Verify: Units: dimensionless ✓. Roughly ek nanosecond per day 100 m ke liye — wahi order jo Pound–Rebka ne 22.5 m par measure kiya tha, scaled up. ✓

Example 2 — Cell B: ek clock ko mine mein NEECHE karna ()
Forecast: Kya deep clock surface clock se faster chalegi ya slower?
Steps
-
Negative height plug karo: . Yeh step kyun? Formula pehle se ka sign carry karta hai; ek lower clock () automatically negative aata hai = slower chalta hai. Yeh Cell B hai aur isme koi nayi physics nahi chahiye, bas minus sign ki honest bookkeeping.
-
Interpret karo: negative ⇒ mine clock slower chalti hai surface clock se. Yeh step kyun? "Potential well mein zyada neeche = slower" yahi gravitational time dilation ka sara content hai; negative woh tarika hai jisse formula "lower" encode karta hai.
-
Light neeche bheji: positive ⇒ badhta hai ⇒ blueshift. Yeh step kyun? Ek photon jo girta hai energy gain karta hai (neechey dhaalta hai), isliye uski frequency badhti hai — Example 1 ka mirror image.
Verify: Magnitude exactly Example 1 ka hai kyunki bada hai ( vs ) — formula mein linear hai. ✓ Sign sahi flip hua: up→redshift, down→blueshift. ✓
Example 3 — Cells C & D: same height () lekin ek clock MOVING hai
Forecast: ke saath, kya koi time dilation hogi bhi?
Steps
-
(a) GR part: . Yeh step kyun? Cell C degenerate case hai: engine mein linear hai, isliye zero height difference exactly zero gravitational shift deta hai. Koi trick nahi, koi residue nahi.
-
(b) SR part (Cell D): . Yeh step kyun? Motion akela clock slow kar deta hai. Hum ab velocity engine use karte hain kyunki dono clocks ke beech sirf speed ka difference hai, height ka nahi. kyun aur kyun nahi? Slow speeds ke liye hum exact factor expand karte hain; leading correction half hai.
-
Per day: . Yeh step kyun? Rate ko duration mein convert karo se multiply karke, pehle ki tarah.
Verify: GR shift exactly hai ✓ (sahi degenerate behaviour). SR shift negative hai ✓ (moving clock slower). Rim clock purely motion ki wajah se ~19 ns/day khoता hai. ✓
Example 4 — Cell E: GPS, dono effects fighting
Forecast: Kya satellite clock ground clock se aage rahegi ya peechhe — aur microseconds mein ya nanoseconds mein?
Steps
-
GR (height) part, exact potential. Kyunki height bahut zyada hai, ki jagah use karo: Numerically . Yeh step kyun? Cell F rule: sirf tab kaam karta hai jab height chhoti ho aur roughly constant ho. km par, kam ho jaata hai, isliye hume potential integrate karna hoga — terms ka difference. Positive = satellite (zyada upar) faster chalta hai.
-
SR (velocity) part: . Yeh step kyun? Satellite move bhi karta hai, aur motion clock slow kar deta hai. Negative, GR gain ka opposition karta hai.
-
Unhe add karo (Cell E superposition hai): . Yeh step kyun? Do chhote effects first order par simply add ho jaate hain. GR () SR () se bada hai, isliye net positive hai: satellite clock fast chalti hai.
-
Per day: . Yeh step kyun? Rate × day. Yahi famous s hai jo GPS ko correct karna padta hai warna positions ~11 km/day drift karti hain.
Verify: GR (-ish) SR (-ish) ko beat karta hai standard textbook split mein, net s/day ✓, aur yeh positive hai (satellite aage) ✓. Har piece ka sign hamari convention se match karta hai (higher=faster, moving=slower). ✓ Dekho GPS Corrections.
Example 5 — Cell F: exact potential vs shortcut
Forecast: 100 km par, kya simple formula abhi bhi hold karta hai — 0.1% off? 10%? 50%?
Steps
-
Naive: . Yeh step kyun? Yeh flat-field shortcut hai, valid tabhi jab roughly constant ho.
-
Exact: . Yeh step kyun? Real potential difference account karta hai ki altitude ke saath thoda drop karta hai — yeh honest Cell F calculation hai.
-
Compare karo: dono mein lagbhag ka fark hai. Yeh step kyun? Yeh dikhata hai kab shortcut toot jaata hai: 100 km par error chhota par visible hai; 20,000 km par (Ex 4) yeh bahut bada hoga, exactly isliye GPS exact form use karta hai.
Verify: Exact < naive (kyunki real climb karte waqt decrease hota hai, true potential gain thoda chhota hai) ✓. Relative difference ✓.
Example 6 — Cell G: teen limiting cases
Forecast: Kya ek accha formula in teen edges par , ek known result, aur ek warning deta hai?
Steps
-
(a) : . Yeh step kyun? Ek hi jagah par do clocks identically tick karni chahiye — formula vanish karna chahiye, aur karta hai ( mein linear).
-
(b) Weak-field / free-fall limit: freely-falling chhote box mein, EP kehta hai gravity "off" hai, isliye sirf velocity time dilation () bachti hai — hum Special Relativity recover karte hain. Yeh step kyun? GR ko locally SR mein reduce karna chahiye; GR term ek gravitational-potential term hai, aur free-fall mein ek tiny box across potential difference .
-
(c) Large- warning: naive with deta hai — ek fractional rate difference jo 1 se zyada ho woh nonsense hai. Yeh step kyun? Yeh flag karta hai ki constant- extrapolation badi distance par illegal hai; tumhe par switch karna hi hoga (Cell F). Formula tumhe batata hai kahan wo fail hota hai.
Verify: (a) exactly ✓; (c) , unphysical ✓ — correctly linear approximation ka breakdown signal karta hai.
Example 7 — Cell H: mountain vs valley (word problem)
Forecast: Poori zindagi mein milliseconds? Seconds? Minutes?
Steps
-
Rate: . Yeh step kyun? Cell A phir se (): zyada upar mountain clock (aur body) faster chalti hai.
-
Total time: . Yeh step kyun? Ek lifetime ko seconds mein convert karo taaki fractional rate ek actual duration ban sake.
-
Extra ageing: . Yeh step kyun? Rate × elapsed time — mountain twin genuinely aadhe millisecond zyada bada hai 80 saalon baad.
Verify: Positive (higher = faster ages) ✓, aur tiny (sub-millisecond ek lifetime mein) ✓ — Example 1 ke ns/day-per-100m se consistent, scaled up ( height, days).
Example 8 — Cell I: exam twist — light bending, clocks nahi
Forecast: Micrometres, nanometres, ya kuch jo ruler se dekh sako?
Steps
-
Crossing time: . Yeh step kyun? Light inertial frame mein seedha travel karti hai; hume jaanna hai ki flight mein kitna time lagta hai taaki dekh sakein ki floor kitna upar uthti hai.
-
Box rises: . Yeh step kyun? Accelerating box ke andar se, box upar move karta hai jabki light seedhi jaati hai, isliye light drop hoti dikhti hai. equivalence principle se, real gravity mein bhi wahi bend hona chahiye.
-
The trap (Cell I twist): naively photon ko Newtonian mass ki tarah girta maan kar yeh milta hai, lekin starlight ka full GR deflection twice as big hai — kyunki space khud bhi curved hai, sirf time nahi. Yeh step kyun? Yeh "photons have mass" misconception ko khatam karta hai: EP/accelerating-box argument sirf time-curvature half capture karta hai; extra factor of 2 spatial curvature se aata hai (dekho Gravitational Lensing).
Verify: ✓ — 3 m par bilkul tiny (isliye lab light-bending unmeasurable hai aur hume Sun ke paas se guzarti starlight chahiye). Real deflection ke liye "factor of 2" standard GR-vs-Newton result hai ✓.

Recall Matrix ke across self-test (answers hide karo)
Ek clock ko upar uthane par ka sign kya hoga? ::: Positive — zyada upar wali clocks faster chalti hain. GPS ke liye kaun sa effect dominate karta hai, GR ya SR? ::: GR (higher = faster) jeetata hai; net s/day. ko se kab replace karna padta hai? ::: Jab height itni badi ho ki appreciably change ho jaaye (Cell F). par kya hota hai? ::: Exactly zero (degenerate Cell C). Real light deflection accelerating-box estimate se twice kyun hai? ::: Box argument sirf time-curvature deta hai; spatial curvature doosra half add karta hai.
Connections
- Parent topic — woh principles jo yeh examples exercise karte hain.
- Gravitational Time Dilation — Cells A/B/C/F/H ke peeche ka engine.
- GPS Corrections — Cell E puri detail mein.
- Special Relativity — velocity engine (Cells D/E, limit G(b)).
- Gravitational Lensing — Example 8 ka "factor of 2."
- Newtonian Gravity — potential ka source jo Cells E/F mein use hota hai.
- Geodesics & Curvature — free-fall weightless kyun lagta hai (Example 8 ka frame).