Different Clock Rates Throughout Accelerating Spaceship

[1977ub]

I have been reading a lot of relativity-related material and clearing up a few gaps in my general knowledge. I read something that struck me as off. Perhaps I am missing something.

Usenet Physics FAQ -> The Relativistic Rocket
http://math.ucr.edu/home/baez/physics/Relativity/SR/rocket.html

In the set-up: "If a rocket accelerates at 1g (9.81 m/s2) the crew will experience the equivalent of a gravitational field with the same strength as that on Earth."

Presumably this means the entire crew will experience the same acceleration - at the leading and trailing ends of the ship, for instance.

Later, we are told that: "inside the rocket, a clock attached to the rocket's ceiling (i.e. furthest from the motor) ages faster than a clock attached to its floor."

Then in the next paragraph: "it tells us something fundamental about gravity, via Einstein's Equivalence Principle. Einstein postulated that any experiment done in a real gravitational field, provided that experiment has a fairly small spatial extent and doesn't take very long, will give a result indistinguishable from the same experiment done in an accelerating rocket. So the idea that the rocket's ceiling ages faster than its floor (and that includes the ageing of any bugs sitting on these) transfers to gravity: the ceiling of the room in which you now sit is ageing faster than its floor; and your head is ageing faster than your feet. ... This difference in ageings on Earth has been verified experimentally. In fact, it was absolutely necessary to take into account when the GPS satellite system was assembled."

Now, I had been under the impression that differences in clock speeds at different altitudes were due to the gravitational field being weaker at higher altitudes.

I understand that once we start expanding the width or height of our accelerating laboratory, we can make measurements to tell whether we are in acceleration vs gravitational field.

Does the clock at the "top" of this accelerating frame indeed tick faster than one at the floor?

Is the reason for this indeed analogous to clocks ticking *faster* at higher altitudes above the Earth's surface?

Is the reason for gravitational time dilation closer to a massive body related or unrelated to the *greater* strength of the gravitational field there?

Does a local measurement of acceleration/g-forces at the top of the accelerating frame differ from a measurement at the bottom?

I would not have thought so. Even if it is true, I would have taken the gravitational difference in clock speeds near Earth to be something that could NOT be noticed or simulated for an observer in an accelerating box, such as by measuring clock speed at the leading vs trailing end.

Thank you.

 

[mfb]

In the set-up: "If a rocket accelerates at 1g (9.81 m/s2) the crew will experience the equivalent of a gravitational field with the same strength as that on Earth."

Presumably this means the entire crew will experience the same acceleration - at the leading and trailing ends of the ship, for instance.

This is a very good approximation, but it is not exact (unless the ship can change its length).

Now, I had been under the impression that differences in clock speeds at different altitudes were due to the gravitational field being weaker at higher altitudes.

No, it is the potential difference, not the local gravitational attraction.

Does the clock at the "top" of this accelerating frame indeed tick faster than one at the floor?

As seen by the spaceship, or as seen from earth? And with a flexible spaceship or not?

I think the other questions are answered or depend on my own questions about the setup.

 

[1977ub]

First - thank you.

Let's take a modern rocket with conventional materials. I imagine it will "settle" slightly but not undergo any further deformation - similar to if sitting on the surface of the earth.

Engine set so that a person sitting at the bottom experiences 1g.

1) Do people at the top experience 1g force, same as those at the bottom do?

2) Do all crew agree that clocks at the top are moving more quickly than those at the bottom?

 

[PAllen]

First - thank you.

Let's take a modern rocket with conventional materials. I imagine it will "settle" slightly but not undergo any further deformation - similar to if sitting on the surface of the earth.

Engine set so that a person sitting at the bottom experiences 1g.

1) Do people at the top experience 1g force, same as those at the bottom do?

2) Do all crew agree that clocks at the top are moving more quickly than those at the bottom?

1) The top will feel very slightly less acceleration than the bottom, under reasonable rigidity assumption. This, however, is not the main reason:

2) All crew will will agree top clocks go faster (by a very small amount). This would be true even if you arranged (by slowly stretching the rocket per rocket crew) for the top and the bottom to experience identical g force.

 

[pervect]

First - thank you.

Let's take a modern rocket with conventional materials. I imagine it will "settle" slightly but not undergo any further deformation - similar to if sitting on the surface of the earth.

Engine set so that a person sitting at the bottom experiences 1g.

1) Do people at the top experience 1g force, same as those at the bottom do?

No. But as mentioned before, for short rockets it's a good approximation.

2) Do all crew agree that clocks at the top are moving more quickly than those at the bottom?

