Worked examples — General relativity — equivalence principle, curved spacetime (overview)
Before any symbol appears, here is the toolbox — every quantity we will use, in plain words:
The two master results from the parent, restated so we can point at each piece:
The scenario matrix
Every problem in this topic is one (or a combination) of these cells:
| Cell | Case class | What changes | Example |
|---|---|---|---|
| A | (clock higher up) | GR: higher clock faster, light redshifts going up | Ex 1 |
| B | (clock lower down) | GR: lower clock slower, light blueshifts going down | Ex 2 |
| C | (same height) | Degenerate: no GR shift | Ex 3 |
| D | Pure velocity, no height | SR only: moving clock slower | Ex 3 |
| E | Both effects competing (GPS) | GR , SR , which wins? | Ex 4 |
| F | Strong-field / exact potential | Use , not | Ex 5 |
| G | Limiting behaviour (, , weak field SR) | Sanity checks on the formula's edges | Ex 6 |
| H | Real-world word problem | Mountain-vs-valley aging | Ex 7 |
| I | Exam twist — light bending, not clocks | Free-fall / deflection reasoning | Ex 8 |
The eight examples below hit every cell.
Example 1 — Cell A: a clock carried UP a tower ()
Forecast: Guess now — nanoseconds, microseconds, or seconds per day? And does the light get redder or bluer going up?
Steps
-
Fractional rate difference. . Why this step? (roof is higher) puts us squarely in Cell A, so we use the GR engine with a plus sign — higher means faster.
-
Compute: (pure number). Why this step? This ratio tells us "for every second, how many extra seconds does the roof gain." We keep it dimensionless before multiplying by real time.
-
Multiply by a day: . Why this step? A rate only becomes a duration when multiplied by elapsed time .
-
Light direction: light climbing UP loses energy drops redshift (). Why this step? The photon is "climbing out of the well," paying energy on the way up — exactly the sign of the formula.
Verify: Units: dimensionless ✓. Roughly a nanosecond a day for 100 m — the same order Pound–Rebka measured over 22.5 m scaled up. ✓

