This paradox is very common it seems, in which A sees B's clock running slow and B sees A's clock running slow. Here is the question a little more concretely.
Let's say B flies by A's spaceship. If B's clock advances $t$, then in that time A's clock advances $\gamma t$ through time dilation (This is easily shown if there is a light clock next to B). Now from A's perspective (assume there is a light clock next to A), during that same time interval, he sees B's clock run slower and thus this time interval must be $\gamma^2 t$. Equating the time intervals gives $t = \gamma^2 t$ and $\gamma = 1$, which is clearly wrong. How is this reconciled?
Answer
It's reconciled by the relativity of simultaneity. Each observer is assumed to measure the time of events using local readings on a network of clocks at rest relative to that observer, which are defined as "synchronized" in that observer's own rest frame using the Einstein synchronization convention. But because this convention is based on each observer assuming that light moves at a constant speed relative to themselves, different observers will disagree about simultaneity, each thinking the clocks of the other are out-of-sync.
So, if one of your clocks is moving at 0.6c relative to me, I might first measure your clock reading T=0 seconds as it passed a clock of mine also reading t=0 s, then later I might measure your clock reading T=20 s as it passed a clock of mine reading t=25 s, at a distance of 15 light-seconds to the right of my other clock according to my ruler. From this I conclude that your clock only ticked 20 seconds in 25 seconds of my time, meaning your clock was slowed down by a factor of 0.8--but this depends on the assumption that my two clocks were synchronized, which isn't true in your own frame. If two clocks have a distance of L between them in their rest frame and are synchronized in that frame, then from the perspective of another frame which sees them moving at speed v, at any given moment the clock in the rear will have a time that's ahead of the clock in the lead by an amount $vL/c^2$, so in this example where the two clocks are 15 light-seconds apart in my rest frame, and you see them moving at 0.6c, the rear clock will have a time that's ahead of the lead clock's time by (0.6 light-seconds/second)(15 light-seconds)/(1 light-second/second)^2 = 9 seconds. So in your frame, at the same moment your clock was reading T=0 s and passing my left clock reading t=0 s, my right clock (which is in the 'rear' from your point of view, since both are traveling left in your frame) read t=9 seconds. Then 20 seconds later in your frame, your clock passes my right clock, and in your frame it's my clocks that are running slow by a factor of 0.8, so after 20 seconds my clocks have only ticked forward by 16 seconds. But since the right clock started at t=9 seconds, then after ticking an additional 16 seconds it will have reached t=25 seconds. So this is how you can consistently explain the fact that when your clock passed my right clock, your clock read T=20 s and mine read t=25 s, even though my clocks were running slower than yours in your own frame.
Here are some diagrams showing in a more visual way how observers using their own rulers and clocks can each measure the other's rulers as length-contracted and the other's clocks as slowed-down and out-of-sync, in a completely symmetrical way. In this example, we have two rulers with clocks mounted on them moving alongside each other, and in order to make the math work out neatly, the relative velocity of the two rulers is (square root of 3)/2 * light speed, or about 259.628 meters per microsecond. This means that each ruler will observe the other one’s clocks tick exactly half as fast as their own, and will see the other ruler's distance-markings to be squashed by a factor of two. Also, I have drawn the markings on the rulers at intervals of 173.085 meters apart—the reason for this is again just to make things work out neatly, it will mean that observers on each ruler will see the other ruler moving at 1.5 markings/microsecond relative to themselves, and that an observer on one ruler will see clocks on the other ruler that are this distance apart (as measured by his own ruler) to be out-of-sync by exactly 1 microsecond, some more nice round numbers.
Given all this, here is how the situation would look at 0 microseconds, 1 microsecond, and 2 microseconds, in the frame of ruler A:
And here’s how the situation would look at 0 microseconds, 1 microsecond, and 2 microseconds, in the frame of ruler B:
Some things to notice in these diagrams:
in each ruler's frame, it is at rest while the other ruler is moving sideways at 259.6 meters/microsecond (ruler A sees ruler B moving to the right, while ruler B sees ruler A moving to the left).
In each ruler's frame, its own clocks are all synchronized, but the other ruler's clocks are all out-of-sync.
In each ruler's frame, each individual clock on the other ruler ticks at half the normal rate. For example, in the diagram of ruler A’s frame, look at the clock with the green hand on the -519.3 meter mark on ruler B--this clock first reads 1.5 microseconds, then 2 microseconds, then 2.5 microseconds. Likewise, in the diagram of ruler B’s frame, look at the clock with the green hand on the 519.3 meter mark on ruler A—this clock also goes from 1.5 microseconds to 2 microseconds to 2.5 microseconds.
Despite these differences, they always agree on which events on their own ruler coincide in time and location with which events on the other. If you have a particular clock at a particular location on one ruler showing a particular time, then if you look at the clock right next to it on the other ruler at that moment, you will get the same answer to what that other clock reads and what marking it’s on regardless of which frame you’re using. Here’s one example:
You can look at the diagrams to see other examples, or extrapolate them further in a given direction then I actually drew them, and to later times, to find even more. In every case, two events which coincide in one reference frame also coincide in the other.
No comments:
Post a Comment