Some care is needed to specify how you measure the relative motion between the top and the bottom.

For instance, the round-trip signal time of a light beam between the top and the bottom will be constant.

The rocket doesn't have a "true" frame, but it's got something that comes close to it. In this almost-frame, there is no relative motion between the top and the bottom of the rocket. Which is necessary if the rocket is to have a constant length in the "almost-frame".

 

[1977ub]

If you read an explanation of GR predictions and results, you will see one of the central ones is that the clock further from massive body will run more quickly. This prediction is not made by SR. The "rocket" example goes out of its way to focus on results which can be seen with SR+acceleration without GR. What surprised me in the page I referenced is this section: "the idea that the rocket's ceiling ages faster than its floor (and that includes the ageing of any bugs sitting on these) transfers to gravity: the ceiling of the room in which you now sit is ageing faster than its floor; and your head is ageing faster than your feet.:"

"transfers to gravity" ?

Presumably the effects have different magnitude and occur for different reasons.

The calculation of the slower clock at the top of my room uses the distance from that ceiling to the center of the Earth vs the distance from the floor to the center of the Earth in order to compare the gravitational potentials, correct? And for the accelerating rocket, there is no 3rd point "focus" analogous to the center of the Earth, so the effect and its calculation are going to be very different. Aren't these phenomena so different that we wouldn't think of the one as "transferring" to the other?

 

[PAllen]

Some care is needed to specify how you measure the relative motion between the top and the bottom.

I assumed question two's ambiguous wording 'clocks moving more quickly' referred to the rate of the clocks, not their state of motion. Normally, this is what is of interest about a clock.

 

[PAllen]

Presumably the effects have different magnitude and occur for different reasons.

The calculation of the slower clock at the top of my room uses the distance from that ceiling to the center of the Earth vs the distance from the floor to the center of the Earth in order to compare the gravitational potentials, correct? And for the accelerating rocket, there is no 3rd point "focus" analogous to the center of the Earth, so the effect and its calculation are going to be very different. Aren't these phenomena so different that we wouldn't think of the one as "transferring" to the other?

Actually, the magnitude is the same for comparable 'every day' magnitudes. Further, if you take compute the time dilation difference between two nearby radial values, for radii much larger than the Schwarzschild radius, and only keep leading Taylor expansion terms, you get that the difference is just proportional to g * (r2-r1).

 

[1977ub]

Ok. Well that's something for me to chew on. The difference in the tick-rates of two clocks, one at sea level vs one raised by a mile - this is not too far off from the difference in the tick-rates of two clocks, one at the base and one at the nose of a mile-high rocket accelerating in space with roughly 1g.

 

[Fredrik]

Presumably the effects have different magnitude and occur for different reasons.

The reasons are the same.

The accelerating rocket in SR: The world line of the top of the rocket is more like a geodesic than the world line of the bottom of the rocket.

A house standing firmly on the ground in GR: The world line of the ceiling is more like a geodesic than the world line of the floor.

 

[1977ub]

I guess I'm still stuck thinking of:
1) gravitational force (Newtonian) decreasing as the square of the distance from the body's center, and

2) a clock's rate slows as the gravitational force/acceleration that it experiences increases.

Let's take an example where instead of the Earth we have a much more massive and smaller body, such that our rocket is sitting on the surface, 1 mile from the center of the body, and at the bottom of the sitting rocket, gravity is experienced as 1g. Presumably at the top of the rocket, we are twice as far from the center of the massive body as the rocket bottom is, and the top clock is much faster relative to the bottom as we would have on earth. The acceleration due to gravity - and thus the extent of decrease in time dilation - is much smaller up there than it would be a mile off the Earth's surface.

 

[PAllen]

2) a clock's rate slows as the gravitational force/acceleration that it experiences increases.

This is your key misunderstanding. In a static field in GR that can be approximated by a Newtonian potential, clock rate differences for static clocks is a function of potential difference not acceleration. Thus, GR says, in the limit if a uniform field, clock difference rate is proportional to g*h, where h is the separation between them; thus proportional to the potential difference. I explained earlier how you can show, for large r, and small difference in r, the clock rate difference is also a function of potential difference: g(r1-r2).

 

[1977ub]

That seems to be splitting hairs a bit for what I'm trying to find out...

Ok perhaps you could take a look at this?

3 cases - do these 1g-experiencing clocks - tick at the same rate?

a) clock on surface of Earth experiencing 1g.
(neglect rotation/orbit of the earth)

