Dismiss Notice
Join Physics Forums Today!
The friendliest, high quality science and math community on the planet! Everyone who loves science is here!

Accelerating Light Clock

  1. Sep 24, 2013 #1
    This is an analysis of how a classic Einstein light clock behaves when accelerated orthogonal to its main axis. The results might be considered slightly controversial, so I am putting the details of the calculation here so that they can be checked.


    Consider a light clock that has its long axis parallel to the y axis that is being accelerated in the x direction as per this diagram:

    https://www.physicsforums.com/attachment.php?attachmentid=62152&stc=1&d=1380051964


    Let the emitter end of the light clock start at x=y=t=0 and accelerate with constant proper acceleration g.
    At times t1, t2, t3 the light clock is at x1, x2, x3 respectively. To find the round trip time of the photon (or the time of one tick of light clock) we need to find ##(\Delta t_2 + \Delta t_1) = (t_3-t_1) ##

    Given t1 we can find t2 starting from the obvious Pythagorus relationship:

    ##L^2 + (\Delta x_1)^2 = c^2( \Delta t_1)^2##

    ##L^2 + (x_2-x_1)^2 = c^2 (t_2-t_1)^2##

    Using the equations of relativistic accelerating motion given here the spatial coordinates can be expressed in terms of the time coordinates via the relationship (using units such that c=1), ##x =\sqrt{1/g^2 + t^2}## giving :

    ##L^2 + \left(\sqrt{1/g^2+t_2^2}-\sqrt{1/g^2+t_1^1}\right)^2 = (t_2-t_1)^2##

    This can rearranged to give t2 in quadratic form:

    ##t_2^2 - t_2*t_1(2+L^2g^2) + (t_1^2- L^4g^2/4 - L^2) = 0##

    and solved in the usual way to give:

    ##t_2 = t_1(1+L^2g^2/2) \pm \sqrt{t_1^2((1+L^2g^2/2)^2 -1) + L^2(1+L^2g^2/4)}##

    There are two possible solutions. When the sign of the second term is positive t2>t1 and when it is negative t2<t1 so the positive term is chosen. (Note that by swapping t2 for t1 and vice versa we can find t1 using the solution with the negative second term, if we are given t2.)

    The above expression is generic and we can find t3 by substituting t3 for t2 and t2 for t1 in the above expression:

    ##t_3 = t_2(1+L^2g^2/2) + \sqrt{t_2^2((1+L^2g^2/2)^2 -1) + L^2(1+L^2g^2/4)}##

    The above calculations show that given t1 we can find t2 and t3 and therefore the round trip time (t3-t1). We can find t1 given any initial conditions such as initial position x1 or initial velocity v1 at the time the photon is emitted at the start of a tick, using the relativistic equations of accelerating motion, given in the link above.

    The round trip time (t3-t1) is the coordinate time in the initial inertial frame. The time interval of the light clock (its tick rate) according to a comoving (accelerating) observer is given by:

    ##(t_3' - t_1') = (1/g)\left(\sinh^{-1}(g*t_3) - \sinh^{-1}(g*t_1)\right)##

    Assuming I have done the calculations correctly, the proper frequency of the light clock does not keep time with a co-accelerating ideal clock. The equations are time dependent and therefore also dependent on the instantaneous velocity or position of the clock. This is a slightly curious result, and demonstrates that while the ruler length of a measurement orthogonal to the direction of motion is constant and not subject to length contraction, the radar length is constantly changing, (except for the special case when g/c=1). It turns out that when g/c<1 the frequency of the light clock increases with increasing velocity and conversely the frequency slows down with increasing velocity of the light clock when g/c>1.

    Before anyone gets too excited and thinks the accelerating light clock indicates absolute motion, bear in mind that it only records its velocity relative to the time it started accelerating. If the light clock stops accelerating and starts again it restarts from v=0. Effectively it does nothing more than multiplying the output of a traditional accelerometer by the elapsed time to estimate the instantaneous velocity.

    Anyway, I won't dwell too long on the implications of the results found here, just in case I have made a glaring mistake. Hopefully someone here will do the honours and check the calculations.

    P.S. From some old discussions on PF, we know that a light clock that has constant proper acceleration parallel to its main axis (undergoing Born rigid motion), does maintain constant proper frequency. It follows that a Michelson-Morley type arrangement of two light clocks at right angles to each other will show an interference fringe shift under constant proper acceleration. There is no reason to think that a MMX type arrangement would show a fringe shift when stationary in a gravitational field due to the acceleration of gravity.

    This is an interesting exception to the equivalence principle which is not due to tidal effects. How does a light clock distinguish between acceleration in flat space, which causes an actual change in location and velocity, and gravitational acceleration when there is no actual change in location and velocity relative to the gravitational field?
     

    Attached Files:

    Last edited: Sep 24, 2013
  2. jcsd
  3. Sep 24, 2013 #2

    PAllen

    User Avatar
    Science Advisor
    Gold Member

    This implies, with certainty, that there is a mistake in your analysis. I don't have time to look for it now, but the only sort of exceptions to the equivalence principle involve charges or certain special devices that directly sense curvature at a point (which really means they can sense tidal gravity no matter how small the device). A light clock would not be one of these devices.

    (An example of a special device of this type is a free falling drop of perfect fluid. It is not perfectly spherical in gravity, and the ratio of its longer dimension to it shorter is constant, independent of size [ as long as it is not too big]. It thus directly measures the second derivative of potential.)
     
  4. Sep 25, 2013 #3
    The distance between the two mirrors should be in the equation. (And as already mentioned, the velocity the of mirrors should not be there)

    When the distance is large an observer that is co-moving with the mirrors will say something like: "The light takes the fastest route in this curved space-time. Light saves quite a lot of time by taking the route that visits quite high altitude."
     
  5. Sep 25, 2013 #4

    Mentz114

    User Avatar
    Gold Member

    I don't know where the rocket equations you linked to come from. I've done this instead.

    The acceleration is 1/x in the x direction. The light clock extends into the y-direction at constant x.

    Using ##ds^2=x^2\ dt^2 - dx^2 -dy^2 - dz^2## with ##ds^2=0## we get ##x_0dt = dy## (for some fixed ##x_0##). For a clock following the stationary (or comoving) worldline ##u^\mu=\partial_t/x## we get ##d\tau=x_0dt##. Combining this with ##x_0dt = dy## gives ##d\tau = dy## which on integration gives ##\tau=y_2-y_1##. Which, I think, shows that the light clock will tick as the same rate as any other clock at ##x_0##.
     
  6. Sep 25, 2013 #5

    Ibix

    User Avatar
    Science Advisor

    For ease of computation, you can simplify this expression to:
    [tex]t_2=\left(L^2g^2/2+1\right)t_1+L\sqrt{\frac{1}{4}L^2g^2+1}\sqrt{g^2t_1^2+1}[/tex]
    where I have selected the positive solution, as you did. Also as you say, the expression for ##t_3## as a function of ##t_2## is the same form.

    You then give the following formula for the proper time interval:
    Have you tried plotting this? The ancient version of OpenOffice I've got on this thing won't open xlsx, and I'm not going to upgrade an half past midnight... I've only done it in said ancient version of OpenOffice's spreadsheet, but the graph is flat to as many decimal places as that will provide - see the attachment. Since that is in accordance with the expectations of relativity I'm not going to bother going through the algebra to prove that it's constant. I suspect that taking the sinh of both sides will get you there if you want; otherwise differentiate with respect to ##t_1## and see if that is zero.
     

    Attached Files:

    Last edited: Sep 25, 2013
  7. Sep 25, 2013 #6
    It is! It is the length L shown next to the red line (representing the light click) in the diagram. L is the initial and final equations. You are right to expect that v should drop out of the final equations, but it does not ....
    I was not quite sure what you meant by this at first, but I think I do now. (See below).

    That page has been referred to often in these forums and no one has had any issues with before. The equations agree with equations given for Rindler coordinates from other sources except for notation differences and the fact that the rocket equations have a spatial offset of 1/d to make the accelerating particle start from the origin. For example "en.wikipedia.org/wiki/Rindler_coordinates" [Broken] gives the spatial coordinate in the accelerating frame as ##x = \sqrt{X^2-T^2}##. Since the light clock is stationary in the accelerating frame we can replace x with 1/g to obtain ##X = \sqrt{1/g^2 + T^2}## where X is the distance travelled in the inertial frame. This is essentially the equation given in the rocket page when you subtract the offset. Also note that the rocket page uses lower case for the Minkowski coordinates and upper case for the Rindler coordinates and Wikipedia use exactly the opposite convention.

    For the time coordinate transformation, Wikipedia gives ##T =x \sinh(gt) ## which solves to ##t = \sinh^{-1}(T/x)*(1/g) = \sinh^{-1}(gT)*(1/g)## which is equivalent to the equation on the rocket page except for the reversed notation.

    Equation 2.4 of this paper on accelerated motion is also equivalent to the equation I used, except for the reversed notation again and is the same as the rocket page equation except the 1/g offset.

    I agree that your calculation is correct. I think the disagreement in our conclusions comes about because in your method, the photon is travelling precisely along the y axis of the accelerating reference frame, while in my method the photon follows a curved path in the accelerating reference frame. In my method the photon only travels a straight path in the Minkowski frame. This straight path transforms to a curved path in the Rindler frame and does not remain on the y axis. I think this is what jartsa was alluding to when he said the photon takes a route that spends more time at 'high altitude'.

    <EDIT> I have deleted he last part of this post while I analyse the spreadsheet uploaded by Ibix. His method appears to work (i.e constant frequency) for the accelerated light clock and he is using very similar methods to mine. Looks like I will have to find out where mine has gone wrong. :(
     
    Last edited by a moderator: May 6, 2017
  8. Sep 25, 2013 #7

    PeterDonis

    User Avatar
    2016 Award

    Staff: Mentor

    I haven't worked through this calculation in detail (though I hope to have time to soon), but this doesn't make sense, because the worldlines of both ends of the light clock are integral curves of Killing vector fields, so you can pick any pair of "comoving" events along those worldlines you like and call the time of that pair of events "t = 0", and do a local analysis of the light clock centered on that pair of events, and the analysis will come out the same. It will also come out the same as doing it in a local inertial frame in a gravity field, so if the clock doesn't change in a gravity field, it shouldn't change in the accelerated frame here either.

    Put another way, a key characteristic of Killing motions is that nothing changes along them, but your calculation purports to show that something is changing along a Killing motion, so there must be a mistake somewhere.

    I do agree that, in the accelerated frame, the light's path should appear curved; that's essentially the same argument that is used to show that gravitational fields must bend light. So Mentz114's analysis, which assumes that dt and dy are the only nonzero differentials along the light's path in the accelerated frame, can't be right as it stands either.

    On a quick skim of your OP, I did notice one other thing that's worth asking about: how are you accounting for length contraction along the x axis? As the velocity of the light clock in the x direction increases, it will appear more and more length contracted in the inertial frame in which you are doing the calculation; but that means a length contraction factor should appear somewhere in your Pythagorean theorem formula, and I don't see one.
     
  9. Sep 25, 2013 #8
    Hi Peter. See the edit at the end of my last post. ibix appears to have cracked this. I notice he only uses times t1 and t3 in his spreadsheet, whereas i was using the velocities at time t1 and t3. I am still looking for the differences. You are right that I did not take length contraction into account and I don't think that is what is causing the problem. All the measurements for the Pythagorean calculation are made entirely in the inertial reference frame so length contraction should not be a factor.. i think .. still scratching my head...

    P.S. Agree with everything else you said.
     
    Last edited: Sep 26, 2013
  10. Sep 26, 2013 #9
    OK, I have found the problem, thanks to the input from Ibix. All the calculations in the OP are correct as is the alternative more compact version given by Ibix. The bug was in my spreadsheet.

    Now the frequency of the accelerating light clock is not time (or velocity) dependent, but the radar length is generally shorter than the ruler length. This seems to confirm the idea that the photon in the clock is travelling along a curved path in the accelerated frame, so it is not tracking exactly along the y axis. I assume this is why the discrepancy between radar length and ruler length does not show up in Mentz's method.

    Thanks guys for all the input. Problem solved (I think). :smile:

    I have attached the corrected spreadsheet in Open Office format.
     

    Attached Files:

  11. Sep 26, 2013 #10
    Thanks for checking the calculations Ibix. The equations were basically sound and you pointed me to the bug in my spreadsheet. As a point of interest that might be of use to someone, the negative solution of the quadratic gives the time of the preceding event. If the emission event is time t1, the reflection event is time t2 and the return event is t3 then we can obtain t1 and t3 if we know the time of the reflection event from:

    [tex]t_1=\left(L^2g^2/2+1\right)t_2-L\sqrt{\frac{1}{4}L^2g^2+1}\sqrt{g^2t_2^2+1}[/tex]

    and

    [tex]t_3=\left(L^2g^2/2+1\right)t_2+L\sqrt{\frac{1}{4}L^2g^2+1}\sqrt{g^2t_2^2+1}[/tex]
     
  12. Sep 26, 2013 #11

    Oh yes, the distance is there. Good.

    As the equations in the OP are actually OK, I guess, I have used them find out that:

    When the acceleration increases, these kind of light clocks increase their ticking rate, according to an ideal co-accelerating clock.

    Larger light clocks differ from ideal clocks more than smaller ones. (large means distance between mirrors is large)
     
  13. Sep 26, 2013 #12
    Hi jartsa. That does appear to be the case. Just for info, the form of the equations presented by Ibix and as used in his spreadsheet is less prone to computational errors by the software for extremes such as small L.
     
  14. Sep 27, 2013 #13
    I'm really puzzled. As already mentioned, doesn't that break the equivalence principle? But wait, if this is correct then it may be interpreted as a prediction of difference in behaviours of different types of clocks in a gravitational field.
     
  15. Sep 27, 2013 #14

    PeterDonis

    User Avatar
    2016 Award

    Staff: Mentor

    Yes; changing the acceleration corresponds to changing "height" in the field; changing the ticking rate corresponds to changing the gravitational time dilation factor.
     
  16. Sep 27, 2013 #15
    Yes. A long light clock in a strong gravitational field will also tick at a slightly different rate than an ideal clock, because the light will travel in a curved path in the gravity field as well. It was only when the light clock appeared to be varying it frequency with constant acceleration (due to an error in my spreadsheet) that the equivalence principle was being violated. That is fixed now.
     
  17. Sep 29, 2013 #16

    Mentz114

    User Avatar
    Gold Member

    I hope yuiop won't mind me posting this question here because it's related to the accelerating light clock. I'm trying to find the null geodesic that starts at (x0,y0) in the y-direction and intersects y=L at (x1,y0+L) . The metric is ##ds^2=-a^2x^2dt^2+dx^2+dy^2+dz^2##. Starting with the Lagrangian

    ##\mathcal{L} = -a^2x^2 \dot{t}^2 + \dot{x}^2+\dot{y}^2## where the dot means d/dλ, λ being an affine parameter. The Euler-Lagrange equations for x are

    ##\frac{\partial \mathcal{L}}{\partial x}=-2a^2 x\dot{t}^2## and ##\frac{d}{d\lambda}\frac{\partial \mathcal{L}}{\partial \dot{x}}=2\ddot{x}## so ##\ddot{x}=-a^2\dot{t}^2x##.
    Because ##\mathcal{L}## does not depend explicitly on t, y nor z, ##\ddot{t}=\ddot{y}=\ddot{z}=0##.

    Applying the constraint that this is a null geodesic, ##\dot{x}^2+\dot{y}^2=1## we can write ##\dot{t}^2=1/(ax)^2## so that ##\ddot{x}=-1/x##. Integrating this gives ##\dot{x}=\lambda(1/x_0-1/x)##.

    This looks like ##v=at## which is what I'd expect on a time-like trajectory but not a null one.

    At this point I'm stuck. How did I go wrong ?
     
  18. Sep 30, 2013 #17
    You're welcome :approve: I would be interested in the answer too and I think it can only enhance this thread.
     
  19. Sep 30, 2013 #18

    pervect

    User Avatar
    Staff Emeritus
    Science Advisor

    I only skimmed the work, but my first thought is that you assumed that light travels in a straight line. This is only true in inertial coordinates.

    What I think you need to compute would be called in optics the "optical path length", to do this I would suggest first to compute the curve that the light actually follows (which will be a null geodesic).

    You can get this from the metric, but the path will be a null path, so it won't have a direct length you can compute via the Lorentz interval.

    Wiki says http://en.wikipedia.org/wiki/Optical_path_length

    You can get the "index of refraction" from the metric for an accelerated obserer. Unlike any normal optical material, the effective index of refraction is going to be greater than 1.

    I haven't carried through this calculation, or even thought of it much, so I might be missing something or even making a conceptual error. This is my current thinking though.

    Intuitively, light will follow an approximately parabolic path. You'll have to angle the beam upwards. As the floor of the spacecraft accelerates, the light will first gain altitude, reach some maximum altitude, then loose altitude.

    Wiki's definition seems to be coordinate dependent, which bothers me a bit. I haven't had any luck finding further defitions of optical path length. But using the wiki defintion, you'd take the 3-space length of the parabolic path (ignoring the time part of the metric) then adjust it for the time dilation.

    [add]
    The basic idea is to find the round-trip time for the light beam as measured by a clock present at the start and end of the round trip. There may be other approaches, this wiki-inspired one seems the easiest.
     
    Last edited: Sep 30, 2013
  20. Sep 30, 2013 #19

    Mentz114

    User Avatar
    Gold Member

    Taking the light beam in the accelerating elevator scenario I assumed is that the light will fall in a curve. I have not made any explicit assumptions by defining ##\dot{t}, \dot{x}## and ##\dot{y}##. These can be any functions of the affine parameter.

    I stated that my aim was to find a null geodesic.

    I am using the metric to get the Lagrangian. Is there another way ?

    Thanks, I'll check it out.

    [edit]
    I think I have a solution. In the local coords on the lift the light appears to travel straight, so the geodesic has no ##\partial_x## component. But when we use the tetrad that converts between the two frames on this geodesic, a ##\partial_x## component appears. This shows that the light will appear to follow a curved path in the other (non-inertial) coords.

    I'm still working out the details.
     
    Last edited: Sep 30, 2013
  21. Sep 30, 2013 #20

    Mentz114

    User Avatar
    Gold Member

    Carrying on from my previous post. The frame basis of the geodesic ##u^\mu=f_0## is

    ##f_0=\frac{\cosh\left( a\,t\right) }{a\,x}\partial_t-\sinh\left( a\,t\right) \partial_x,\ f_1= -\frac{\sinh\left( a\,t\right) }{a\,x}\partial_t+\cosh\left( a\,t\right) \partial_x,\ f_2=\partial_y,\ f_3=\partial_z##

    from which we get the tetrad ##\left(f_a\right)^\mu## which transforms from the local frame basis to the coordinate basis, i.e. ##\left(f_a\right)^\mu\left(f_b\right)^\nu\eta^{ab}=g^{\mu\nu}##.

    In the local frame the light clock is set up by shining the light across the elevator along the y-axis, and the local null geodesic is just ##u^a=\partial_\hat{t}+\partial_\hat{y}##. Transforming ##u^a## gives

    ##u^\mu = \left(f_a\right)^\mu u^a=\frac{\cosh\left( a\,t\right) }{a\,x}\partial_t-\sinh\left( a\,t\right) \partial_x+\partial_y##. The norm is still zero, ##g_{\mu\nu}u^\mu u^\nu = 0##.

    The three components of ##u^\mu## are 'affine' velocities, ie ##dx^\mu/d\lambda## and the final step is to convert them to coordinate velocites by dividing by ##dt/d\lambda=\frac{\cosh\left( a\,t\right) }{a\,x}##

    This gives ##\frac{dx}{dt}=-a\,x\,\tanh\left( a\,t\right) ## and ##\frac{dy}{dt}=\frac{a\,x}{\cosh\left( a\,t\right) }##

    This looks plausible. At ##t=0,\ x=x_0## the velocity is ##ax_0## in the y-direction and zero in the x-direction. (##ax## is the coordinate speed of light). Also ##\left(\frac{dx}{dt}\right)^2+\left(\frac{dy}{dt}\right)^2=a^2x^2##, again this is what we require.

    The worldline ##u^\mu## satisfies the geodesic equations

    ##\frac{d^2t}{d\lambda^2}+{\Gamma^t}_{\mu\nu}u^\mu u^\nu=0## and ##\frac{d^2y}{d\lambda^2}=0## but so far (I could be making a mistake) not the ##x## equation.

    I have to say, I'm not content with some aspects of this. But I can't find any other approach to what seems a pretty simple problem.

    (I've noticed that I've written ##\sinh(at)## etc when it should be ##\sinh(a\tau)## or ##k\sinh(a\lambda)##. I don't think it matters, because the final step of dividing the spatial velocities by ##\dot{t}## cancels the affine factors. )
     
    Last edited: Sep 30, 2013
Know someone interested in this topic? Share this thread via Reddit, Google+, Twitter, or Facebook




Similar Discussions: Accelerating Light Clock
  1. Light Clock (Replies: 7)

  2. Light Clocks (Replies: 2)

  3. Light Clock (Replies: 8)

  4. Clock acceleration (Replies: 1)

Loading...