I Simultaneity and the Twin Paradox

Click For Summary
The discussion revolves around the complexities of simultaneity in the context of the Twin Paradox, particularly how different perspectives affect the understanding of time dilation. A key insight is that the stationary twin and the traveling twin perceive simultaneity differently, leading to confusion when interpreting diagrams that do not account for both perspectives. The conversation also addresses the implications of acceleration and inertial frames, emphasizing that the traveling twin's experience is inherently different due to their path through spacetime. The potential for a hypothetical inertialess drive raises questions about detecting changes in motion, but it is clarified that the fundamental differences in aging between the twins remain regardless of the frame of reference. Ultimately, the discussion highlights the necessity of understanding the nuances of relativity to grasp the Twin Paradox fully.
  • #91
Freixas said:
Let me see if I can paraphrase some useful content out of this. I send a real person on a real spaceship to a real location, transmitting video the whole way. All of this is real, but when we take the video and adjust frames for light delay, we have shifted out of the real and into the imaginary.

When you adjust for light travel time you are assuming that a clock located there (where the movie was made) is synchronized with a clock located here (where the movie is viewed). Others will simply not agree that the clocks are synchronized. It doesn't make anything less real, it just means that simultaneity is not absolute.

Consider the location of an accident involving the collision of two cars. That location can be described as, say, two blocks east of the courthouse, but it can also be described as two blocks west of Bob's Diner. Each description is valid, the fact that they differ doesn't make the collision any less real. Everybody who is familiar with this scheme of locating events will find nothing peculiar about it.

Likewise, everybody who is familiar with Einstein's relativity will find nothing peculiar about simultaneity being relative.
 
Physics news on Phys.org
  • #92
Mister T said:
When you adjust for light travel time you are assuming that a clock located there (where the movie was made) is synchronized with a clock located here (where the movie is viewed).

This is not my assumption at all; my problem statement long ago implies the opposite. The assembly of the final video is reference-frame-independent, in any case. As for viewing a video, as long as the viewer and the video player are in the same reference frame, you are fine. If the viewer and the player are not, the viewer won't see the show for very long, anyway.
 
  • #93
OK, I believe I figured out my error by working it through to a logical contradiction.

Let's review the A, B, C, M scenario: for A and M are 4 LY apart and in the same inertial frame. B travels from A to M at a constant 0.8c. A and B synchronize clocks at 0 when they pass. C also travels at a constant 0.8c, reaching M at the same time as B and continuing on to A. For B and C, the distance between A and M is 2.4 LY and the travel time is 3 years. For A (and M) B and C take 5 years to cover 4 LY. A sends a video of his clock to B and C.