b) clock in space in our solar system,
far enough from the Sun to experience 1g,
held in place by rocket engine,
(neglecting presence of other planets)

c) clock in space inside rotating ring,
such that clock experiences 1g from 'centrifugal' force.

 

[mfb]

In general, all those will tick at different rates.
As mentioned before, gravitational acceleration itself is not relevant, gravitational potential is.

 

[PAllen]

That seems to be splitting hairs a bit for what I'm trying to find out...

Ok perhaps you could take a look at this?

3 cases - do these 1g-experiencing clocks - tick at the same rate?

a) clock on surface of Earth experiencing 1g.
(neglect rotation/orbit of the earth)

b) clock in space in our solar system,
far enough from the Sun to experience 1g,
held in place by rocket engine,
(neglecting presence of other planets)

c) clock in space inside rotating ring,
such that clock experiences 1g from 'centrifugal' force.

A couple of issues here:

It is a misconception to imagine an objective tick rate for clock compared to some 'standard'. Instead, you should think only in terms of comparing tick rates on two clocks that exchange signals. As you know from SR, you can have the situation where each finds the other one slower.

If the three clocks you describe compare rates, as mfb noted, they would all be different from each other, and the relation would be rather complex.

What is simple is comparing two clocks at rest relative to a static field (that is, each finds their proper acceleration is constant over time), and they are in the same static field (e.g. rocket; near earth; etc.). Then the difference in rate between those clocks will proportional to the potential difference between them.

 

[DrGreg]

In general, all those will tick at different rates.
As mentioned before, gravitational acceleration itself is not relevant, gravitational potential is.

1977ub,

Another way of putting this is that if you want to calculate the difference in rates between two clocks, it's not enough to know the gravitational acceleration at the locations of the two clocks, you need to know it at every point in between as well.

(Under the assumption of a static spacetime.)

 

[1977ub]

PAllen,

My attempt was to describe 3 situations where the clocks were not moving relative to one another. (#c obviously wobbles). Observers near the clocks could compare notes to see if they are ticking at the same rate.

DrGreg,

Ahh. interesting. Very often GR examples are compared to a default situation of being out away in empty space. Thus, here http://en.wikipedia.org/wiki/Gravitational_time_dilation we read that "a clock on the surface of the Earth (assuming it does not rotate) will accumulate around 0.0219 seconds less than a distant observer over a period of one year. In comparison, a clock on the surface of the sun will accumulate around 66.4 seconds less in a year."

My question related to the 3 cases would treat each in isolation from other factors and compare to "a distant observer."

I understand that these cases are different... for some reason my mind is still balking... i guess getting further into GR math at some point might cure me... ok - let's take case a vs b, are there any back-of-envelope calculations that could figure out which clock ticks slower wrt "a distant observer" ?

Thanks.

 

[Fredrik]

Observers near the clocks could compare notes to see if they are ticking at the same rate.

Each observer could compare one of those clocks to his own clock, but what would be the point of that? The results will also depend on how those observers are moving.

 

[1977ub]

The ambiguities of SR comparisons of tick-rates do not come up since all 3 observers find they are not moving relative to one another, or to a 4th "distant observer" for that matter.

 

[Fredrik]

The ambiguities of SR comparisons of tick-rates do not come up since all 3 observers find they are not moving relative to one another, or to a 4th "distant observer" for that matter.

I still don't see a meaningful way to interpret the results. Consider a GR spacetime that contains two spherical distributions of mass that are far enough from each other that the spacetime is approximately a Schwarzschild spacetime* in the vicinity of each of them. (This is just to make sense of your (a) and (b)). Where is the distant observer located? Do you want to put him at a distance from both objects that's far greater than the distance between the objects? In that case, the signal from a clock near one of the spherical objects will first have to travel through a region of spacetime that's a lot like the Schwarzschild spacetime associated with that object, but as it moves closer to the distant observer, the properties of the spacetime around it keep changing. It sounds very difficult to do calculations.

And even if you could do a calculation (of e.g. the interval between arrivals of signals sent 1 s apart from the clock near one of the spherical objects), how would you interpret the result? It seems that you want to know something about a specific point in spacetime, but the result will depend on the properties of spacetime along the entire path the signal takes to get to the distant observer.

*) A Schwarzschild spacetime describes a universe that's completely empty except for one spherically symmetric non-rotating distribution of mass.

 

[Fredrik]

By the way, I think it's a bad idea to think of what's going on in these scenarios as clocks having different ticking rates in different situations. The way I see it, clocks always tick at the same rate. The numbers they display tell you nothing about the clock, and something about the path through spacetime that the clock has taken.

 

