A question about the equivalence principle.

Click For Summary
The discussion centers on the equivalence principle and time dilation in an accelerating spaceship. It is established that, similar to gravitational fields, time flows non-uniformly in non-inertial frames, leading to the clock at the rear of the spaceship running slower than the clock at the front. This effect can be derived using special relativity (SR) without relying on the equivalence principle. The Doppler shift explanation is highlighted as a valid method to understand the discrepancy in clock rates, functioning independently of length contraction. Overall, the conversation emphasizes the complexities of time dilation in both gravitational and accelerating systems.
  • #31
Austin0 said:
Hi Take a look at yuiop's diagrams a couple of posts back. Compare the relative path lengths between forward and backward travel and see if you still think the front to back travel would have greater effect on elapsed time than the travel from back to front.


I have no idea what the diagrams mean.

I think we can say this:

In all cases when the clock did make extra ticks, because of the visit it made upstairs, in these cases the bacward travel had greater effect on elapsed time.
 
Physics news on Phys.org
  • #32
stevendaryl said:
Okay, I did some calculations and I think I have a good grasp now on the clock discrepancies in the accelerated rocket. There are two effects going on:
  1. Because of relativity of simultaneity, if two clocks are synchronized in the "launch" frame, then the forward clock will be farther ahead, as measured in the instantaneous rest frame.
  2. The front clock is traveling slightly slower than the rear clock (as measured in any inertial frame), and so experiences slightly less time dilation.

Here's what's interesting: Early on, effect number 1 is the most important, and effect number 2 is negligible. Much later, when the rocket is traveling very close to the speed of light, effect number 2 is most important, and effect number 1 is negligible.



OK. But effect 1 is not a time dilation effect. Clocks aren't in anyway effected by effect 1.

In our accelerating rocket case clocks are effected only by velocity time dilation.


I have tried to suggest a very simpe thing: After the rocket has accelerated and stopped accelerating, somebody carries a clock from the rear of the rocket to the front of the rocket, where he compares the clock to a clock that was at the front of the rocket all the time, and he observes that the clocks have ticked at different rates, which he may explain by gravitational time dilation, while an outside observer must explain it by velocity time dilation, which was caused by two things: 1: length contraction 2: carrying
 
  • #33
Austin0 said:
I thought we were no longer talking about the case of non contraction.

Well, I was trying to see the contributions of length contraction and relativity of simultaneity to the discrepancy between the front and rear clocks in the comoving frame. Obviously, if there is no length contraction, then it is all due to relativity of simultaneity.

And I agreed with your thought regarding the desynchronization relative to the momentarily comoving frame. I disagreed with your assumption that that effect would dimish over time.
IMO it would increase throughout the complete course of acceleration. Why do you think it would diminish?

Okay, let's pick a time t after the two clocks have been accelerating. Let the event e1 be an event taking place at the rear clock at time t, and let e2 be an event taking place at the front clock at time t. Let the coordinates of e1 be (x1,t) and let the coordinates of e2 be (x2,t), as measured in the launch frame. Let the corresponding coordinates in the momentary inertial rest frame be (x1',t1') and (x2',t2'). Letting δt' be the difference between t1' and t2', and letting δx be the difference between x1 and x2, the Lorentz transforms tell us that:

δt' = γ (δt - v/c2 δx)

We chose the two events so that they are simultaneous in the launch frame, so δt = 0. So we have:

δt' = -γ v/c2 δx

But δx is the distance between the front and the rear, as measured in the launch frame. So by length contraction, that is L/γ, where L is the length of the rocket in its comoving frame. So we have:

δt' = -γ v/c2 L/γ
= - v/c2 L

As time goes on, v→c, so this expression approaches

δt' = -L/c

So the desynchronization effect doesn't keep growing, it approaches a fixed constant (which happens to be the length of time required for light to travel from the rear to the front, in the comoving frame; hmm, not sure what the significance of that is).

In contrast, the discrepancy due to length contraction keeps getting bigger and bigger.
 
  • #34
Austin0 said:
Do you know of any treatment done through Doppler that has been worked out for review??

The brute force approach as you called it. It certainly seems messy in principle and hard to interpret but I would like to know the method of approach.
I posted it a few years back in this post, but the LaTeX has changed and so now it is all math processing errors:
https://www.physicsforums.com/showthread.php?t=236880&page=4

I will try to re-work it and re-post it here.
 
  • #35