What I added was B' who is in the same inertial frame as B but trails by 2.4 LY (B's view) or 4 LY (A's view). There is also a C' in the same inertial frame as C, but leading by 2.4 LY (or 4 LY).

When B reaches M, B' reaches A. My incorrect thinking was in believing the following were both true:
  • Two observers are co-located but in different inertial frames. An event occurs at that location at time t for the first observer and t' for the second. They now know when the event occurred in their own inertial frame and the other's inertial frame.
  • Two observers are in the same inertial frame. They consider two moments simultaneous if each of their synchronized clocks displays the same time.
The incorrect conclusion, then, is that if the co-located observer's t maps to t', then t maps to t' for all observers in the same inertial frame. Again, bitten by the relativity of simultaneity.

Let's examine this using B and B'. B reaches M, receives A's video clock showing 1yr. Correcting for light delay, B would say "I was 1 2/3 years into my journey when A sent this video frame." Continuing to gather video after passing point M, B eventually receives a video clock of 2.4 years. Correcting for light delay would put B at M when the signal was sent. B' would have been at A at the same time as B was at M, so would have seen the signal as it was sent. So B' would directly see A's clock showing 2.4 years.

The idea I had was that a light-delay correction was equivalent to a direct observation at the event's location. Running the same logic for C and C', one would conclude that C' saw A's clock showing 7.6 years at the same time and location as B' saw 2.4 years. This is impossible.

When B is at A, their clocks both read 0. For A, that means M's clock is also 0, but for B (if I did the math correctly) it reads 2.6 years. A thinks his clocks are synchronized, but B doesn't. B', 2.4 LY back, has the same problem with A's clock: it doesn't read 0, it reads 2.6 years. When B' reaches A, A's clock reads 5 years. When B reaches M, M's clock reads 5 years. Neither is surprised since they considered the clock ahead of them off by 2.6 years. They both think that A's clocks are running slow by a factor of 0.6.

I could run the numbers for A's view and C's view, but it's not important.

Sometimes things are clearer when one can figure out the problem one's own.

For what it's worth, a light-delay-corrected video will show an effect that appears to reflect the planes of simultaneity. In other words, A's clock will be seen to run slow by a factor of 0.6 and there will be a gap at turn-around. People seemed to have trouble with the whole video mapping concept, so let me see if I can clarify:
  • Record the video as received.
  • For B's recorded video, map each frame to a new time on the mapped video. Say frame n occurs at B's time t. We then place n at time f(t), where f() is the light-delay correction formula for B. We completely ignore the recorded value of A's clock on frame n when we do this mapping.
  • When B is at A, f(0) = 0, so the frame (showing 0) is placed at time 0.
  • When B is at M, f(3) = 1 2/3, so the frame (showing 1) is placed at time 1 2/3.
  • B's entire 3 years of video is mapped to a new video 1 2/3 years long.
B transfers the video to C, who continues the recording.
  • We need two mapping functions for C's leg: g() and h().
  • g() maps a frame to the light-delay-corrected position of B. This is a tricky, of course. It fills in the mapped video from 1 2/3 to 3 years.
  • h() maps a frame to the light-delay-corrected position of C.
  • We use g() until g(t) = 3 (when B reached M).
  • We use h() after g(t) = 3. However, when g(t) = 3, h(t) < 3. In other words, C will be processing frames it received before it reached M. It throws these away. When h(t) = 3, he starts filling the incoming leg of the video. The frame will show A's clock at 7.6. h(6) = 6, so that frame (showing 10) is placed at time 6.
I'll leave determining f(), g() and h() as an exercise for the reader. :-)

Let's say we have an infinite line of B' ships, so there's always one adjacent to A. Let's say the video frame rate is 30 frames/sec and that, on each 1/30th second mark, the B' closest to A captured one frame showing A's clock. This repeats until the lead B reaches M. Assemble the frames in sequence (remember that all B's clocks are synchronized). The video produced this way will show A's clock going from 0 to 5 years over a 3 year period. It is not equivalent to the light-delay-corrected video, as I originally thought.
 
  • #94
Freixas said:
When B reaches M, B' reaches A.

In whose frame? You can't use the word "when" in this way without specifying a frame. It looks like you mean in the common rest frame of B and B', but you should make this explicit.

Freixas said:
The incorrect conclusion, then, is that if the co-located observer's t maps to t', then t maps to t' for all observers in the same inertial frame. Again, bitten by the relativity of simultaneity.

Yes, you've got it.

Freixas said:
The idea I had was that a light-delay correction was equivalent to a direct observation at the event's location. Running the same logic for C and C', one would conclude that C' saw A's clock showing 7.6 years at the same time and location as B' saw 2.4 years. This is impossible.

Yes, you've got it.

Freixas said:
When B is at A, their clocks both read 0. For A, that means M's clock is also 0, but for B (if I did the math correctly) it reads 2.6 years.

You have the right idea here, but you need to check your math. I get that M's clock reads 3.2 years at the event on M's worldline which is simultaneous, in B's frame, with the event of B meeting A. (And M is 2.4 light-years from B, in B's frame, at this event, and is moving towards B at speed 0.8, so M will meet B in 3 years, in this frame. Btw, knowing that M's clock reads 5 years when M meets B, and that M's clock runs slow by the time dilation factor of 0.6 in B's frame, you can check that the 3.2 years that I just quoted is correct.)
 
  • #95
Freixas said:
The video produced this way will show A's clock going from 0 to 5 years over a 3 year period.

No, it won't. It will show A's clock going from 0 to 1.8 years over a 3 year period. All of the B clocks are sychronized in the B rest frame, not the A rest frame, but you are thinking of simultaneity in the A rest frame.
 
  • #96
PeterDonis said:
You have the right idea here, but you need to check your math. I get that M's clock reads 3.2 years at the event on M's worldline

Ah, yes, I forgot the dilation factor and I might have swapped time and distance. Let's see, for B, A's clocks run slower by 0.6. B travels to M in 3 years, [edit so 5. 3 * 0.6 = 1.8 years pass for M], so for 1.8 years to have passed and A's clock to read 5 at the end of that, the clock must have started at 3.2. Got it now.
 
  • #97
PeterDonis said:
No, it won't. It will show A's clock going from 0 to 1.8 years over a 3 year period. All of the B clocks are sychronized in the B rest frame, not the A rest frame, but you are thinking of simultaneity in the A rest frame.

OK, let's say B1 is the lead B ship and BN is the last B ship. When B1 is at A, B1's clock reads 0 and A's clock reads 0, so we know the video starts at 0. When A meets B1, it would seem that B1 would view M's clock in the same way that BN views A's clock. So I thought BN would, on arrival, also view A's clock as reading 5. When at A, BN would not view M's clock as reading 5, but 8.2. In another 3 years, BN would reach M where the clock would read 10.

BN's clock reads 3 years when it reaches A, so the video frame at 3 years should show 5.

Another way to think about it is that when B1 is at M, A thinks 5 years have passed. BN should be at A at the same time that B1 is at M, no matter whose frame I approach it from. So if the video ends with 1.8 at year 3, either I don't understand something or you are assembling the video in a different way than I am. B1 might think that A's clock is 1.8 when B1 is at M, but the video is captured at A by BN, where it should be 5.
 
  • #98
Freixas said:
OK, I believe I figured out my error by working it through to a logical contradiction.

Let's review the A, B, C, M scenario: for A and M are 4 LY apart and in the same inertial frame. B travels from A to M at a constant 0.8c. A and B synchronize clocks at 0 when they pass. C also travels at a constant 0.8c, reaching M at the same time as B and continuing on to A. For B and C, the distance between A and M is 2.4 LY and the travel time is 3 years. For A (and M) B and C take 5 years to cover 4 LY. A sends a video of his clock to B and C.

What I added was B' who is in the same inertial frame as B but trails by 2.4 LY (B's view) or 4 LY (A's view). There is also a C' in the same inertial frame as C, but leading by 2.4 LY (or 4 LY).

When B reaches M, B' reaches A.

Wait. If B' trails B by 2.4 LY in B's rest frame, then it trails B by 1.44 LY in A's rest rest frame.
Or, if B' trails B by 4 LY in A's rest frame, then it trails B by 6 2/3 LY in the rest frame of B and B'.

Only the second choice allows B to reach M as B' reaches A, and then only according to the rest frame of A and M.

Thus in the rest frame of A things start like this:

B'-------------------B
----------------------A--------------------M
------------------------------------------------------------------C--------------------C'
Which will eventually become:

----------------------B'--------------------B
----------------------A--------------------M
--------------------------------------------C--------------------C'
The rest frame of B will start like this:

B'--------------------------------B
-----------------------------------A------------M
----------------------------------------------------C-------C'
The distance between A and M is 2.4 LY
Also, for B, the addition of velocities gives a relative velocity of 0.9756c for C and C', and thus a distance between them of ~1.47 LY

Which as events unfold you will reach this point.

B'--------------------------------B
---------------------A------------M
-----------------------------------C-------C'

note that When B and M meet, B' and A are well short f meeting.
 
  • #99
Freixas said:
When B1 is at A, B1's clock reads 0 and A's clock reads 0, so we know the video starts at 0.

Yes. But this "when" doesn't require any notion of simultaneity, because B1 and A are co-located.

Freixas said:
When A meets B1, it would seem that B1 would view M's clock in the same way that BN views A's clock.

I'm not sure what you mean by this, but it seems to be leading you astray, so let's take a step back.

First, we need to be clear about what defines which B clock is clock BN. Clock BN is the clock that reads exactly 3 years at the instant at which it passes clock A. That is the definition in B's frame of "happens at the same time as B1 meets M".

It will also be helpful to define another B clock, which I'll call BX, which is the clock that reads exactly 0 at the instant at which it passes M. The reading on M's clock at this event will be, as we've already seen, 3.2 years

Now, we know that when B1 meets M, M's clock reads 5 years, and B1's clock reads 3 years. And we've just seen that M's clock reads 3.2 years when clock BX passes it--and clock BX reads 0 at that same event. So M's clock ticks 1.8 years between those events. And that corresponds to M's clock ticking 1.8 years while M is traveling from BX to B1, while 3 years elapse in the B frame.

The same reasoning applies to A traveling from B1 to BN: B1's clock reads 0 when A passes B1, and BN's clock reads 3 years when A passes BN. And we know A's clock reads 0 when A passes B1; therefore, A's clock must read 1.8 years when A passes BN. In other words, the difference in A clock times between passing B1 and passing BN, must be the same as the difference in M clock times between passing BX and passing B1.

Another way of putting this: we have that, in B frame, M's clock reads 3.2 years when A's clock reads 0. In other words, that is the clock offset between A and M in the B frame (which is another way of describing the relativity of simultaneity between the two frames). But that clock offset is constant--it's true for any pair of A and M clock readings that are taken at the same time in the B frame. So it must also be true that, when M's clock reads 5 years, A's clock reads 1.8 years in the B frame. And that is the same as saying that A's clock reads 1.8 years when A passes BN.
 
  • #100
Freixas said:
When at A, BN would not view M's clock as reading 5, but 8.2. In another 3 years, BN would reach M where the clock would read 10.

No. Let's continue the analysis from my last post and figure out what M's clock reads when M passes BN.

The simplest way of doing this is to realize that clocks BN, B1, and BX are all equally spaced in the B frame. (Can you see why?) So M's clock must tick the same amount of time between passing BX and B1, as it does between passing B1 and BN. We know the former time is 1.8 years, so the latter must be as well. Hence, M's clock reads 6.8 years when M passes BN.

Another way of doing it is to realize that, on clock B1, 3 years elapse between A passing and M passing. Therefore, 3 years should also elapse on clock BN between A passing and M passing. And the difference between the A and M clock readings that B1 sees on the two passings is 5 years. So the difference between the A and M clock readings that BN sees on its two passings (A and M) must also be 5 years. Since BN sees A's clock reading 1.8 years when A passes, BN must see M's clock reading 1.8 + 5 = 6.8 years when M passes.
 
  • #101
Freixas said:
when B1 is at M, A thinks 5 years have passed. BN should be at A at the same time that B1 is at M, no matter whose frame I approach it from

No! You've forgotten relativity of simultaneity again. "At the same time" is frame-dependent. So is "when" in reference to events that are not co-located.

Here is a correct statement of the first part of the above quote: In the A frame, when B1 is at M, 5 years have passed. That is, A's clock reads 5 years at the event on A's worldline which is simultaneous, in the A frame, with B1 passing M. But that does not mean that A's clock reads 5 years at the event on A's worldline which is simultaneous, in the B frame, with B1 passing M. That is a different event, and as I've already shown, A's clock reads 1.8 years at that event (it's the event at which BN passes A).
 
  • #102
PeterDonis said:
Here is a correct statement of the first part of the above quote: In the A frame, when B1 is at M, 5 years have passed.

And to expand on this further, here is a corrected statement for the B frame: in the B frame, when B1 is at M, 3 years have passed. Note: not 1.8 years! 3 years. Why? Because we are counting "have passed" from the event where B1 meets A, and if there's one thing that we have always agreed on in this whole discussion, it's that B1's clock ticks 3 years from meeting A to meeting M. :wink: And since B1 is at rest in B's frame, B1's clock time is the same as time in B's frame.

Then we have a further statement: in the B frame, 1.8 years elapse on clocks A and M between B1 meeting A and B1 meeting M. That's just a simple consequence of time dilation for A in B's frame--but now it is stated precisely enough to see exactly what it does and doesn't mean. We could also restate the pair of meetings involved as: between BN meeting A and BN meeting M. The statement is true either way.
 
  • #103
PeterDonis said:
I'm not sure what you mean by this, but it seems to be leading you astray, so let's take a step back.

The thing that is leading me astray is that I picture a line of B's spaced 4 LY apart and traveling at 0.8c. Conjunctions are events. Events happen in all frames. Objects are in all frames. Clocks (and their readings) can be viewed in all frames.

I think (incorrectly?) that this means that A sees a B pass by every 5 years. So if a B passes by A and observes that A's clock is not a multiple of 5 years, my brain seizes up. Are B's showing up faster and faster? Or do B's pass by every 1.8 of A's years?

This imagery is preventing me from following any of your detailed explanations. I understand that B sees 1.8 years pass by on A's clock, but that's not the same as the reading that A's clock will show. I can't picture that as anything except a multiple of 5.
 
  • #104
PeterDonis said:
And to expand on this further, here is a corrected statement for the B frame: in the B frame, when B1 is at M, 3 years have passed. Note: not 1.8 years! 3 years. Why? Because we are counting "have passed" from the event where B1 meets A, and if there's one thing that we have always agreed on in this whole discussion, it's that B1's clock ticks 3 years from meeting A to meeting M. :wink: And since B1 is at rest in B's frame, B1's clock time is the same as time in B's frame.

Then we have a further statement: in the B frame, 1.8 years elapse on clocks A and M between B1 meeting A and B1 meeting M. That's just a simple consequence of time dilation for A in B's frame--but now it is stated precisely enough to see exactly what it does and doesn't mean. We could also restate the pair of meetings involved as: between BN meeting A and BN meeting M. The statement is true either way.

I agree with all this. However (relativity of simultaneity), when B and A are together and agree that their clocks are synchronized at 0, BN disagrees and says that A's clock actually reads 3.2. BN then travels to A, where he arrives in 3 years (his time) and 1.8 years (A's time). A flashes a time of 5 years, which is what goes on the video. So the video starts at 0 (B's video frame) and ends at 5 (with BN's video frame)
 
  • #105
Freixas said:
I picture a line of B's spaced 4 LY apart and traveling at 0.8c.

In the A frame, the B's are traveling at 0.8c, yes, but they are not spaced 4 LY apart. The A's are. The B's spacing is shorter--quite a bit shorter. (Note that I am assuming that the B's are all spaced the way BX, B1, and BN are spaced.)

How much shorter? Consider the "meetings": M meets BX when M's clock reads 3.2 years; M meets B1 when M's clock reads 5 years. So the meetings in the A frame are spaced 1.8 years apart. The B's are traveling at 0.8c in the A frame, so in 1.8 years a B will travel 1.8 * 0.8 = 1.44 light years. So that's how far apart the B's are in the A frame.

Another way of figuring this is to observe that, in the B frame, the B's are all at rest and are 2.4 LY apart. (And A and M, and any other "A" type objects we might concoct, are moving at 0.8c in the opposite direction from the direction the B's are moving in the A frame. For concreteness, I have been thinking of the B's moving to the right in the A frame, and the A's moving to the left in the B frame.) But in the A frame, the distance between the B's is length contracted by a factor of 0.6; so in the A frame, the B's are 2.4 * 0.6 = 1.44 LY apart.