[1977ub]

Frederik,

It sounds like you have a big problem with phrases such as those that are used in the wiki page. If you were an editor there, would you remove them? Is there no value to these types of comparisons? Is yours a common belief?

 

[Nugatory]

Frederik,

It sounds like you have a big problem with phrases such as those that are used in the wiki page. If you were an editor there, would you remove them? Is there no value to these types of comparisons? Is yours a common belief?

Fredrik is accurately describing the math and the science.

The page is not outright wrong, but it is consistently sloppy about remembering that when we say that a clock is "running slower" there's an implied something else that we're comparing against.
(If you haven't looked at the talk section of that wiki page, you will find it interesting)

 

[pervect]

By the way, I think it's a bad idea to think of what's going on in these scenarios as clocks having different ticking rates in different situations. The way I see it, clocks always tick at the same rate. The numbers they display tell you nothing about the clock, and something about the path through spacetime that the clock has taken.

I agree with this view - unfortunately there are plenty of sources that talk about clocks ticking at different rates. It's not really a huge problem which view you use UNLESS the person is imagining some sort of "universal clock" relative to which the rate of ticking of all others can be measured. In which case it's a huge problem.

Unfortunately, I have a strong suspicion that many, if not most, lay readers implicitly assume the existence of such a "universal clock" in spite of perhpas having a few lectures about "the relativity of simultaneity" float by over their heads. I hope I'm just being pessimistic...

 

[1977ub]

Presumably, as one gets out away from the Sun (or the Earth, or a black hole, whatever) the further away into relatively empty space, there is a limit which is approached for the ratio between the high gravity clockspeed and nearly zero gravity clockspeed. the multiplier is 1 right next to the clock near the body, and asymptotically approaches some exact figure the further we get away. This is what I presume is being discussed on the wiki page, i.e 66.4 sec / year does not apply exactly at any distance from the ideal isolated sun but is approached asymptotically as we head away.

 

[Nugatory]

I agree with this view - unfortunately there are plenty of sources that talk about clocks ticking at different rates. It's not really a huge problem which view you use UNLESS the person is imagining some sort of "universal clock" relative to which the rate of ticking of all others can be measured. In which case it's a huge problem.

Unfortunately, I have a strong suspicion that many, if not most, lay readers implicitly assume the existence of such a "universal clock" in spite of perhpas having a few lectures about "the relativity of simultaneity" float by over their heads. I hope I'm just being pessimistic...

Nope, not pessimistic. That assumption is so intuitive, so consistent with the experience of an entire life lived in non-relativistic conditions, that many people don't even realize that they're making that assumption.

It doesn't help any that it's much easier to say "ticking at different rates" than something rigorous involving simultaneity conventions and the ratio of proper time at the clock to proper time at the observer. Thus, even those who really do understand tend to speak in ways that do not explicitly reject the assumption of universal simultaneity; and as you say, no great harm is done as long as the listener understands as well.

 

[stevendaryl]

1) The top will feel very slightly less acceleration than the bottom, under reasonable rigidity assumption. This, however, is not the main reason:

2) All crew will will agree top clocks go faster (by a very small amount). This would be true even if you arranged (by slowly stretching the rocket per rocket crew) for the top and the bottom to experience identical g force.

There was a thread about this topic a year or so ago. There are two effects going on in the accelerated rocket that conspire to make the rear clock show an earlier time than the front clock:

1. Because of the relativity of simultaneity, a comoving inertial frame will find the front clock ahead of the rear clock, even if they show the same time in the "launch frame".
2. Because of length contraction of the rocket itself, the front clock is traveling at a slightly slower speed than the rear clock. So the time dilation factor effects the rear clock more.

The first effect is visible in the comoving frame. It is present even if you make the front and the rear experience equal accelerations.

The second effect is visible in the "launch" frame. If you "stretch" the rocket so that the front and the rear experience the same acceleration, then this effect disappears.

If you have a Born-rigid rocket (meaning that its length is always the same, when measured in the comoving inertial frame), then it's actually interesting: Effect number 1 is most important right after launch, but if you wait a really long time, then effect number 2 comes to dominate.

 

[1977ub]

Quote of stevendaryl :
"Because of length contraction of the rocket itself, the front clock is traveling at a slightly slower speed than the rear clock. So the time dilation factor effects the rear clock more."

The "length contraction" only applies for observers in the rest frame, correct?

I am primarily interested in the experiences of 2 observers on board - head vs tail of ship - how much acceleration they experience, and if they find their clocks to tick differently as they compare notes. (There is no simultaneity problem since they find each other to be relatively nonmoving.)

 

