Updated by DK 2015.

Original by Don Koks 1998.

It's often said that special relativity is based on two postulates: that all inertial frames are of equal validity, and that light travels at the same speed in all inertial frames. But in real world scenarios, objects almost never travel at constant velocity, and so we might never find an inertial frame in which such an object is at rest. To allow us to make predictions about how accelerating objects behave, we need to introduce a third postulate.

This is often called the "clock postulate", but it applies to much more than just clocks, and in fact it underpins much of advanced relativity, both special and general, as well as the notion of covariance (that is, writing the equations of physics in a observer-independent way).

The clock postulate can be stated in the following way. First, we take the rate
that our frame's clocks count out their time, and compare that to the rate that a moving
clock counts out its time. Before the clock postulate was ever thought of, all that
was known was that when the moving clock has a constant velocity and speed *v* (measured
relative to the speed of light *c*), this ratio of rates is the "gamma factor"

*γ = (1 − v ^{2}) ^{−1/2}* .

In other words, the accelerated clock's rate is identical to the clock rate in a "momentarily comoving inertial frame" (MCIF), which we can imagine is holding an inertial clock that for a brief moment slows to a stop alongside the accelerated clock, so that their relative velocity is momentarily zero. At that moment they are ticking at the same rate. A moment later, the accelerated clock has a new MCIF, again one that is moving momentarily to match its speed, and there is a new inertial clock that briefly slows to a stop alongside the accelerated clock. And again, the rates of accelerated clock and the new inertial one will momentarily be the same.

So the clock postulate says that the rate of an accelerated clock doesn't depend on its
acceleration. But note: the clock postulate does *not* say that the rate of
timing of a moving clock is *unaffected* by its acceleration. The timing rate
will certainly be affected if the acceleration changes the clock's speed of movement,
because its speed determines how fast it counts out its time (i.e. by the factor
*γ*). (The clock rate won't be affected by circular motion at constant
speed.) If that all seems confusing, think of an everyday analogy. If you ride
your bicycle on an icy morning, you get very cold due to the wind chill factor. The
faster you go, the colder your hands get. This wind chill is a function of your
speed, but not your acceleration. Nevertheless, it *is* affected by your
acceleration when your acceleration changes your speed. But regardless of whether
you have a low or a high acceleration, the only thing that matters as far as your cold
hands are concerned is what your current speed is. And for circular motion, two
cyclists who follow different-diameter circles at the same speed will feel the same wind
chill, even though they have different accelerations. So the wind chill factor does
not depend on your acceleration, but it certainly can be affected by your
acceleration.

The clock postulate also implies that the amount of shortening of a moving rod is independent of its acceleration. And also, that the relativistic mass of a moving object also doesn't depend on its acceleration.

The clock postulate is not meant to be obvious, and it can't be proved. It's
*not* merely some kind of trivial result obtained by writing special relativity using non-cartesian
coordinates. Rather, it's a statement about the physical world. But we don't know if it's true; it's
just a postulate. For instance, we can't magically verify it by noting that the Lorentz transform is only a
function of speed, because the Lorentz transform is something that's built before the clock postulate enters the
picture. Also, we cannot simply maintain that an acceleration can be treated as a sequence of constant
velocities that each exist only for an infinitesimal time interval, for the simple reason that an accelerating body
(away from gravity) feels a force, while a constant-velocity body does not. Although the clock postulate does
speak in terms of constant velocities and infinitesimal time intervals, there's no a priori reason why that should
be meaningful or correct. It's just a postulate! This is just like the fact that even though a
1000-sided polygon looks pretty much like a circle, a small piece of a circle can't always be treated as an
infinitesimal straight line: after all, no matter how small the circular arc is, it will always have the same
radius of curvature, whereas a straight line has an infinite radius of curvature. It also won't do to
simply *define* a clock to be a device whose timing is unaffected by its acceleration, because it's not
clear what such a device has got to do with the real world: that is, how well it approximates the thing we wear on
our wrist.

Although the clock postulate is just that, a postulate, it has been verified
experimentally up to extraordinarily high accelerations, as much as *10 ^{18}
g* in fact (see the FAQ What is the
experimental basis of Special Relativity?). Of course, the postulate also speaks
of more than acceleration, it speaks of all derivatives of

This something is the idea of a spacetime metric. Typically when learning special relativity, at some
stage we note that the "interval" between two events, Δ*t ^{2}
− *Δ

But, what is the time as shown on a *noninertial* (i.e. accelerated) clock
connecting two widely separated events? There's no reason why it should be
Δ*t ^{2} − *Δ

d*T ^{2} = *d

since this is the time that elapses on a clock in the MCIF. And we can now integrate
this d*T* along the accelerated clock's world line to get the actual elapsed time
that it shows.