Freixas said:
Conjunctions are events. Events happen in all frames. Objects are in all frames. Clocks (and their readings) can be viewed in all frames.

All of these statements are true yes. But it makes a big difference which events/conjunctions you look at.

Freixas said:
I think (incorrectly?) that this means that A sees a B pass by every 5 years.

Your guess that you were incorrect is correct. :wink: If we space the B's the way B1 and BX and BN are spaced, then an A sees a B pass by every 1.8 years by the A's clock. See above.
 
  • #106
Freixas said:
when B and A are together and agree that their clocks are synchronized at 0, BN disagrees and says that A's clock actually reads 3.2.

No. Both B1 and BN are at rest relative to each other, so they have the same notion of simultaneity. So whatever B1 says A's clock reads at a given time, BN will say the same. That's what "clock synchronization" means.

To put it another way: the purpose of having the whole fleet of B observers is so that, at any event of interest, there will be some B observer there to record his clock time. At the event where B1 meets A, that B observer is, of course, B1. But the definition of "time" in the B frame just is whatever time is recorded on the clock of the B observer who is located at that event. So B1's clock time--zero--when he meets A is also the "time" at which every other B observer says that event happened.

Yet another way of looking at it: A's clock reading at the event where B1 meets A is an invariant--it's 0. That's true for all observers in all frames (you've already agreed to this). So every B observer must say that, at the event at which B1 meets A (which is also an invariant--it's an event), A's clock reads 0. But by the definition of "time" for all B observers, all B observers say that that event happened at time zero. That's what "time" in the B frame means. So every B observer must say that, at his time 0, A's clock reads 0.

What every B observer will not say is that, at his time 0, the time on the clock of the A observer who happens to be passing him at that instant will read zero. That, of course, is false--we already know a counterexample, since we know that when BX passes M, BX's clock reads zero, but M's clock reads 3.2. But that does not mean that BX will say that, when he passes M, A's clock reads 3.2. Why not? Relativity of simutaneity! (But correctly applied this time.) Or, to put it another way, the A clocks are offset in the B frame--A's clock runs 3.2 years earlier than M's clock does. So BX can calculate, from that clock offset, that when he passes M, and M's clock reads 3.2, A's clock must read zero. And of course he gets that confirmed when he gets the message from B1 that, when B1 passed A (which happened at clock time 0 for B1, so for BX, it happened at the same time BX passed M), A's clock read 0.
 
  • Like
Likes Freixas
  • #107
PeterDonis said:
Your guess that you were incorrect is correct. :wink:

Well, it's nice to be right about something!

Before I asked my first question on PhysicsForums, I had worked through an interesting conundrum. We have a line of A objects equally spaced and in the same inertial frame. We have a similar line of B objects so that each A object is adjacent to a B object. B objects are all in the same inertial frame, but a different frame than A. It appears that A's and B's will all be in conjunction at regular intervals.

I was able to figure out on my own that this could only be the situation from one viewpoint. In the other frame, A's (or B's, depending on the viewpoint) would be closer together and conjunctions would not be simultaneous at all.