[stevendaryl]

Quote of stevendaryl :
"Because of length contraction of the rocket itself, the front clock is traveling at a slightly slower speed than the rear clock. So the time dilation factor effects the rear clock more."

The "length contraction" only applies for observers in the rest frame, correct?

I am primarily interested in the experiences of 2 observers on board - head vs tail of ship - how much acceleration they experience, and if they find their clocks to tick differently as they compare notes. (There is no simultaneity problem since they find each other to be relatively nonmoving.)

If the rocket ship is "rigid", meaning that its length doesn't change with time as measured by crew members, then the acceleration felt by someone at the front of the rocket will be less than the acceleration felt by someone at the rear of the rocket. Also, the time on the front clock will advance more quickly than the time on the rear clock. This is an operationally defined difference. Take a third clock to the rear, and synchronize the third clock to show the same time as the rear clock. Then move the clock up to the front of the rocket. Let it sit there for a year, or whatever. Then carry it back to the rear clock. The movable clock will be ahead of the rear clock.

 

[1977ub]

Stevendaryl,

Yes. Still struggling with parts of this. What if the nose is fully detached - forward and aft sections each having their own engines - and the base and nose synchronize in the initial rest frame such that they begin accelerating simultaneously? Would there then be any reason that they will later find that the clock in the nose module is ticking more slowly than the one at the base?

 

[jartsa]

Nope, not pessimistic. That assumption is so intuitive, so consistent with the experience of an entire life lived in non-relativistic conditions, that many people don't even realize that they're making that assumption.

It doesn't help any that it's much easier to say "ticking at different rates" than something rigorous involving simultaneity conventions and the ratio of proper time at the clock to proper time at the observer. Thus, even those who really do understand tend to speak in ways that do not explicitly reject the assumption of universal simultaneity; and as you say, no great harm is done as long as the listener understands as well.

Why is it that "lower clock is faster than upper clock" is more incorrect than "lower clock is slower than upper clock"?

I think it's because lower clock really is slower than upper clock.

 

[stevendaryl]

Stevendaryl,

Yes. Still struggling with parts of this. What if the nose is fully detached, and the base and nose synchronize in the initial rest frame such that they begin accelerating simultaneously? Would there then be any reason to reason that they will later find that the clock in the nose module is ticking more slowly than the one at the base?

If the front and the rear follow identical accelerations, then the two clocks will show the same time, as viewed from the "launch" frame, but the front clock will be ahead, according to crew members.

 

[1977ub]

Perhaps you can explain the flaw here:

I'll use Epstein's 3-rockets-in-a-row model.

* At regular intervals *, the central rocket sends a ping to front and back rockets.

Front and back rockets fire their boosters briefly when they get the ping. Also, clock ticks once.

Middle rocket delays appropriately after releasing the ping before boosting in order to stay midway between the other rockets.

We'll call them A, B, and C.
B releases first ping,
A, B, and C all boost together, as seen by them and the reference frame.
Now all are moving wrt the rest frame.
From rest frame perspective, 2nd ping hits A first, then B boosts, then ping hits C, which then boosts.
So with each ping, since rocket is moving faster wrt rest frame, A is boosting sooner and sooner wrt C. It appears to be accelerating faster than C.
Also with each ping, rest frame measures increasing length contraction between A & C.
This is basically the scenario I presented above, whereby nose/tail of rocket begin accelerating simultaneously.
It would appear from this reasoning that the clocks remain synchronized and therefore running at same rate as seen on the rockets,
while the rest observer is the one who observes the front and back clocks to run at different rates.

 

[stevendaryl]

Perhaps you can explain the flaw here:

I'll use Epstein's 3-rockets-in-a-row model.

The central rocket sends a ping to front and back rockets.

Front and back rockets fire their boosters briefly when they get the ping. Also, clock ticks once.

Middle rocket delays appropriately after releasing the ping before boosting in order to stay midway between the other rockets.

We'll call them A, B, and C.
B releases first ping,
A, B, and C all boost together, as seen by them and the reference frame.
Now all are moving wrt the rest frame.
From rest frame perspective, 2nd ping hits A first, then B boosts, then ping hits C, which then boosts.
So with each ping, since rocket is moving faster wrt rest frame, A is boosting sooner and sooner wrt C. It appears to be accelerating faster than C.
Also with each ping, rest frame measures increasing length contraction between A & C.
This is basically the scenario I presented above, whereby nose/tail of rocket begin accelerating simultaneously.
It would appear from this reasoning that the clocks remain synchronized and therefore running at same rate as seen on the rockets,
while the rest observer is the one who observes the front and back clocks to run at different rates.