Austin0 said:
I wish I could handle the math. I have essentially completely forgotten basic trig and never knew the hyperbolic functions.
So did you derive this from your calculations involving the momentarily comoving inertial frames? Aren't these the Rindler coordinate functions?

Yeah, it's the Rindler coordinates. The Rindler coordinates X and T relate to the coordinates x and t of the launch frame via:

X = √(x2 - (ct)2)

T = c/a arctanh(ct/x)
= c/a arcsinh(ct/X)

where a = the acceleration felt by the rear of the rocket, and where x is not measured from the rear of the rocket, but is instead measured so that the rear of rocket is at x=c2/a; that just makes the formulas come out nicer).

T is not the same as the time shown on clocks aboard the accelerated rocket; that time, τ, is related to T through

τ = T aX/c2
= X/c arcsinh(ct/X)
 
  • #36
DaleSpam said:
I posted it a few years back in this post, but the LaTeX has changed and so now it is all math processing errors:
https://www.physicsforums.com/showthread.php?t=236880&page=4

I will try to re-work it and re-post it here.

It seems like the Doppler derivation is the worst of all possible worlds, as far as difficulty; you have to take into account everything: the changing distances between the two clocks, the time dilations experienced by the clocks, and the transit time for light.

Of course, right after launch, you can compute the Doppler shift approximately by assuming that the clocks are still moving nonrelativistically.
 
  • #37
DaleSpam said:
I posted it a few years back in this post, but the LaTeX has changed and so now it is all math processing errors:
https://www.physicsforums.com/showthread.php?t=236880&page=4

I will try to re-work it and re-post it here.
Here it is with the math processing errors fixed:

I appreciate the effort. I believe that your eq 2.0 is correct to a first order approximation for low velocities, although your derivation was not very clear. I would have derived it this way:

Consider the momentarily co-moving inertial reference frame where the detector is initially at rest at the origin and accelerates in the positive x direction with an acceleration of g and where the emitter emits a photon while at rest at a position of H on the positive x axis. We can express the worldlines of the photon and detector in this reference frame as:
\begin{array}{l}<br /> x_d(t)=\frac{g t^2}{2} \\<br /> x_p(t)=H-c t<br /> \end{array} eq 0.1

We can deterimne the time when the detector meets the photon by setting the two equations in 0.1 equal to each other and solving for t.
\begin{array}{l}<br /> x_d\left(t_d\right)=x_p\left(t_d\right) \\<br /> \frac{g t_d^2}{2}=H-c t_d \\<br /> t_d=\frac{\sqrt{c^2+2 g H}-c}{g}<br /> \end{array} eq 0.2

Multiplying the resulting detection time by g gives us the velocity of the detector relative to the velocity of the emitter.
v=\dot{x}_d(t_d)= g t_d=\sqrt{c^2+2 g H}-c eq 0.3

Substituting eq 0.3 into the relativistic Doppler equation (eq 1.0) and simplifying gives us:
\frac{\omega}{\omega_0}=\frac{1}{\sqrt{\frac{2 c}{\sqrt{c^2+2 g<br /> H}}-1}} eq 1.1

And finally, taking a Taylor series expansion about g=0 and simplifying gives.
\frac{\omega}{\omega_0}=1+\frac{H g}{c^2}+O\left(g^2\right) eq 2.0

Please note that your eq 2.0 is constant wrt time since g H and c are all constant wrt time. Note also that eq 1.0, the relativistic Doppler equation, does not depend on the distance between emission and detection, only the relative velocity of the emitter and detector. The fact that this distance becomes smaller as the rocket's velocity increases is irrelevant, although you keep mentioning it.

Finally, note that your eq 3.0 is dimensionally inconsistent and doesn't follow from eq 2.0.
 
  • #38
stevendaryl said:
It seems like the Doppler derivation is the worst of all possible worlds, as far as difficulty; you have to take into account everything: the changing distances between the two clocks, the time dilations experienced by the clocks, and the transit time for light.
That is why I called it "the brute force approach". However, it has the distinct benefit of giving the same formula as the standard weak field approximation to GR does. I doubt that the length contraction approach does.
 
  • #39
DaleSpam said:
That is why I called it "the brute force approach". However, it has the distinct benefit of giving the same formula as the standard weak field approximation to GR does. I doubt that the length contraction approach does.

As I said, considering only length contraction gives approximately the correct answer long after the launch time, but not immediately after launch.