I have switched terminology and specifications several times, so even I'm not sure who's who and what's what. The idea for the video was to have an infinite line of B's trailing a lead B so that there would be one B always adjacent to A. The thinking is that this would be equivalent to calculating a light-delay-corrected video as per a boring mapping I detailed a while back. It isn't because of relativity of simultaneity problems. That's sufficient for me at this point, I can work the math later.

Thanks for working though all this with me.
 
  • #108
Freixas said:
Well, it's nice to be right about something!

Before I asked my first question on PhysicsForums, I had worked through an interesting conundrum. We have a line of A objects equally spaced and in the same inertial frame. We have a similar line of B objects so that each A object is adjacent to a B object. B objects are all in the same inertial frame, but a different frame than A. It appears that A's and B's will all be in conjunction at regular intervals.
You mean something like this:
clock_sync1.gif
I was able to figure out on my own that this could only be the situation from one viewpoint. In the other frame, A's (or B's, depending on the viewpoint) would be closer together and conjunctions would not be simultaneous at all.
Such as when when you switch to the frame for the top row of clocks, and get this:
clock_snyc2.gif
 

Attachments

  • clock_sync1.gif
    clock_sync1.gif
    660.9 KB · Views: 760
  • clock_snyc2.gif
    clock_snyc2.gif
    634.8 KB · Views: 790
  • Like