Are you saying that A and C don't have their own clocks, but instead rely on counting the signals from B to know what the time is? That is, you want it to be the case that aboard the spaceship, time at C = number of "pings" received by C, and similarly for A?

In that case, aboard the spaceship they are using a coordinate time that is different from the time shown on a normal clock. Well, the two are the same for B, but for A, "clock time" is slower than "coordinate time", and for C, "clock time" is faster than "coordinate time".

If I understand correctly, then yes, as viewed by those aboard the rocket, everyone is using the same "coordinate time". But as viewed by those in the "launch" frame, the coordinate time for the front is ahead of coordinate time for the rear.

 

[1977ub]

As far as B is concerned, a ping is released once per second let's say. You don't reason that A & C will perceive it that way, I take it. Ok let's scale this back to a single ping/boost. While in rest frame, all agree that distances between ships will take light 1 second to reach from B to A or C, let's say. After the first brief round of boosting, Will the ships no longer find their own clocks to be synchronized? Will they no longer find their ships to be the same distance from one another as they did in the rest frame?

 

[Nugatory]

I think it's because lower clock really is slower than upper clock.

Try writing down a rigorous definition of "really is slower", one that I could use to construct an experiment that will allow all observers to agree about which one is "really slower". It can be done, but it's harder than it sounds, and when you succeed you'll have a better sense of why the question posed in #13 of this thread isn't all that well-formed.

 

[1977ub]

Another related question:

So two ships are side by side.

They accelerate identically for a period of time, then decelerate identically for a period of time, finally coming to a stop.

Since they are side by side, they both agree that their clocks are perfectly synchronized the whole time.

However, If instead of being side by side, one of the ships is spacially separated from the other *along the axis of travel*, we can no longer say this?

Instead we must say that during the acceleration, the ship at the rear will determine that the ship at the front has a faster ticking clock, and during the deceleration phase, presumably, the other way around, since all will be agree that clocks are synchronized after both have stopped.

If this is true, and I have missed it, is there a clear description somewhere?

 

[stevendaryl]

As far as B is concerned, a ping is released once per second let's say. You don't reason that A & C will perceive it that way, I take it.

No, as measured by A's clock (assuming it's a normal windup clock, or else an electronic clock), the pings come more often than once per second, and as measured by C's clock, they come less often than once per second.

Ok let's scale this back to a single ping/boost. While in rest frame, all agree that distances between ships will take light 1 second to reach from B to A or C, let's say. After the first brief round of boosting, Will the ships no longer find their own clocks to be synchronized? Will they no longer find their ships to be the same distance from one another as they did in the rest frame?

Okay, let's suppose that initially A, B, and C are all at rest. Then at t=0 (according to the "launch" frame, they all accelerate suddenly, to get to a new speed of v relative to the launch frame. Call the launch frame F, and the new frame F'.

Assume that there is some distance L between A and B and between B and C. So let e_1 = the event at which A suddenly changes velocity, e_2 = the event at which B suddenly changes velocity, e_3 = the event at which C suddenly changes velocity. The coordinates of these events in frame F are:

t_1 = 0, x_1 = -L

t_2 = 0, x_2 = 0

t_3 = 0, x_3 = +L

The coordinates of these events in frame F' are:

t_1' = \gamma (t_1 - \dfrac{v}{c^2} x_1) = \gamma \dfrac{vL}{c^2}
x_1' = \gamma (x_1 - v t_1) = -\gamma L
t_2' = \gamma (t_2 - \dfrac{v}{c^2} x_2) = 0
x_1' = \gamma (x_2 - v t_2) = 0
t_3' = \gamma (t_3 - \dfrac{v}{c^2} x_3) = - \gamma \dfrac{vL}{c^2}
x_3' = \gamma (x_3 - v t_3) = +\gamma L

So from the point of view of the crew, immediately after the acceleration, it appears that: C accelerated first, then B, and finally A. So from their point of view, the distance between C and B increased, and the distance between B and A increased. So they conclude that if they want to keep the distance between the rockets constant in future jumps, they will have to tell C to accelerate a little softer or a little later than B, and A should accelerate a little harder or a little earlier than B.

 

[stevendaryl]

Another related question:

So two ships are side by side.

They accelerate identically for a period of time, then decelerate identically for a period of time, finally coming to a stop.

Since they are side by side, they both agree that their clocks are perfectly synchronized the whole time.

