Radar coordinates from one echo
A sends light at its time , the light meets the event, and the echo returns at . For an observer at rest this reproduces Einstein's synchronization.
Special relativity · Measuring time
Why does seeing a clock tick differ from dating it or reading the clock itself? Light needs time to reach you, so you see every tick late. Echoes let you subtract that travel time and assign a coordinate time, which depends on how the clocks were synchronized. The moving clock's own reading is a third quantity: it counts time along its own path, and a round trip leaves it behind.
Drag a clock's path through spacetime and compare four times for one tick: when its light arrives, its coordinate time, its radar time from echoes and the clock's own reading.
Blue uses A's synchronized coordinates; gold is what A sees when the light arrives.
The JSON record lists every tick of B with its event coordinates, A's send and receive times and the radar time recomputed from that pair.
Physics tutorial
BackgroundA distant clock flashes once a year. Observer A writes down when each flash arrives, sends light pulses that the clock echoes, and later compares notes with the clock itself.
Why it mattersPhysics needs times that do not depend on where the observer happens to stand. Light travel time, synchronization and the clock's own path each change a different number.
Start with the essentials
A sends light at its time , the light meets the event, and the echo returns at . For an observer at rest this reproduces Einstein's synchronization.
Every inertial frame gives the same value. It is zero along a light ray and positive along the path of a clock.
Each leg contributes the square root of its interval divided by c. Out and back at six tenths of light speed for ten years of A's time gives eight years on B.
Here is the velocity away from A. Receding ticks arrive spread out and approaching ticks bunched together; this is the Doppler effect, not a change in the clock's rate.
Typical misconceptionThe time at which I see a distant event is the time at which it happened.
Better mental modelThe flash needs time to arrive. Coordinate time subtracts that delay using an agreed synchronization, here radar echoes.
Typical misconceptionAn approaching clock really runs fast because its ticks arrive more often.
Better mental modelAfter the light delay is removed, a moving clock runs slow in A's frame whether it approaches or recedes. The bunching comes from the shrinking light path.
Typical misconceptionThe diagram shows how the clock would look through a telescope.
Better mental modelOne space dimension, with light speed set to one light-year per year. Observer A rests at the origin and uses Einstein-synchronized clocks. Clock B moves at a constant speed on each of two legs, so its turn is instantaneous. Flashes and echoes travel on straight light lines. The model has no gravity, no forces during the turn and no optics of real images; the drawing frame only relabels the same events.
Start with A round trip leaves fewer ticks and inspect the fourth tick, at the turning point.
What to observe: A dates the turn at five years by coordinates and by radar, sees it at eight years, and B's own clock reads four.Choose A distant resting clock only looks late.
What to observe: Every tick is seen five years late, yet coordinate time and the clock's reading agree. Delay alone does not slow a clock.Move the frame speed slider or choose Same events, moving frame.
What to observe: The coordinate time of the tick changes, while the arrival time on A and the reading on B stay fixed.Relativity as measurement · Reading path
Articles on this path that use this experiment, followed by the other experiments they suggest.