This sort of idea is exactly analogous to the idea of calculating the length of a curve
by dividing it into a large number of short segments, each of which is "almost straight",
and then adding up the lengths of each of those using Pythagoras: d*ℓ ^{2} =
*d

So, the idea of calculating the time elapsed on a clock that accelerates from one event to another is just the same. We're dividing its path into small segments that the clock postulate lets us work with. And just as the curvatures of those small segments in the previous paragraph never become zero (and yet we can ignore them), so too the accelerations of the clock along its path never become zero either—and yet the clock postulate allows us to ignore them too.

This is why we can give some structure to spacetime, because it's possible to talk
about the "length" of a curved world line as being given by the time shown on a clock
moving along that world line, even though the clock itself is accelerating (since the
world line is curved—we are still only talking about flat space here). If the
"length" between two infinitesimally separated spacetime points was something that
depended on how a clock connecting them moved, then it wouldn't be an intrinsically
geometric thing. The clock postulate geometrises relativity by saying that we don't
need to consider how the clock moves; the time (squared) shown by any clock connecting two
closely separated events is just d*t ^{2} − *d

Ultimately, that's why the interval is written using infinitesimals. It has nothing to do with curved spacetime; we use infinitesimals even if the spacetime is flat. We use them because in this form the interval embodies the clock postulate. But now the grand thing is that this idea of spacetime structure allows us to make the transition to general relativity, and the great success of that theory lends plausibility to the parts that make it up—and one of these is the clock postulate.

The clock postulate is one of the ideas we use to build the theory of gravity known as general relativity. People sometimes think (and books sometimes say) that a proper description of accelerating clocks demands general relativity. That's not true at all. General relativity is built on a foundation that includes the clock postulate. Once we've built general relativity, we cannot then turn around and start using it to "explain" the physics of accelerating clocks! That would be circular reasoning. General relativity is built upon the ideas of special relativity, but the physics of accelerating clocks is completely handled by special relativity alone.

Sometimes people say "But if a clock's rate isn't affected by its acceleration, doesn't that mean the Equivalence Principle comes out wrong? If the Equivalence Principle says that a gravitational field is akin to acceleration, shouldn't that imply that a clock isn't affected by a gravitational field, even though the textbooks say it is?"

No, the Equivalence Principle is fine. Again, the confusion here is the same sort of thing as above where we spoke about the wind chill factor. Let's try to see what is happening. Imagine we have a rocket with no fuel. It sits on the launch pad with two occupants, a couple of astronauts who can't see outside and who believe that they are accelerating at 1 g in deep space, far from any gravity.

One of the astronauts sits at the base of the rocket, with the other at its top, and they both send a light beam to each other. Now, general relativity tells us that light loses energy as it climbs up a gravitational field, so we know that the top astronaut will see a redshifted signal. Likewise, the bottom astronaut will see a blueshifted signal, because the light coming down has fallen down the gravitational field and gained some energy en route.

How do the astronauts describe what is going on? They believe they're accelerating in deep space. The top astronaut reasons "By the time the light from the bottom astronaut reaches me, I'll have picked up some speed, so that I'll be receding from the light at a higher rate than previously as I receive it. So it should be redshifted—and yes, so it is!" The bottom astronaut reasons very similarly: "By the time the light from the top astronaut reaches me, I'll have picked up some speed, so that I'll be approaching the light at a higher rate than previously as I receive it. So it should be blueshifted—and yes, so it is!"

As you can see, they both got the right answer, care of the Equivalence
Principle. But their analysis only used their *speed*, not their acceleration
as such. So just like our wind chill factor above, applying the Equivalence
Principle to the case of the rocket doesn't depend on acceleration per se, but it
*does* depend on the result of acceleration: changing speeds!

There are some who state that the clock postulate isn't a postulate at all; that it's simply a theorem can be
proved in the following way. They use some standard reasoning about inertial frames that you'll find in most
books on relativity, but then they apply that reasoning incorrectly to an accelerated frame. Here's their
reasoning. I'll make sure to include all factors of *c* explicitly here.

First, they appeal to a standard and useful description of a "light clock" in relativity, as follows. Sit
yourself on a train that is moving with *constant* velocity relative to the platform, with a torch aimed at
a mirror on the ceiling a distance *L* above you. You send a pulse of light up from the torch at
speed *c* (light has speed *c* in all inertial frames), and let it bounce off the mirror so that it
returns to you some short time Δ*t'* later. You have a receiver that detects the light and
"ticks". Applying "time taken = distance the light travelled divided by light speed", you write down

Δ*t' = 2L/c* .