However, If instead of being side by side, one of the ships is spacially separated from the other *along the axis of travel*, we can no longer say this?

Instead we must say that during the acceleration, the ship at the rear will determine that the ship at the front has a faster ticking clock, and during the deceleration phase, presumably, the other way around, since all will be agree that clocks are synchronized after both have stopped.

You're talking about the case where the two rockets accelerate and decelerate identically, as measured in their initial rest frame? In that case, from the point of view of the "launch" frame, the clocks will remain synchronized at all times. From the point of view of those aboard the rockets, the front clock will get ahead of the rear one during acceleration, and then the rear rocket will catch up during deceleration.

I'm not sure what's a good reference book for this stuff. If you google "rocket, acceleration, relativity", you get plenty of hits, but I'm not sure what articles are the most definitive.

 

[Nugatory]

However, If instead of being side by side, one of the ships is spacially separated from the other *along the axis of travel*, we can no longer say this?
...

If this is true, and I have missed it, is there a clear description somewhere?

Look for "Bell's spaceship paradox". It's described in terms of length contraction instead of time dilation, but it's still a pretty good starting point for understanding just how tricky "synchronized" acceleration can be.

 

[1977ub]

Nugatory,

Yes, I have read about Bell's Spaceship Paradox. I actually found it a bit surprising that people didn't get it at first. Acceleration leads to velocity leads to length contraction measured in the rest frame. If on the other hand you try to coordinate acceleration such that in the rest frame the two ships are seen as being at a constant distance, you are stretching the line! The whole issue I'm dealing with here I am somehow not prepared for, however. I understand that length contraction is closely related to relativity-of-simultaneity, and that as a moving rod gets shorter in the RF, the clocks at either end of the rod get out of synch in RF with the tail clock reading later than the front clock, and this can be seen the in resolution to the ladder paradox. I understand that clocks in the moving ship that seem out of synch in the reference frame seem perfectly in synch on board the ship and vice versa.

I guess i'd like to use something like the trapped-photon clocks that are used to illustrate the non-accelerating phenomena of SR.

You can continue to look at them from the resting frame, but do they actually show you how a clock ticks in an accelerating ship?

After all, on the ship, the photon's path now curves. There no longer would appear to be any "regular" tick that one can find on board the accelerating frame to compare with one's own frame, right?

You have to use the equivalence principle to cut up the acceleration into individual SR slices?

 

[1977ub]

stevendaryl,

"So they conclude that if they want to keep the distance between the rockets constant in future jumps, they will have to tell C to accelerate a little softer or a little later than B, and A should accelerate a little harder or a little earlier than B."

I'm defining everything as automatic. There are 3 ships with observers. A & C are set to fire the booster when they get a ping. B is set to send a ping and then wait the set time which light takes to get from B to A in the frame, and then fire booster. B is to ping once per second. Start program. Now, you agree with me that from the rest frame, the distance between A to C contracts as the whole parade accelerates. Are you telling me that from the POV of observers on the ships, that the AC distance *increases* as the ships accelerate?

 

[pervect]

Another related question:

So two ships are side by side.

They accelerate identically for a period of time, then decelerate identically for a period of time, finally coming to a stop.

Since they are side by side, they both agree that their clocks are perfectly synchronized the whole time.

However, If instead of being side by side, one of the ships is spacially separated from the other *along the axis of travel*, we can no longer say this?

That sounds right as there isn't any way to define "at the same time" for spatially separated clocks.

Did you ever read about the relativity of simultaneity? Einstein's original explanation can be found at http://www.bartleby.com/173/9.html, there are many others out there.

This is a key issue in understanding relativity, and it doesn't involve acceleration at all.


Instead we must say that during the acceleration, the ship at the rear will determine that the ship at the front has a faster ticking clock, and during the deceleration phase, presumably, the other way around, since all will be agree that clocks are synchronized after both have stopped.

If this is true, and I have missed it, is there a clear description somewhere?[/QUOTE]

 

[jartsa]

Another related question:

So two ships are side by side.

They accelerate identically for a period of time, then decelerate identically for a period of time, finally coming to a stop.

Since they are side by side, they both agree that their clocks are perfectly synchronized the whole time.

However, If instead of being side by side, one of the ships is spacially separated from the other *along the axis of travel*, we can no longer say this?

Instead we must say that during the acceleration, the ship at the rear will determine that the ship at the front has a faster ticking clock, and during the deceleration phase, presumably, the other way around, since all will be agree that clocks are synchronized after both have stopped.

If this is true, and I have missed it, is there a clear description somewhere?

