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.8
c. A and B synchronize clocks at 0 when they pass. C also travels at a constant 0.8
c, 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.