On the platform, I watch you move past me with speed *v*, and I note that the light moved with
speed *c* along two diagonal paths in a time Δ*t*, which may or may not equal your
Δ*t'*: that's what we want to work out. As the light climbs to the top of the train, the train
moves a distance *v*Δ*t/2*, and similarly for the light coming back down. Pythagoras
tells me that the length of that whole path is twice the square root of *(L ^{2} +
(v*Δ

Δ*t = 2 sqrt(L ^{2} + (v*Δ

which I can solve for Δ*t*, getting

Δ*t = 2L/c/sqrt(1 − v ^{2}/c^{2})* .

But remember that *2L/c* is just Δ*t'*, so finally I have

Δ*t = *Δ*t'/sqrt(1 − v ^{2}/c^{2})* .

In other words, the time taken for the pulse of light to do a round trip "torch-to-mirror-to-torch", as seen
from the platform, is greater by a factor of *1/sqrt(1 − v ^{2}/c^{2})* than the time
taken on the train. This is traditionally one way in which time dilation is derived.

All well and good. Now here's where they mis-apply the above argument to the case of an accelerating
train. They suggest having the train accelerate with some acceleration *a*, so that the distance moved
by the train as the pulse goes up is now not *v*Δ*t/2* but *v*Δ*t/2 +
a*Δ*t ^{2}/2*. That's okay so far. Then they replace
"

Δ*t = *Δ*t'/sqrt(1 − v ^{2}/c^{2})* ,

without ever needing to invoke the clock postulate, saying that this all follows from the first two postulates of special relativity, and the clock postulate is therefore not a third postulate after all, but just a theorem.

Where they went wrong was to assume, with no justification, that the speed of light on the accelerating train is
also *c*. Is it? What do Maxwell's equations say? Maxwell's equations are valid only for
inertial frames, so they don't tell us the speed of light in the accelerating train.

You can use the clock postulate to show that the speed of light does turn out to be *c* *locally*
in the accelerating train: in other words, the light's speed as measured by the train passenger actually turns out
to be a function of its distance from that passenger, but as the light gets closer to the passenger, its speed as
measured by the passenger gets closer to *c*. But those who apply the above inertial calculation to an
accelerating train cannot know or claim a priori that the speed of light is *c* in the light clock on the
accelerating train (and, of course, they're not allowed to use the clock postulate to show that). They are
only assuming that the speed is *c*; and by assuming what turns out to be correct *locally* (and they
never knew anything about "local"), they fluked the right answer, that *γ* has no dependence
on *a*. But because they were not allowed to assume a priori that light travels at speed *c* in
an accelerated frame, their calculation has failed to show that the clock postulate is a theorem.

On a more advanced note, the clock postulate can be generalised to say something about measurements we make in a noninertial frame. First, it tells us that noninertial objects only age and contract by the same gamma factor as that of their MCIF. So, any measurements we make in a noninertial frame that use clocks and rods will be identical to measurements made in our MCIF—at least, if these measurements are made over a small enough region. This is because, in general, different regions of the noninertial frame have different MCIFs, a complicating factor that makes the construction of noninertial frames very difficult. In fact, it can only readily be done for constant-velocity and constant-acceleration frames; and for the last, that is rather difficult.

But we now choose to extend the clock postulate to include *all* measurements
(though perhaps it can be argued that all measurements only ever use clocks and rods
anyway). This idea leads onto "covariance", which is a way of using tensors to write
the language of physics in a way that applies to all frames, noninertial as well as
inertial. How is this done?

Take, for example, the electromagnetic field. Suppose some measurements were made in an inertial lab
frame, and it was determined to have components *A ^{a}* (up to a choice of gauge). Now, we
know from other considerations that

(where repeated indices are always summed over). This much can be shown without the clock postulate, because it deals only with inertial frames. The question is, in this language, how do thea' a' ∂ x b A = ----- A , ... (1) b ∂ x

Suppose we are in a noninertial frame, and wish to know what values the field will take
for us. The clock postulate tells us that the field in our frame,
*A ^{a''}*, will be identical to the field measured by our MCIF,

Again, we make use of the clock postulate. It says that our measurements of distance and time are unaffected by any pseudo forces we feel, so that they are identical to those of our MCIF:

This is just another way of saying thata'' a'dx =dx.

so that we can put it all together to writea'' a' ∂ x ∂ x ----- = ------ , b b ∂ x ∂ x

or finallya'' a' A = A(by our extended clock postulate)a' ∂ x b = ------ A(Lorentz transform between MCIF and lab frame)b ∂ x a'' ∂ x b = ------ A(the clock postulate again),b ∂ x

which is just like (1) above, except now it holds in a noninertial frame! So, we've managed to write our original transformation law (1), which only held between two inertial frames, in a way that looks just the same as (1), except that it's using different coordinates, some from a noninertial frame. Anda'' a'' ∂ x b A = ------ A , b ∂ x