Let x be the location of the rear of the rocket at time t (t and x measured in the launch frame). Let dx/dt = v.

Let x2 be the location of the front of the rocket at time t, where initially, the front is a distance L away from the rear. Using length contraction, we compute:

x2 = x + L √(1-(v/c)2)

v2 = v - vL/c2 dv/dt 1/√(1-(v/c)2)

Now, we use (derivation skipped) the fact that if the acceleration is g in the rocket's instantaneous rest frame, then in the launch frame, it is g/γ3. Using the fact that γ = 1/√(1-(v/c)2), we get:

v2 = v - vgL/c2 (1-(v/c)2)

Computing 1-(v2/c)2, we get:

1-(v2/c)2 = (1-(v/c)2)(1+2(v/c)2gL/c2)
(ignoring higher powers of L)

√(1-(v2/c)2) = √(1-(v/c)2)(1+(v/c)2gL/c2)

Letting T2 be the time on the front clock, and T be the time on the rear clock, we find:

T2 = ∫√(1-(v/c)2)(1+(v/c)2gL/c2) dt

In the limit v→c (long after launch), this becomes

T2 = T(1 + gL/c2)

(where I used the formula T = ∫√(1-(v/c)2) dt
 
  • #40
stevendaryl said:
In the limit v→c (long after launch), this becomes

T2 = T(1 + gL/c2)

(where I used the formula T = ∫√(1-(v/c)2) dt

That looks like the binomial expansion approximation for

T_2 = \frac{T}{(1 - gL/c^2)}

By the way, is g measured at the front or back (or middle)? It makes a big difference.
 
  • #41
stevendaryl said:
Well, I was trying to see the contributions of length contraction and relativity of simultaneity to the discrepancy between the front and rear clocks in the comoving frame. Obviously, if there is no length contraction, then it is all due to relativity of simultaneity.



Okay, let's pick a time t after the two clocks have been accelerating. Let the event e1 be an event taking place at the rear clock at time t, and let e2 be an event taking place at the front clock at time t. Let the coordinates of e1 be (x1,t) and let the coordinates of e2 be (x2,t), as measured in the launch frame. Let the corresponding coordinates in the momentary inertial rest frame be (x1',t1') and (x2',t2'). Letting δt' be the difference between t1' and t2', and letting δx be the difference between x1 and x2, the Lorentz transforms tell us that:

δt' = γ (δt - v/c2 δx)

We chose the two events so that they are simultaneous in the launch frame, so δt = 0. So we have:

δt' = -γ v/c2 δx

But δx is the distance between the front and the rear, as measured in the launch frame. So by length contraction, that is L/γ, where L is the length of the rocket in its comoving frame. So we have:

δt' = -γ v/c2 L/γ
= - v/c2 L

As time goes on, v→c, so this expression approaches

δt' = -L/c

So the desynchronization effect doesn't keep growing, it approaches a fixed constant (which happens to be the length of time required for light to travel from the rear to the front, in the comoving frame; hmm, not sure what the significance of that is).

In contrast, the discrepancy due to length contraction keeps getting bigger and bigger.

Hi I thought you were comparing the accelerating frames clocks to the momentarily comoving inertial frames.

In the case you are describing here as I understand it you are comparing the launch frame clocks to the CMIRF's correct??

In this case I am fairly certain that throughout the course of acceleration the relationship will be simply vL. Specifically the clock at the rear of any particular MCIRF will be running vL (current v) ahead of the front clock relative to the simultaneity of the launch frame. SO as v increases so will the desynchronization.
But that does not apply to the accelerating clocks without resynchronization because they will retain their original synchronization with the additional increase at the front due to the relatively faster rate of the front clock. SO relative to any MCIRF the front clock will be running ahead which is what I was talking about before when I misunderstood your approach.
 
Last edited:
  • #42
stevendaryl said:
Using length contraction, we compute:

x2 = x + L √(1-(v/c)2)
I am not even sure this step is correct since the Length contraction formula is a feature of the Lorentz transform which relates two inertial frames. I think that you are going to get into some thorny issues about synchronization here.
 
  • #43
stevendaryl said:
As I said, considering only length contraction gives approximately the correct answer long after the launch time, but not immediately after launch.

Let x be the location of the rear of the rocket at time t (t and x measured in the launch frame). Let dx/dt = v.

Let x2 be the location of the front of the rocket at time t, where initially, the front is a distance L away from the rear. Using length contraction, we compute:

x2 = x + L √(1-(v/c)2)

v2 = v - vL/c2 dv/dt 1/√(1-(v/c)2)

Could you explain what you are doing here. I am unclear on the reason for division by acceleration times gamma. Also is it v-vL divided by... or is it v - (vL divided by...)
Sorry my math is not up to your level.

Now, we use (derivation skipped) the fact that if the acceleration is g in the rocket's instantaneous rest frame, then in the launch frame, it is g/γ3. Using the fact that γ = 1/√(1-(v/c)2), we get:

v2 = v - vgL/c2 (1-(v/c)2)

Computing 1-(v2/c)2, we get:

1-(v2/c)2 = (1-(v/c)2)(1+2(v/c)2gL/c2)
(ignoring higher powers of L)

√(1-(v2/c)2) = √(1-(v/c)2)(1+(v/c)2gL/c2)

Letting T2 be the time on the front clock, and T be the time on the rear clock, we find:

T2 = ∫√(1-(v/c)2)(1+(v/c)2gL/c2) dt

In the limit v→c (long after launch), this becomes

T2 = T(1 + gL/c2)

(where I used the formula T = ∫√(1-(v/c)2) dt
Is this the other (non brute) method DaleSpam mentioned?
 
  • #44
No, it seems even more brutish than the brute force method.

The elegant method is to take the transform and use it to compute the metric. Any time dilation will fall out automatically. Or, if you already know the metric, you can even skip the first step.
 
Last edited:
  • #45
DaleSpam said:
Here it is with the math processing errors fixed:

I appreciate the effort. I believe that your eq 2.0 is correct to a first order approximation for low velocities, although your derivation was not very clear. I would have derived it this way:

Consider the momentarily co-moving inertial reference frame where the detector is initially at rest at the origin and accelerates in the positive x direction with an acceleration of g and where the emitter emits a photon while at rest at a position of H on the positive x axis. We can express the worldlines of the photon and detector in this reference frame as:
\begin{array}{l}<br /> x_d(t)=\frac{g t^2}{2} \\<br /> x_p(t)=H-c t<br /> \end{array} eq 0.1

We can deterimne the time when the detector meets the photon by setting the two equations in 0.1 equal to each other and solving for t.
\begin{array}{l}<br /> x_d\left(t_d\right)=x_p\left(t_d\right) \\<br /> \frac{g t_d^2}{2}=H-c t_d \\<br /> t_d=\frac{\sqrt{c^2+2 g H}-c}{g}<br /> \end{array} eq 0.2

Multiplying the resulting detection time by g gives us the velocity of the detector relative to the velocity of the emitter.
v=\dot{x}_d(t_d)= g t_d=\sqrt{c^2+2 g H}-c eq 0.3

Substituting eq 0.3 into the relativistic Doppler equation (eq 1.0) and simplifying gives us:
\frac{\omega}{\omega_0}=\frac{1}{\sqrt{\frac{2 c}{\sqrt{c^2+2 g<br /> H}}-1}} eq 1.1

And finally, taking a Taylor series expansion about g=0 and simplifying gives.
\frac{\omega}{\omega_0}=1+\frac{H g}{c^2}+O\left(g^2\right) eq 2.0

Please note that your eq 2.0 is constant wrt time since g H and c are all constant wrt time. Note also that eq 1.0, the relativistic Doppler equation, does not depend on the distance between emission and detection, only the relative velocity of the emitter and detector. The fact that this distance becomes smaller as the rocket's velocity increases is irrelevant, although you keep mentioning it.

Finally, note that your eq 3.0 is dimensionally inconsistent and doesn't follow from eq 2.0.

Hi I can folow most of this but am unsure about the conceptual setup.

My assumption is that the emitter at H is at the front of the accelerating system
so at eq 3 the relative velocity is reated to the MCIRF at the time of emission . Is this correct?
If this is the case then H is constant wrt the MCIRF's but not to the launch frame?

What is the Taylor series expansion doing in this case??

Does this caculation result in a constant gamma between front and back??

Thanks
 
  • #46
DaleSpam said:
No, it seems even more brutish than the brute force method.

The elegant method is to take the transform and use it to compute the metric. Any time dilation will fall out automatically. Or, if you already know the metric, you can even skip the first step.

Well your description is certainly elegant: Minimal, refined and completely enigmatic.

I can think of possible interpretations for the first sentance but nary a glimpse of falling dilations. Just kidding!. Could you perhaps be a little more exspansive in explaining what may be to you, obvious?

Thanks
 
  • #47
Austin0 said:
My assumption is that the emitter at H is at the front of the accelerating system
Sorry about the confusion. It is always clearer in my head than on paper. Yes, the emitter is assumed to be at the front.

Austin0 said:
so at eq 3 the relative velocity is reated to the MCIRF at the time of emission . Is this correct?
Yes.

Austin0 said:
If this is the case then H is constant wrt the MCIRF's but not to the launch frame?
Yes, that is an assumption that I never stated explicitly. I was assuming a rocket under continuous acceleration where any transient strains had long since died out.

Austin0 said:
What is the Taylor series expansion doing in this case??
Approximating the time dilation to first order.

Austin0 said:
Does this caculation result in a constant gamma between front and back??
Yes.
 
  • #48
Austin0 said:
Could you perhaps be a little more exspansive in explaining what may be to you, obvious?
It will probably be easier to just work a couple of examples. I will try to do that tomorrow.
 
  • #49
DaleSpam said:
I am not even sure this step is correct since the Length contraction formula is a feature of the Lorentz transform which relates two inertial frames. I think that you are going to get into some thorny issues about synchronization here.

The formula I gave was for the length of the rocket as viewed in the launch frame, under the assumption that the original length L is very small compared with the characteristic length c2/g, where g is the acceleration of the rear of the rocket. In this case, the length of the rocket in the comoving frame will be L, and you can transform back to get the length in the original frame as L/gamma. Of course, the various parts of the rocket are not at rest relative to each other if the rocket is accelerating, so the "comoving frame" is slightly ambiguous, but if the rocket is small enough compared with c2/g, that doesn't make much difference.

The exact result for a Born-rigid rocket undergoing constant proper acceleration is this:

  1. xrear = √((ct)2 + R2)
  2. xfront = √((ct)2 + (R+L)2)
    Taking the derivative of equation 1 to find the velocity, and expanding equation 2 in powers of L gives us the following:
  3. xfront = xrear + L √(1-(vrear/c)2)
where R is the characteristic length c2/g.

With the given form for xrear, we can take a derivative to get vrear, and we can prove that
√(1-(vrear/c)2) = R/xrear
which is what I used for equation 3.

I suspect that my derivation is actually circular, in a sense; the way that you can derive that the front of the rocket must have the form in equation 2 is by demanding that each infinitesimal segment dL of the rocket has length dL/γ in the moving frame, where γ is computed for that segment.
 
  • #50
Austin0 said:
Hi I thought you were comparing the accelerating frames clocks to the momentarily comoving inertial frames.

No. There actually is not very much difference between those two, if the length of the rocket is sufficiently small. I was comparing the comoving inertial frame to the launch frame.

In this case I am fairly certain that throughout the course of acceleration the relationship will be simply vL. Specifically the clock at the rear of any particular MCIRF will be running vL (current v) ahead of the front clock relative to the simultaneity of the launch frame. SO as v increases so will the desynchronization.

I'm not sure that we are disagreeing. I said that long after launching, the velocity approaches c, and so the desynchronization approaches the constant L/c.

But that does not apply to the accelerating clocks without resynchronization because they will retain their original synchronization with the additional increase at the front due to the relatively faster rate of the front clock. SO relative to any MCIRF the front clock will be running ahead which is what I was talking about before when I misunderstood your approach.

I'm not sure whether we disagree, or not. In the comoving frame, the front clock always runs at a rate (R+L)/R faster than the rear clock, where L is the length of the rocket, and R is the characteristic length c2/g (where g is the acceleration of the rear). In the launch frame, the rates for both clocks start out the same, but the ratio gradually approaches the same value.
 
  • #51
Austin0 said:
Is this the other (non brute) method DaleSpam mentioned?

I don't know.

Let me do the derivation a little more slowly.

I'm assuming that when the rear of the rocket is traveling at speed vrear, then the length of the rocket will be approximately L√(1-(vrear/c)2) by length contraction (where L is the original length of the rocket). That means that if we let xrear be the location of the rear, and xfront be the location of the front, then, approximately:

xfront = xrear + L√(1-(vrear/c)2)

Now, to compute vfront, the velocity of the front of the rocket, we take a derivative of xfront with respect to t.

  1. d/dt xfront = vfront (by definition)
  2. d/dt xrear = vrear (by definition)
  3. d/dt L√(1-(vrear/c)2)
    = -Lvrear/c2 (d/dt vrear)/√(1-(vrear/c)2)

Are you asking how I derived equation 3? It's just calculus, using the fact that
d/dt f(vrear ) = (d/dvrear f(vrear )) dvrear /dt

In this particular case f(vrear ) = L√(1-(vrear/c)2)
d/dvrear L√(1-(vrear/c)2)
= -Lvrear/c2/√(1-(vrear/c)2)

Putting equations 1,2, and 3 together gives
vfront = vrear - Lvrear/c2 (d/dt vrear)/√(1-(vrear/c)2)
 
  • #52
stevendaryl said:
The formula I gave was for the length of the rocket as viewed in the launch frame, under the assumption that the original length L is very small compared with the characteristic length c2/g, where g is the acceleration of the rear of the rocket. In this case, the length of the rocket in the comoving frame will be L, and you can transform back to get the length in the original frame as L/gamma. Of course, the various parts of the rocket are not at rest relative to each other if the rocket is accelerating, so the "comoving frame" is slightly ambiguous, but if the rocket is small enough compared with c2/g, that doesn't make much difference.
They are not at rest wrt each other in a given inertial reference frame, when the MCIRF of accelerating rocket has significant relative velocity to that given inertial reference frame, but momentarily in any MCIRF they are at rest wrt each other and in the accelerating reference frame of the rocket they are permanently at rest wrt each other. On board the rocket, any part of the rocket has a constant radar (and ruler) distance from any other part of the rocket so in that sense they are at rest wrt each other. The ambiguity only arises if you fail to specify which reference frame the measurements are made from.
 
  • #53
stevendaryl said:
I'm not sure that we are disagreeing. I said that long after launching, the velocity approaches c, and so the desynchronization approaches the constant L/c.
I am not sure what you are getting at here. Let's say the clocks are initially synchronised in the launch frame. After launch let's say that when 1 second elapses on the rear clock, 4 seconds elapses on the front clock in the MCIRF. It then follows that after 2 seconds elapses on the rear clock, 8 seconds will have elapsed on the front clock in the new MCIRF in which the rocket is momentarily at rest. The ratio between the time elapsed on the front clock versus the rear clock is always constant in any given MCIRF. If we stay with the measurements made in the initial inertial launch frame, then the desynchronisation is always increasing.

stevendaryl said:
I'm not sure whether we disagree, or not. In the comoving frame, the front clock always runs at a rate (R+L)/R faster than the rear clock, where L is the length of the rocket, and R is the characteristic length c2/g (where g is the acceleration of the rear).
This approximation is good if R is large and L is small, but becomes very inaccurate if R is small and L is large.
 
  • #54
yuiop said:
They are not at rest wrt each other in a given inertial reference frame, when the MCIRF of accelerating rocket has significant relative velocity to that given inertial reference frame, but momentarily in any MCIRF they are at rest wrt each other

You are exactly right! Somehow, either I never did the calculation, or forgot it, but I just convinced myself of that this morning. The description of the rocket's position and velocity as a function of time in the launch frame I always knew was this:

  1. xrear = √((ct)2 + R2)
  2. vrear = c2 t/√((ct)2 + R2)
  3. xfront = √((ct)2 + (R+L)2)
  4. vfront = c2 t/√((ct)2 + (R+L)2)

(So at time t=0, both the front and the rear have speed 0.) But what's amazing is that equations 1-4 aren't just true in the launch frame, it's true in every inertial frame in which the rocket is momentarily at rest. That's pretty amazing; the rocket launches at time t=0 in frame F. At some time later, the rocket is at rest in some frame F' moving at speed v relative to F'. That time is t'=0, according to frame F', and equations 1-4 still hold, with x replaced by x' and t replaced by t'.
 
  • #55
stevendaryl said:
... In the comoving frame, the front clock always runs at a rate (R+L)/R faster than the rear clock, where L is the length of the rocket, and R is the characteristic length c2/g (where g is the acceleration of the rear).
yuiop said:
This approximation is good if R is large and L is small, but becomes very inaccurate if R is small and L is large.
I may have to retract this last claim and you may be right here! The analysis I did with graphical software may have had limitations due to the accuracy of the software.

Here is a small "derivation" of the ratio of the clock rates being proportional to the ratio (R+L)/R.

The velocity of a clock on the rocket after proper time T is given as:

v = c - tanh(aT/c)

This can be rearranged to:

T = atanh(c-v)*c/a

Since the acceleration is equal to c^2/r this becomes:

T = atanh(c-v)*r/c

The ratio of the clock rates of two clocks at r1 and r2 respectively is then given by:

\frac{T_2}{T_1} = \frac{ atanh(c-v_2)*r_2/c}{atanh(c-v_1)*r_1/c}

In any given MCIRF, v is equal for all clocks at rest in that MCIRF, from the point of view of any other inertial reference frame, so we can assume v1 = v2 and can conclude:

\frac{T_2}{T_1} = \frac{r_2}{r_1} = \frac{r_1+L}{r_1}

This is how more time elapses (from launch) on the front clock relative to the rear clock as seen in any MCIRF and is also a measure of the constant redshift seen by an observer at r2 of a signal at r1.
 
  • #56
yuiop said:
I am not sure what you are getting at here. Let's say the clocks are initially synchronised in the launch frame. After launch let's say that when 1 second elapses on the rear clock, 4 seconds elapses on the front clock in the MCIRF. It then follows that after 2 seconds elapses on the rear clock, 8 seconds will have elapsed on the front clock in the new MCIRF in which the rocket is momentarily at rest. The ratio between the time elapsed on the front clock versus the rear clock is always constant in any given MCIRF. If we stay with the measurements made in the initial inertial launch frame, then the desynchronisation is always increasing. This approximation is good if R is large and L is small, but becomes very inaccurate if R is small and L is large.

I misunderstood how you were using the word "desynchronization". I was meaning "relativity of simultaneity", the fact that clocks that are synchronized in one frame are not synchronized in another frame. You are using to mean the discrepancy between the two clocks (regardless of the cause).

Let me try to explain what I meant by the two causes for the discrepancy between the two clocks.

Let e1 be some event taking place at the rear clock. Let T1 be the time on that clock at that event.

Let e2 be some event taking place at the front clock that is simultaneous with e1, according to the launch frame. Let T2 be the time on that clock at that event.

Let e3 be some event taking place at the front clock that is simultaneous with e1, according to the instantaneous inertial reference frame of the rocket. Let T3 be the time on that clock at that event.

Let δT1 = T2 - T1
Let δT2 = T3 - T2

δT1 is completely due to length contraction; the front travels less than the rear, and so experiences less time dilation.

δT2 is an additional effect due to relativity of simultaneity.

In the instantaneous rest frame of the rocket, the discrepancy between the times on the two clocks is the sum of the two δs. What I've been saying is that soon after launch, δT2 is much bigger than δT1. Long after launch, δT1 eventually becomes much bigger than δT2. (The latter approaches a maximum value of L/c). In the accelerated reference frame of the rocket itself, the only relevant number is the sum of the two, which grows steadily at a constant rate.
 
  • #57
Austin0 said:
Could you perhaps be a little more exspansive in explaining what may be to you, obvious?
OK, so what I was talking about was using the metric to get an expression for time dilation as follows:

Time dilation in Minkowski spacetime:
c^2 d\tau^2=c^2 dt^2-dx^2-dy^2-dz^2\frac{d\tau^2}{dt^2}=1-\frac{1}{c^2}\left(\frac{dx^2}{dt^2}+\frac{dy^2}{dt^2}+\frac{dz^2}{dt^2}\right)\frac{d\tau}{dt}=\sqrt{1-\frac{v^2}{c^2}}=1/\gamma

Time dilation in Schwarzschild spacetime:
c^2 d\tau^2 = \left(1-\frac{R}{r}\right) c^2 dt^2 - \left(1-\frac{R}{r}\right)^{-1} dr^2 - r^2 \left( d\theta^2 + sin^2\theta d\phi^2 \right)\frac{d\tau^2}{dt^2} = \left(1-\frac{R}{r}\right) - \frac{1}{c^2}\left(1-\frac{R}{r}\right)^{-1} \frac{dr^2}{dt^2} - \frac{r^2}{c^2} \left( \frac{d\theta^2}{dt^2} + sin^2\theta \frac{d\phi^2}{dt^2} \right)for an object at rest in the Schwarzschild coordinates all of the spatial derivatives are 0 leaving\frac{d\tau}{dt} = \sqrt{\left(1-\frac{R}{r}\right) }

Time dilation in Rindler coordinates:
c^2 d\tau^2 = \frac{g^2 x^2}{c^2}dt^2 - dx^2 - dy^2 - dz^2\frac{d\tau^2}{dt^2} = \frac{g^2 x^2}{c^4} -\frac{1}{c^2}\left( \frac{dx^2}{dt^2} + \frac{dy^2}{dt^2} + \frac{dz^2}{dt^2} \right)\frac{d\tau}{dt} = \sqrt{\frac{g^2 x^2}{c^4} -\frac{v^2}{c^2}}for an object at rest in the Rindler coordinates v=0 leaving\frac{d\tau}{dt} = \frac{g x}{c^2}
 
  • #58
yuiop said:
I may have to retract this last claim and you may be right here! The analysis I did with graphical software may have had limitations due to the accuracy of the software.

Here is a small "derivation" of the ratio of the clock rates being proportional to the ratio (R+L)/R.

The velocity of a clock on the rocket after proper time T is given as:

v = c - tanh(aT/c)

Are you sure about that? The formulas that I use are:
v = c tanh(aT/c)
not
v = c - tanh(aT/c)
 
  • #59
yuiop said:
... so we can assume v1 = v2 and can conclude:

\frac{T_2}{T_1} = \frac{r_2}{r_1} = \frac{r_1+L}{r_1}

This is how more time elapses (from launch) on the front clock relative to the rear clock as seen in any MCIRF and is also a measure of the constant redshift seen by an observer at r2 of a signal at r1.

I think it is interesting to expand on this relation T2/T1 = R2/R1 (which appears to be an exact result) by comparing it to the gravitational time dilation in the Schwarzschild metric.

First the time dilation ratio in the Born rigid acceleration case, as a function of constant proper acceleration is given by:

\frac{T_2}{T_1} = \frac{r_2}{r_1} = \frac{a_1}{a_2}

In the Schwarzschild metric the time dilation ratio of two stationary clocks in the field is given by:

\frac{T_2}{T_1} = \frac{\sqrt{1-2GM/(r_2c^2)}}{\sqrt{1-2GM/(r_1c^2)}}

and when we express this in terms of proper acceleration it becomes:

\frac{T_2}{T_1} = \sqrt{\frac{(c^2-2a_2r_2)}{(c^2-2a_1 r_1)}}

This appears to be very different to the Born rigid acceleration case with possibly a poor equivalence principle correlation, but maybe I am missing a gamma cubed factor in there somewhere between proper acceleration and coordinate acceleration. Any ideas?
 
Last edited:
  • #60
stevendaryl said:
Are you sure about that? The formulas that I use are:
v = c tanh(aT/c)
not
v = c - tanh(aT/c)

Oops, I slipped up in quoting the given formula. Here is the derivation again using your correct expression. (The end result is still the same).

===============================

Here is a small "derivation" of the ratio of the clock rates being proportional to the ratio (R+L)/R.

The velocity of a clock on the rocket after proper time T is given as:

v = c * tanh(aT/c)

This can be rearranged to:

T = atanh(v/c)*c/a

Since the acceleration is equal to c^2/r this becomes:

T = atanh(v/c)*r/c

The ratio of the clock rates of two clocks at r1 and r2 respectively is then given by:

\frac{T_2}{T_1} = \frac{ atanh(v_2/c)*r_2/c}{atanh(v_1/c)*r_1/c}

In any given MCIRF, v is equal for all clocks at rest in that MCIRF, from the point of view of any other inertial reference frame, so we can assume v1 = v2 and can conclude:

\frac{T_2}{T_1} = \frac{r_2}{r_1} = \frac{r_1+L}{r_1}

This is how much more time elapses (from launch) on the front clock relative to the rear clock as seen in any MCIRF and is also a measure of the constant redshift seen by an observer at r2 of a signal at r1

===============================

Hopefully I got it right this time :)
 

Similar threads

  • · Replies 44 ·
2
Replies
44
Views
6K
  • · Replies 18 ·
Replies
18
Views
2K
  • · Replies 9 ·
Replies
9
Views
2K
  • · Replies 32 ·
2
Replies
32
Views
4K
Replies
8
Views
2K
  • · Replies 115 ·
4
Replies
115
Views
8K
  • · Replies 36 ·
2
Replies
36
Views
4K
Replies
60
Views
8K
  • · Replies 8 ·
Replies
8
Views
2K
Replies
11
Views
2K