Likes Freixas
  • #109
  • #110
Freixas said:
We have a line of A objects equally spaced and in the same inertial frame. We have a similar line of B objects so that each A object is adjacent to a B object. B objects are all in the same inertial frame, but a different frame than A.

One point of terminology: instead of "in an inertial frame", it's much better to say "at rest in an inertial frame". All objects are "in" all inertial frames; they don't disappear from one particular frame just because they happen to be moving in that frame.
 
  • #111
PeterDonis said:
One point of terminology: instead of "in an inertial frame", it's much better to say "at rest in an inertial frame". All objects are "in" all inertial frames; they don't disappear from one particular frame just because they happen to be moving in that frame.

OK, I thought some objects were in non-inertial frames and that I got dinged for not specifying which it was. Every time I added inertial frame it was to eliminate acceleration from the mix. But I get your point. In this inertial frame, an object is at rest; in this other inertial frame, it is moving.
 
  • #112
Freixas said:
In this inertial frame, an object is at rest; in this other inertial frame, it is moving.

Yes, and the same goes for non-inertial frames; an object can be at rest in one non-inertial frame but moving in another (or in an inertial frame). The key difference is that inertial frames have some nice properties (like light always moving at ##c## in all directions) that non-inertial frames do not have.

Freixas said:
I thought some objects were in non-inertial frames and that I got dinged for not specifying which it was.

The point is more that, if an object is moving inertially (i.e., in free fall, feeling no force), then once you say "the inertial frame in which this object is at rest", you've uniquely specified the frame. Inertial frames are constructed in a particular way, and specifying which object is at rest in one is sufficient.

With non-inertial frames, by contrast, even if you know the entire worldline of an object that is at rest in such a frame, you haven't uniquely specified the frame. So you can't just say "the non-inertial frame in which this object is at rest". You have to give more information about how the non-inertial frame is constructed.
 
  • Like
Likes Freixas
  • #113
Janus said:
You mean something like this:
clock_sync1-gif.gif

I'm puzzled by this animation. The clocks are small and I can't single-step through it, but aren't the clocks in the top row running at the same rate as the ones in the bottom row? Shouldn't they be running slower?
 

Attachments

  • clock_sync1-gif.gif
    clock_sync1-gif.gif
    660.9 KB · Views: 414
  • #114
Freixas said:
I'm puzzled by this animation. The clocks are small and I can't single-step through it, but aren't the clocks in the top row running at the same rate as the ones in the bottom row? Shouldn't they be running slower?
For this particular set of animations, I assume that the clocks in the upper row have had their tick rates adjusted so that they match that of the clocks in the lower row as measured from this frame. That way, as any clock in the top row passes a clock in the lower row, they read the same time.

Then when we switch to the frame in which the upper row is at rest, we see that, even though the clocks are all out of sync with each other, the lower clocks run slower than the upper clocks, and the lower clocks are closer together, whenever a lower and upper clock pass each other they still read the same time.
 
  • #115
Mister T said:
When you adjust for light travel time you are assuming that a clock located there (where the movie was made) is synchronized with a clock located here (where the movie is viewed).

Freixas said:
This is not my assumption at all; my problem statement long ago implies the opposite.

Anytime anyone adjusts for light travel time what they are doing is saying that when the light left some distant position over there, the time over here was such-and-such. For example, if the light arrives here at 9:00 am and was emitted from some position that's one light-hour away from here, I will conclude that the light must have left at 8:00 am. Let's say I just happened to be taking my first bite of breakfast at 8:00 am. I therefore conclude that the emission of the light was simultaneous with my first bite.
 
  • #116
@PeterDonis: I like to work things out fully for myself, which takes time. I understand things better when I can crank through all the logic on my own.

I thought I had found an error in my work. This just told me my conclusions were wrong, but it didn't provide a solid understanding of why. Thus, I revisited the thread and re-read a number of your posts.

I realized I still didn't understand how BN could read A's clock as 1.8. Tracing through your comments, I think the problem starts here:

PeterDonis said:
No. Both B1 and BN are at rest relative to each other, so they have the same notion of simultaneity. So whatever B1 says A's clock reads at a given time, BN will say the same. That's what "clock synchronization" means.

If I take this approach, I arrive at a logical contradiction. So I clearly still don't understand.

Let's look at things from A's frame only. Let's remove the infinite line of closely spaced B's and replace it with a line of B's that are spaced evenly 4 LY apart as measured by A. Traveling at 0.8c, A will expect to see a B pass by every 5 years. The math seems simple and unavoidable. Each time a B passes by and sees A, it should see that A's time is a multiple of 5 (if the first conjunction occurred at 0). I can't picture any other scenario that makes sense. We're are looking at things from A's view, but the event (and A's clock reading) is in all frames.