Example 2 — Cell B: a clock lowered DOWN a mine ()
Forecast: Does the deep clock run faster or slower than the surface clock?
Steps
-
Plug the negative height: . Why this step? The formula already carries the sign of ; a lower clock () automatically comes out negative = runs slower. This is Cell B and it needs no new physics, just honest bookkeeping of the minus sign.
-
Interpret: negative ⇒ the mine clock runs slower than the surface clock. Why this step? "Lower in the potential well = slower" is the whole content of gravitational time dilation; the negative is how the formula encodes "lower."
-
Light sent down: positive ⇒ increases ⇒ blueshift. Why this step? A photon falling gains energy (rolling downhill), so its frequency rises — the mirror image of Example 1.
Verify: Magnitude is exactly Example 1's because is larger ( vs ) — the formula is linear in . ✓ Sign flipped correctly: up→redshift, down→blueshift. ✓
Example 3 — Cells C & D: same height () but one clock MOVING
Forecast: With , is there any time dilation at all?
Steps
-
(a) GR part: . Why this step? Cell C is the degenerate case: the engine is linear in , so zero height difference gives exactly zero gravitational shift. No trick, no residue.
-
(b) SR part (Cell D): . Why this step? Motion alone slows a clock. We use the velocity engine now because the only difference between the clocks is speed, not height. Why and not ? For slow speeds we expand the exact factor ; the leading correction is half .
-
Per day: . Why this step? Convert rate to duration by multiplying by , same as before.
Verify: GR shift is exactly ✓ (correct degenerate behaviour). SR shift is negative ✓ (moving clock slower). The rim clock loses ~19 ns/day purely from motion. ✓
Example 4 — Cell E: GPS, both effects fighting
Forecast: Does the satellite clock end up ahead or behind the ground clock — and by microseconds or nanoseconds?
Steps
-
GR (height) part, exact potential. Because the height is huge, use not : Numerically . Why this step? Cell F rule: only works over small heights where is constant. Over km, falls off, so we must integrate the potential — the difference of terms. Positive = satellite (higher) runs faster.
-
SR (velocity) part: . Why this step? The satellite also moves, and motion slows clocks. Negative, opposing the GR gain.
-
Add them (Cell E is a superposition): . Why this step? The two small effects simply add to first order. GR () is bigger than SR (), so the net is positive: the satellite clock runs fast.
-
Per day: . Why this step? Rate × day. This is the famous s that GPS must correct or positions drift ~11 km/day.
Verify: GR (-ish) beats SR (-ish) in the standard textbook split, net s/day ✓, and it is positive (satellite ahead) ✓. Sign of each piece matches our convention (higher=faster, moving=slower). ✓ See GPS Corrections.
Example 5 — Cell F: exact potential vs the shortcut
Forecast: Over 100 km, does the simple formula still hold — off by 0.1%? 10%? 50%?
Steps
-
Naive: . Why this step? This is the flat-field shortcut, valid only while is roughly constant.
-
Exact: . Why this step? The real potential difference accounts for dropping slightly with altitude — this is the honest Cell F calculation.
-
Compare: they differ by about . Why this step? It shows when the shortcut breaks: over 100 km the error is small but visible; over 20,000 km (Ex 4) it would be enormous, which is exactly why GPS uses the exact form.
Verify: Exact < naive (since real decreases as you climb, the true potential gain is slightly smaller) ✓. Relative difference ✓.
Example 6 — Cell G: the three limiting cases
Forecast: Should a good formula give , a known result, and a warning at these three edges?
Steps
-
(a) : . Why this step? Two clocks at the same place must tick identically — the formula must vanish, and it does (linear in ).
-
(b) Weak-field / free-fall limit: in a freely-falling small box, EP says gravity is "off," so only velocity time dilation () survives — you recover Special Relativity. Why this step? GR must reduce to SR locally; the GR term is a gravitational-potential term, and in free-fall the potential difference across a tiny box .
-
(c) Large- warning: naive with gives — a fractional rate difference exceeding 1 is nonsense. Why this step? It flags that constant- extrapolation is illegal at large distance; you must switch to (Cell F). The formula tells you where it dies.
Verify: (a) exactly ✓; (c) , unphysical ✓ — correctly signals breakdown of the linear approximation.
Example 7 — Cell H: mountain vs valley (word problem)
Forecast: Milliseconds? Seconds? Minutes over a whole lifetime?
Steps
-
Rate: . Why this step? Cell A again (): the higher-up mountain clock (and body) runs faster.
-
Total time: . Why this step? Convert a lifetime into seconds so the fractional rate becomes an actual duration.
-
Extra ageing: . Why this step? Rate × elapsed time — the mountain twin is genuinely older by half a millisecond after 80 years.
Verify: Positive (higher = ages faster) ✓, and tiny (sub-millisecond over a lifetime) ✓ — consistent with the ns/day-per-100m of Example 1 scaled up ( height, days).
Example 8 — Cell I: the exam twist — light bending, not clocks
Forecast: Micrometres, nanometres, or something you could see with a ruler?
Steps
-
Crossing time: . Why this step? Light travels straight in the inertial frame; we need how long it's in flight to see how far the floor rises under it.
-
Box rises: . Why this step? From inside the accelerating box, the box moves up while light goes straight, so light appears to drop by . By the equivalence principle, the same bend must occur in real gravity.
-
The trap (Cell I twist): naively treating the photon as a Newtonian mass falling gives this , but the full GR deflection of starlight is twice as big — because space itself is also curved, not just time. Why this step? It kills the "photons have mass" misconception: the EP/accelerating-box argument captures only the time-curvature half; the extra factor of 2 comes from spatial curvature (see Gravitational Lensing).
Verify: ✓ — utterly tiny over 3 m (why lab light-bending is unmeasurable and we need starlight grazing the Sun). The "factor of 2" for real deflection is the standard GR-vs-Newton result ✓.

Recall Self-test across the matrix (hide answers)
Sign of for a clock lifted higher? ::: Positive — higher clocks run faster. Which effect dominates for GPS, GR or SR? ::: GR (higher = faster) wins; net s/day. When must you drop for ? ::: When height is large enough that changes appreciably (Cell F). What is when ? ::: Exactly zero (degenerate Cell C). Why is the real light deflection twice the accelerating-box estimate? ::: The box argument only gives time-curvature; spatial curvature adds the other half.
Connections
- Parent topic — the principles these examples exercise.
- Gravitational Time Dilation — the engine behind Cells A/B/C/F/H.
- GPS Corrections — Cell E in full detail.
- Special Relativity — the velocity engine (Cells D/E, limit G(b)).
- Gravitational Lensing — the "factor of 2" of Example 8.
- Newtonian Gravity — source of the potential used in Cells E/F.
- Geodesics & Curvature — why free-fall feels weightless (Example 8's frame).