Let's look at this from the launch frame.

When the ships are accelerating, the two clocks are ticking at the same rate. The amount of light, that is on trip, trying to catch the fleeing front ship, is increasing. This explains why rear clock seems slow as seen from the front.

When the ships are decelerating, the two clocks are ticking at the same rate. The amount of light, that is on trip, trying to catch the fleeing front ship, is decreasing. This explains why rear clock seems fast as seen from the front.

 

[stevendaryl]

I'm defining everything as automatic. There are 3 ships with observers. A & C are set to fire the booster when they get a ping. B is set to send a ping and then wait the set time which light takes to get from B to A in the frame, and then fire booster. B is to ping once per second. Start program. Now, you agree with me that from the rest frame, the distance between A to C contracts as the whole parade accelerates. Are you telling me that from the POV of observers on the ships, that the AC distance *increases* as the ships accelerate?

It depends on the acceleration profiles of A&C. You're making the acceleration discrete, so that every time there is a "ping", A&C suddenly change velocity to a new velocity. If they follow identical acceleration profiles, then the distance between A&C will gradually increase, as viewed by the people on board the rockets.

If instead, you try to keep the distance between A&C constant, as viewed by the people aboard the rockets, then you have to accelerate A (the rear rocket) slightly more than C (the front rocket).

 

[1977ub]

How's this.
RF (rest frame) : events further along x are simultaneous.

observer moving along x axis: events further along x that RF views as simultaneous seem to be later as a linear function of x distance, so that clocks RF views to be moving at same rate are still seen as moving at the same rate, but set later.

observer accelerating along X: events further along x that RF views as simultaneous seem to be *increasingly* later, such that clocks that RF sees as both synchronized and ticking at the same rate appear to be ticking faster the further up x axis.

 

[1977ub]

pervect,

[ That sounds right as there isn't any way to define "at the same time" for spatially separated clocks. ]

Yes, good point. I was thinking of programmed maneuvers which are intended to be simultaneous and are deemed so in the rest frame. I definitely understand the relativity of simultaneity. I've become very accustomed to remembering that on our moving frame, things that seem simultaneous are not seen as so on the rest frame and vice versa. This very habit had made it harder for me to think of things getting out of synch on the accelerating ship, for observers on the ship. But of course, this is the difference between moving and accelerating. In the boosting example, during periods of "coasting" people along the ship will find their clocks to tick at the same rate. However during periods of "boosting" the clock up ahead will appear to all aboard to be ticking faster.

 

[pervect]

pervect,

Yes, good point. I was thinking of programmed maneuvers which are intended to be simultaneous and are deemed so in the rest frame. I definitely understand the relativity of simultaneity. I've become very accustomed to remembering that on our moving frame, things that seem simultaneous are not seen as so on the rest frame and vice versa. This very habit had made it harder for me to think of things getting out of synch on the accelerating ship, for observers on the ship. But of course, this is the difference between moving and accelerating. In the boosting example, during periods of "coasting" people along the ship will find their clocks to tick at the same rate. However during periods of "boosting" the clock up ahead will appear to all aboard to be ticking faster.

Yes, that's a good way of looking at it. You still do need a definition of simultaneity to use while "boosting. The most common definition of simultaneity used fits the above description of what happens. This definition is to define events in the accelerated "frame" to be simultaneious when they are simultaneous in the co-moving inertial reference frame.

 

[1977ub]

Two people are in ships sitting at different points along x. They find that their clocks are synchronized. They agree that one second into the future, they will each hurl an identical boulder backward along the x-axis with the same force. After they do so, they find that their clocks are no longer synchronized. I have found this puzzling, but certainly:

1) They can't be synchronized in both the rest and the moving frame.
2) They absolutely *have* to be synchronized in the rest frame due to the symmetry of the actions.
3) Therefore they can't be any longer synchronized in the moving frame.

This I find very simple and persuasive. Furthermore, as the vehicle accelerates, this effect would multiply, and the clocks would become ever more desynchronized to those on the ship, suggesting differing clock rates along the ship.

Looks like I'll need to delve further into the equations of GR to be convinced that the differing clock rates at different altitudes are a similar phenomenon.

 

[1977ub]

2) Actually I take it back. Since the hurling process takes time, and they are both moving wrt rest frame by the end of the boulder hurling process, I expect the forward person to finish hurling later that the back individual as seen from the rest frame.

3) So this simple logic doesn't convince me that they must be out of synch in the moving frame.

Perhaps there's no "stick-figure" way to illustrate this without performing the integration of the changing velocity.