I'm not looking at things from B's frame at all. It shouldn't matter. A's viewpoint provides all the information I need. We don't care about B's clock anywhere, just about what A's clock says at conjunctions.

You tell me that the first trailing B (what you call BN) will see A's clock as reading 1.8 years at conjunction. I can't see how. Help!

This is really the heart of my objection. What follows is just details.

--------------------------------------------------------------------------------

Let me draw the clocks based on your statement about clock synchronization. I am going to add a line of A's, also spaced 4 LY apart as measured by A.

A . . . . A . . . . A . . . . A . . . . A
B . . . . B . . . . B . . . . B . . . . B
^-7.2 . .-5.4 . . .-3.6 . . .-1.8 . . . 0
^-5.4 . . .-3.6 . . .-1.8 . . . 0
-3.6 . . .-1.8 . . . 0
^-1.8 . . . 0
^0
The caret points to the corresponding B's view of each of A's clocks at B's time 0. The time listed under each A, is the time as perceived by the B with the caret. As I imagine movement in typical Western left-to-right fashion, the rightmost A is the one that we've been concerned with. The rightmost B is the "lead B" or B1. All times are for when the lead B is at time 0, so all B's perceive the lead A to have time 0. This is my interpretation of your statement.

The other times are what I think they would be so that B would perceive A's clocks advancing by 1.8 years as one B went to the next. If we advance this diagram by 3 years (B's time) or 5 years (A's time), the trailing B would say that the lead A's clock reads 1.8, which I believe to be impossible.

Here's the way I think things should like so that B sees a multiple of 5 at each conjunction. B also sees A's clocks advancing by 1.8 years during the trip:

A . . . . A . . . . A . . . . A . . . . A
B . . . . B . . . . B . . . . B . . . . B
^0 . . . 3.2 . . . 7.4 . . . 9.6 . . . 12.8
^0 . . . 3.2 . . . 7.4 . . . 9.6
^0 . . . 3.2 . . . 7.4
^0 . . . 3.2
^0

In this example, the last B would reach A (the lead A) in 4 * 3 = 12 B years (4 * 1.8 = 7.2 years A years from B's view) and A's clock would read 7.2 + 12.8 = 20.

In my diagram, when B's clocks are at time 0, each adjacent A's clock also reads 0. But the lead A's clock reads 0 only for the lead B.

I have no idea if this diagram is a representation of how things work. All I can say is that it satisfies these two constraints: A's clocks are a multiple of 5 at conjunctions and B's perceive A's clock as running at 0.6x (assuming I did the math right, always a concern).
 
  • #117
Mister T said:
Anytime anyone adjusts for light travel time what they are doing is saying that when the light left some distant position over there, the time over here was such-and-such. For example, if the light arrives here at 9:00 am and was emitted from some position that's one light-hour away from here, I will conclude that the light must have left at 8:00 am. Let's say I just happened to be taking my first bite of breakfast at 8:00 am. I therefore conclude that the emission of the light was simultaneous with my first bite.

Sure. That has nothing to do with where a movie is viewed. You can watch the same movie at home or in an interstellar cruiser and it still looks the same to you.

For example, let's say a clock reads 5 PM 1 light hour away from where you are having your breakfast. One hour after your first bite, you look in a powerful telescope and see the distant clock reading 5 PM. You then say, "I was taking my first bite when the clock actually read 5 PM." If you had a video tape of you eating breakfast and a video of telescope view, you could assemble a light-delay corrected video showing, in split-screen, the two events happening simultaneously. However, a clock located "where the movie is viewed" would have no influence on any of this. You could, after all, view the movie multiple times.
 
  • #118
Freixas said:
Let's remove the infinite line of closely spaced B's and replace it with a line of B's that are spaced evenly 4 LY apart as measured by A.

Ok so far. (Note, though, that this is a different spacing than the one we have been assuming, implicitly, thus far. See below.)

Freixas said:
Traveling at 0.8c, A will expect to see a B pass by every 5 years.

Ok so far.

Freixas said:
Each time a B passes by and sees A, it should see that A's time is a multiple of 5 (if the first conjunction occurred at 0).

Yes, if the first conjunction occurred at 0. But, if the B clocks are all synchronized with each other--meaning that all of them are synchronized using the natural notion of simultaneity in the B rest frame--then only one of the B clocks will have a first conjunction with an A clock that reads zero at the same instant that that B clock reads zero. That clock is the clock we have been calling B1.

So here is the first logical error you are making: you are assuming that all of the B clocks have a conjunction with an A clock at which the B's clock reads zero and the A clock it is passing reads zero. That is only true of one B clock.

Freixas said:
You tell me that the first trailing B (what you call BN) will see A's clock as reading 1.8 years at conjunction. I can't see how. Help!

You were the one who defined what clock BN sees, not me. I was just working out consequences of your definition that you did not realize.

First, let's be clear about clock B1. It meets A when its clock reads zero and A's clock reads zero. It meets M when its clock reads 3 years and M's clock reads five years. We agree on those things, at least.

Now here is how you defined clock BN:

Freixas said:
BN's clock reads 3 years when it reaches A

Let's analyze this in the A frame, since you said that's all you're concerned about. In this frame, the B clocks are moving to the right (positive x direction) at speed 0.8. Clock M is at rest in this frame 4 light years to the right of clock A (i.e., at x = 4). Clock B1 therefore passes through the events ##(x, t) = (0, 0)## and ##(x, t) = (4, 5)##. And the spacetime interval between these two events is ##\sqrt{5^2 - 4^2} = 3##, which is consistent with clock B1 reading 3 years when it passes M (because we have specified that it reads zero when it passes A).

Now consider clock BN. Its clock reads 3 years when it passes A, which means that this event has coordinates ##(0, T)## for some ##T## that we have to calculate (the ##x## coordinate of this event must be zero because A is always at ##x = 0##). You have been implicitly assuming that all of those events have the same value of ##t## in the A frame--in other words, that since clock B1 reads 3 years at ##t = 5## (when it passes M), then any other B clock must also read 3 years at ##t = 5## (but at some other ##x## value)--which would mean clock BN would read three years at the event ##(x, t) = (0, 5)##. But that is obviously false, because of relativity of simultaneity--or, to put it another way, because the B clocks must be offset in the A frame.

How much are they offset? There are a number of ways to calculate this, but the simplest is to use the Lorentz transformation. We know that clock B1 reads 3 years at event ##(4, 5)##. We know that clock BN reads 3 years at event ##(0, T)##. And we know that, for both of these events, the equation ##t' = 3 = \gamma \left( t - v x \right)## must hold. So we have ##3 = (5/3) \left( 5 - 4 * 0.8 \right) = (5/3) T##. The first equality is obviously correct and gives us a sanity check; the second equality easily gives us ##T = 3 (3/5) = 9/5 = 1.8##. So, as I have been saying, when clock BN, defined as you defined it, meets clock A, clock BN reads 3 years (by your definition) and clock A reads 1.8 years (by the calculation I have just done).

So to summarize: each B clock passes an A clock every 3 years by its own time, and each A clock reads 5 years later than the last A clock it passed. But if we compare adjacent B clocks, the readings they see on the same A clock when they pass it are not separated by 5 years; they are separated by only 1.8 years. And, as should be evident, these B clocks are not spaced 4 LY apart in the A frame. They are spaced only 1.44 LY apart (as I calculated before). And the B clocks do not all see the A clock readings be exact multiples of 5 years when they pass; only clock B1 does. Clock BN, for example, sees the A clock readings as multiples of 5 years plus a fixed offset of 1.8 years.

Now, let's ask a different question: suppose we define "adjacent" B clocks by the requirement I quoted at the start of this post--that they are spaced 4 LY apart in the A frame. Under this requirement, yes, each B clock will see each A clock read some multiple of 5 years when it passes it, and will also see each A clock read 5 years later than the previous B clock did when it passed the same A clock. But now the B clock readings will not all be multiples of 3 years; they will still be 3 years apart as they pass each successive A clock, but only clock B1 will see its own readings be multiples of 3 years (0, 3, ...).

For example, call the next clock in the B series under this definition clock BA--it is the clock that passes clock A when clock A reads 5 years. What will clock BA read at this passing? We didn't quite calculate this above, but it's easy enough to do. We calculated above that clock BN reads 3 years at ##(x, t) = (0, 1.8)## in the A frame. And we know clock B1 reads zero years at ##(x, t) = (0, 0)##. So if we move along the ##t## axis of the A frame (i.e., along clock A's worldline, at ##x = 0##), we find the readings of B clocks passing us increasing at a rate of ##3 / 1.8 = 5/3##, i.e., ##\gamma##. So at ##t = 5##, we should see the B clock passing us read ##5 * 5/3 = 8 + 1/3## years. But this is just clock BA, so we have shown that clock BA reads 8 1/3 years when it passes clock A at A's clock reading of 5 years. And since 3 years will elapse on clock BA until it passes clock M, it will pass clock M at 11 1/3 years. In other words, clock BA's readings when it passes A clocks will be multiples of 3 plus a fixed offset of 2 1/3 years (whereas clock B1's readings are exact multiples of 3 years).
 
  • #119
Freixas said:
If you had a video tape of you eating breakfast and a video of telescope view, you could assemble a light-delay corrected video showing, in split-screen, the two events happening simultaneously.

Yes, but my point is that those in motion relative to you may not necessarily agree that you've made the correction for light travel time correctly, and that's the reason why you think they're simultaneous. All will agree, though, that each frame of the movie was made before it was viewed.
 
  • #120
PeterDonis said:
Now, let's ask a different question: suppose we define "adjacent" B clocks by the requirement I quoted at the start of this post--that they are spaced 4 LY apart in the A frame. Under this requirement, yes, each B clock will see each A clock read some multiple of 5 years when it passes it, and will also see each A clock read 5 years later than the previous B clock did when it passed the same A clock. But now the B clock readings will not all be multiples of 3 years; they will still be 3 years apart as they pass each successive A clock, but only clock B1 will see its own readings be multiples of 3 years (0, 3, ...).

A's "5 years" will fall 8 1/3 years into the mapped video. Let's see, I pictured the "2 .4 years" frame mapped to the 3 year mark, so both numbers scale at 0.6x. This seems to show that both methods of generating the video are equivalent. In other words, if we go back to the infinite line of B's, the B adjacent to A when A sends the "2.4 year" frame should have a clock reading of 3 years, no?

That makes me wonder what I did specify.

I find in post 93: Let's say we have an infinite line of B' ships, so there's always one adjacent to A. Let's say the video frame rate is 30 frames/sec and that, on each 1/30th second mark, the B' closest to A captured one frame showing A's clock. This repeats until the lead B reaches M. That seems OK.

In post 95, I say: The video produced this way will show A's clock going from 0 to 5 years over a 3 year period. That's wrong, wrong, wrong. Where I did I come up with this? It should have said 0 to 2.4 years over a 3 year period.

Now we get to post 97: BN's clock reads 3 years when it reaches A, so the video frame at 3 years should show 5. At this point, the terminology has got out of control. I actually defined BN as the "last ship". That means that it's the ship adjacent to A when the lead B reaches M. And then I totally confused that with the scenario of evenly spaced B's, which would reach A at multiples of 5 a years. I think you assumed the evenly spaced B's scenario as well, added in my 3-year comment and went from there. I think the correct statement is: BN's clock reads 3 years when it reaches A, so the video frame at 3 years should show 2.4. BN is not one of the ships that shows up in A's skies every 5 years, just the ship that is alongside A when its clock hits 3.

Hmmm...I think I just associated BN with 3 years again. But I'm being vague about everything else. Where was BN when it's clock read 0? Well, 2.4 LY behind the lead B (in B's frame), but not in conjunction with any line of A's out of some other scenario (mixing scenarios again—this scenario has only one A, so just 2.4 LY behind B is sufficient).

Garbage in, garbage out. Shifting and incorrect terminology doesn't help. At this point, I have to go back multiple forum pages to find out what I set up.

Hmmm... I'm sure I just added some new errors. If this is all clean, let me know. Otherwise, let's see if I can work out the errors.
 

Similar threads

  • · Replies 35 ·
2
Replies
35
Views
3K
  • · Replies 4 ·
Replies
4
Views
1K
  • · Replies 43 ·
2
Replies
43
Views
4K
  • · Replies 20 ·
Replies
20
Views
3K
  • · Replies 13 ·
Replies
13
Views
3K
Replies
5
Views
2K
  • · Replies 23 ·
Replies
23
Views
3K
  • · Replies 31 ·
2
Replies
31
Views
3K
  • · Replies 11 ·
Replies
11
Views
2K
  • · Replies 137 ·
5
Replies
137
Views
10K