Exploring the Paradoxical Light Clock Problem in Special Relativity Analysis

In summary: No, angles are comparative, it just means that the angle between the emitted light and the observer is the same as the angle between the emitted light and the diagram.
  • #141
A footnote: length contraction usually applies to the distance between two bodies in relative motion, meaning, it usually applies to a length that is changing with time. In the proposed setup, the distance is fixed and has been previously marked. It is the symmetric distance between A and B.
 
Physics news on Phys.org
  • #142
altergnostic said:
h' is not being measured, it is given
I realize that, which is why I said that your givens are wrong. Givens can be wrong either by being inconsistent with themselves (e.g. given a right triangle with three equal sides) or by being inconsistent with the laws of physics (e.g. given a moving mass 2m which comes to rest after colliding elastically with a mass m initially at rest).

altergnostic said:
it is supposed to be the constituent L of the relative V that is usually given in SR problems, which we are not given in this setup and is the unknown we seek.
I thought that v=0.5c was also a given, is it not? If v is not given then you can simply plug your other givens into [itex]c^2 t^2 = y^2 + v^2 t^2[/itex] where t=h'/c and then solve for v.
 
Last edited:
  • #143
altergnostic said:
A footnote: length contraction usually applies to the distance between two bodies in relative motion, meaning, it usually applies to a length that is changing with time.
This is an incorrect understanding of length contraction. I recommend starting with the Wikipedia article on length contraction. Length contraction has nothing to do with the distance between two bodies in motion. It also does not refer to a change in length over time, it refers to a difference in the same length as measured by two different frames.
 
  • #144
DaleSpam said:
I realize that, which is why I said that your givens are wrong. *Givens can be wrong either by being inconsistent with themselves (e.g. given a right triangle with three equal sides) or by being inconsistent with the laws of physics (e.g. given a moving mass 2m which comes to rest after colliding elastically with a mass m initially at rest).

I thought that v=0.5c was also a given, is it not? *If v is not given then you can simply plug your other givens into [itex]c^2 t^2 = y^2 + v^2 t^2[/itex] where t=h'/c and then solve for v.

I have reestaded many times that you could ditch the speed of the light clock, since it is useless to this problem. What speed would you insert into gamma in the train and embankment problem? We would have to insert the speed of the projectile/beam and align our x-axis with AB in my setup, do you see? If you were given the projectile speed and the times you could calculate the distance AB, this is simply the other way around: given the distance and times you can calculate the speed. The speed of the light clock is completely trivial and you can solve even if the observer at A doesn't know it, since he is given distances and knows all times. From my analysis you can actually derive both the speed of the beam and of the clock, since after finding the total speed for the beam, you can subtract c from that and find the speed of the clock.

Quote altergnostic
A footnote: length contraction usually applies to the distance between two bodies in relative motion, meaning, it usually applies to a length that is changing with time.
DaleSpam said:
This is an incorrect understanding of length contraction. *I recommend starting with the Wikipedia article on length contraction. *Length contraction has nothing to do with the distance between two bodies in motion. *It also does not refer to a change in length over time, it refers to a difference in the same length as measured by two different frames.

Yes, but it is usually the difference measured by two frames in relative motion (you could have length contraction between two observers at rest also). But the main point is your final sentence: it is a difference between two distances being measured by different frames. The given distance h' is not being measured at all in my setup. It has been previously marked with lightsecond signs, remember? This distance is visual data, not vt (how could it be measured with no v, after all?).
 
  • #145
altergnostic said:
I prefer this analysis over the previous one, but the problem remains: you are not given any v

You are missing the point of this version of my analysis; I let v be unknown. It is the speed of the light clock relative to the observer, but I assumed no value for it. My whole point was to show that, even if you do not know the speed of the light clock relative to the observer, you can still show that the velocity of the "projectile" inside the clock is different relative to the observer than it is relative to the clock, *if* the "projectile" moves slower than light. But if the "projectile" is a light beam, then its speed is 1 (i.e., c) in both the clock frame and the observer frame. My understanding was that that was your point of confusion: you couldn't understand how a projectile's velocity could change from frame to frame if it moves slower than light, but yet the velocity of a light beam does *not* change from frame to frame. I've now given you an explicit formula that shows why that's true for the clock scenario.

You have said several times now that you can "ditch the speed of the light clock" in the analysis. I don't understand what this means. The light clock itself is part of the scenario, so you have to model its motion to correctly analyze the scenario. If you just mean that you can't assume you *know* what its speed is, that's fine; as I said above, I let that speed be unknown in my latest analysis, and showed how it doesn't matter for the question I thought you were interested in--why the projectile's velocity changes from frame to frame while the light beam's does not.

If you mean that we can somehow model the scenario without including the light clock at all, I don't see how. The motion of the parts of the light clock gives a critical constraint on the motion of the projectile/light beam inside the clock. Also, the light clock does not change direction in the scenario, so you can define a single inertial "clock frame"; but the projectile *does* change direction, so there's no way to define a single inertial "projectile frame". That means we can't just focus on the "velocity of the projectile", because that velocity *changes* during the scenario; it's not a "fixed point" that we can use as a reference.

As for "assuming" that the light beam travels at c, I have not assumed that. The only assumptions I have made are translation and rotation invariance, plus the principle of relativity, plus an assumption about how the light clock's "projectile" reflects off the mirror. It's probably futile at this point to walk through the chain of reasoning again, but I'll do it once more anyway. I'll focus on your "triangle diagram" since it's a good illustration of the spatial geometry in the unprimed frame.

We have a "projectile clock" consisting of a source/detector, which moves from A to C to D in the triangle diagram, and a mirror/reflector, which moves on a line parallel to the source/detector that passes through B at the same time (in the unprimed frame) that the source/detector passes through C. The clock as a whole moves at speed [itex]v[/itex] relative to the observer who remains motionless at A (in the unprimed frame).

The "projectile" within the clock moves at some speed [itex]v_p[/itex] in the unprimed frame (which we take to be unknown at this point), along the line A to B, then B to D. At the instant that this "projectile" (call it P1) reaches B, a second "projectile" (call it P2), moving at the *same* speed [itex]v_p[/itex], is emitted back towards A, to carry the information to the observer at A that the first projectile has reached B.

Here are some key facts about the geometry that follow from the above:

- Angle ABC equals angle CBD.
- Distance AB equals distance BD.
- Distance AC equals distance CD.
- Line BC is perpendicular to line AD.

We can also define the following times of interest (in the unprimed frame): T_AB = the time for P1 to travel from A to B; T_BD = the time for P1 to travel from B to D; T_BA = the time for P2 to travel from B to A. It is then easy to show from the above that all three of these times are equal: T_AB = T_BD = T_BA. We also have T_AC = the time for the light clock source/detector to travel from A to C, and T_CD = the time for the source/detector to travel from C to D. And we have T_AC = T_CD = T_AB = T_BD, because projectile P1 and the source/detector are co-located at A and D and both of their speeds are constant.

Thus, we have the following spacetime events:

A0 = D0 = the spacetime origin; the light clock source/detector passes the observer at A at the instant projectile P1 is emitted from the source/detector.

B1 = P1 reaches the mirror/reflector and bounces off; P2 is emitted back towards A.

C1 = the light clock source/detector passes point C.

D2 = P1 reaches the light clock source/detector and is detected.

A2 = P2 reaches the observer at A.

The above facts about the times and the motion of the light clock imply that B1 and C1 are simultaneous (in the unprimed frame), and D2 and A2 are simultaneous (in the primed frame).

Finally, we have formulas about the speeds:

[tex]v_p = \frac{AB}{T_{AB}} = \frac{BD}{T_{BD}} = \frac{AB}{T_{BA}}[/tex]

[tex]v = \frac{AC}{T_{AC}} = \frac{CD}{T_{CD}} = \frac{AC}{AB} v_p[/tex]

The last equality follows from the fact that T_AC = T_AB. Do you see what it says? It says that, if you know v_p, AC, and AB, you know v, the "light clock velocity". You stipulated v_p, AC, and AB in your statement of the problem; therefore you implicitly gave a value for v as well. But the value for v that you stated was a *different* v; it did not satisfy the above equation, which is enforced by the geometry that you yourself gave for the problem; that's why your "givens" were inconsistent.

I'll stop at this point since this post is getting long. What I'm trying to say is that the scenario you proposed has more constraints in it than you think it does; it already *contains* the information about how the projectile/light beam's velocity has to transform between frames.
 
  • #146
altergnostic said:
I have reestaded many times that you could ditch the speed of the light clock, since it is useless to this problem.
Yes, you have restated many times many incorrect things in this thread. Obviously, whenever you are interested in the effect of speed on the operation of a clock then the speed of the clock is important.

However, if it is not a given in the problem then everything becomes easier. Simply plug the givens into the equation I posted above and we find that v = 0.45 c. At 0.45 c the time dilation factor is 1.12, so in 1.12 s the clock travels .5 ls and the light travels a distance of 1.12 ls. 1.12 ls / 1.12 s = c.


altergnostic said:
given the distance and times you can calculate the speed.
Certainly. And as long as your givens are both self-consistent and consistent with physics then you will always get that light travels at c.

altergnostic said:
(you could have length contraction between two observers at rest also).
No, you cannot.

altergnostic said:
The given distance h' is not being measured at all in my setup. It has been previously marked with lightsecond signs
This is yet another self-contradictory statement. The lightsecond signs are a measuring device, and comparing anything to them is performing a measurement.
 
Last edited:
  • #147
altergnostic said:
Why are they self contradictory? [..]
I trust that that has been solved now; so we simply ditch v and find v=0.45 from your 1.12.
altergnostic said:
[..] server line of sight. I propose that he places his x-axis in line with AB so he can give all the motion to beam and solve without knowledge of the clock's velocity.
- spatial rotation is useless. Standard is to orient the system speed along X (don't you know that the Lorentz transformation uses that convention?)
- he can give no motion to the beam; and how he places his coordinates can have no effect on the beam! Seriously, nothing of that makes any sense to me.
From the link, [https://www.physicsforums.com/showthread.php?t=574757] I will comment only upon the same issue I have been discussing here: the beam leaves A and reaches B in the rest frame [..]
Sorry, the first thing you discussed here and which was not solved were the speed and direction - and those also appear in your last example, so you must be sure to get it right...
Maybe my terminology is incorrect? The rest frame is meant to be the frame at rest relative to the clock. The moving frame is supposed to be the observer who sees the moving clock.
That is exactly how I understand it; thus you disagree about the calculation method, which is identical to the method to explain the Michelson-Morley experiment.
The beam never reaches the observer at A. Only the signal from B does. He then marks the observed time of event B and plots it against the given L. He can then find the time of event B as marked on the detector's clock by subtracting the time it takes light to cross the distance between the coordinates of the event at B from the observed time. From that, he can calculate the distance from source to receiver as seen from the clock itself by transforming the calculated speed of the beam into c (the speed of light as seen locally, which is the speed supported by a huge amount of evidence). [..]
That is wrong: it appears that you heard some stuff about SR and some stuff about GR and mixed them up. There is nothing to "transform"; as you earlier claimed there is no transformation to make, as all distance and time measurements are made with the single reference system S', the "rest" system.
[MMX:] The interferometer was supposed to test the existence of the aether and find a variance of the speed of light relative to the ether. The setup was built so we had perdicular light paths.
Note: the essential point of the experiment is that the light paths in the ether are not perpendicular; I hope that that is clear.
As the apparatus (and the Earth) revolved, no fringe displacement was detected (actally, no significant displacement). So it was concluded that the speed of light was constant regardless of the orientation of the beams or the detectors relative to an absolute frame.
Not exactly, no... There was only one detector. And no effect was detected from changing orientation regardless of the velocity (although apparently Michelson only measured it at one velocity; others repeated it at other velocities).
Notice that in the equations applied to this experiment, V was the relative velocity wrt the aether, so there was only one possible V, as the aether was absolute. Since then, the speed if light was measured with ever increasing accuracy, always in the same manner: by noting the return time if light as it went forth and back a specified distance. The time of detection after emission is always proportional to c. This is exactly the premise of my setup: light can't be detected to move at any V other than c. Just notice that the beam is not detected by A, only the signal from B is. There's no return, no detection, nothing that relates the path of the beam with the experiments that tested the speed of light. [..]
I still can't make any sense of that last part. Sorry. But there are sufficient glitches in your descripton, and sufficent lack of equations, to make me confident that before anything else it will be better to go through a special relativity calculation example of MMX. And this thread is already too long. Please start a new one on MMX. I do think it likely that this whole topic here will disappear after that exercise. Especially because:
This is merely the outcome of a realisation that this thought problem has never been done before and that the postulate of the speed of light applies to source and receiver, but not necessarily to a non-receiver. It is the preconception that the postulate of the speed of light also applies to undetected light that keeps you from aknowledging the possibility I intend to discuss here. [..] the conclusion is strictly dependant upon the acceptance of the constancy of the speed of any received or detected light.
No. Once more: there are detectors where you like, even non-detected light is assumed to go at c, and such experiments as the one you describe have been done, both in theory and in practice. As a matter of fact, radar uses that same set-up. And the basic calculations are similar as with MMX.
if light reaches us at a constant speed, distance events will be seen at a later time than the time of the event determined locally (for an observer in close proximity and at rest relative to the event). Hence, if the observed time is delayed and distances are given, the observed speed must be smaller.
:bugeye: Do you think that the traffic police will observe speeding cars further away as going slower - or that GPS will tell that you are going slower as the satellite is further away??
 
Last edited:
  • #148
Peter, thanks for your patiance and effort. I'll make a couple observations regarding your reply.
You misinterpret my assertion that we can ditch the velocity of the light clock to mean that it is an unknown that must enter the equations nonetheless. No, I mean that we don't need it to solve at all. To determine the speed of the beam all the observer needs to know is the distance teavelled over the observed time - this will be the apparent velocity. Conversely, if you were given the relative velocity of the beam/projectilr from A to B (the vector addition of the upward speed of the projectile and the perpendicular speed of the projectile-clock) you could find the distance AB. Given the distance AB you can directly calculate the observed velocity as seen from A, just plot it over the observed time. You have to put yourself in the observer shoes and really imagine how he calculate the speed of the beam.
Since we are given the time of event B as measured by the clock itself, we can easily find the time that event is observed at a distance AB. Note this is the case for any scenario, we wouldn't need a beam traveling fron A to B at all. If the blinker at B simply turns on at t=1s (as measured with the blinker's own clock), you just have to consider the spatial separation from the event and the observer to get the observed time.

Assuming the event is caused by a beam going from A to B, he only has to plot the given distance over the observed time.

The mistake I keep pointing you to is the fact that you assumed the velocity of the clock enters the equations. But it would enter only if we were doing some kind if vector addition, but since the clock is going from A to D and the observer sees the event from B (at a time T), there's no reason to take that velocity into consideration, you are only looking for the time separation between events A and B to figure out at what speed something has to travel this distance to cause the observed times.

Later you state that T_AB = T_BA, but that is an assumption. The observer has to calculate T_AB from the observed time of event B, which is the local or proper time of event B plus the time it takes for that event to be seen at A. We know T_BA as seen from A from experiment, the speed of any directly detected light must be c. We don't know T_AB as seen from A because T_AB is only observed after T_BA, orherwise the observer doesn't see event B at all. T_AB must be calculated in this setup. Of course, if the observer at rest were to send a beam of light towards B, that would take the same time as a beam would need to come back from B to A. But notice the very important fact here that, if that was the case, the time of event B as seen from B would NOT be 1s (the time light takes to cross y'), but actually 1.12s (the time it would take for light to cross h').

Your last remark reassures me that you are assuming what you are trying to prove. The setup has no information on the beam, only on the events, which are good to calculate the speed of the beam in each frame.
 
  • #149
altergnostic said:
[..] To determine the speed of the beam all the observer needs to know is the distance teavelled over the observed time - this will be the apparent velocity. [...]
Just one more remark: you are mixing up reference systems, just as we already discovered - in fact you try to use t instead of t' for S'. That doesn't work. This will become clearer when you discuss MMX, which is the "mother" of all such calculations.
 
  • #150
altergnostic said:
You misinterpret my assertion that we can ditch the velocity of the light clock to mean that it is an unknown that must enter the equations nonetheless. No, I mean that we don't need it to solve at all. To determine the speed of the beam all the observer needs to know is the distance teavelled over the observed time - this will be the apparent velocity.

You are correct that you could set up the scenario so that the distances AB, AC, and BC were pre-determined; then you would have to control the speed of the light clock so that the beam actually hit the light clock's mirror at point B, instead of at some other point along the mirror's trajectory. That's fine, but it doesn't change anything about my analysis; my analysis is still correct, because even if you don't need the light clock's speed to do the analysis (which you actually do--see below--but for the moment I'll assume for the sake of argument that you don't), that is not the same as saying that an analysis which does use the light clock speed (even if it is left unknown) is incorrect.

altergnostic said:
Conversely, if you were given the relative velocity of the beam/projectilr from A to B (the vector addition of the upward speed of the projectile and the perpendicular speed of the projectile-clock) you could find the distance AB.

Yes, that's true, but you did not specify the upward speed of the projectile in the unprimed (observer) frame. You specified it in the primed (clock) frame. (Btw, I mis-stated this somewhat in my previous post; I said that you specified [itex]v_p[/itex], but I should have said that you specified [itex]v'_p[/itex]. I can go back and continue the analysis I was doing in my last post with that corrected, but it may not be worth bothering.)

So before you do this vector addition, you have to first transform the upward speed of the projectile from the primed to the unprimed frame. The upward distance (AB in the primed frame; BC in the unprimed frame, since the clock is moving in that frame) does not change when you change frames, but the *time* does, because of time dilation, so the upward speed of the projectile (i.e., the upward *component* of its velocity) is different in the unprimed frame than in the primed frame. So you do need to know the relative velocity of the light clock and the observer; without that you can't transform the upward velocity in the primed frame to the upward velocity component in the unprimed frame.

altergnostic said:
Given the distance AB you can directly calculate the observed velocity as seen from A, just plot it over the observed time. You have to put yourself in the observer shoes and really imagine how he calculate the speed of the beam.

Yes, let's do that. We have a light beam traveling from A to B, and a second light beam (the one that is emitted at the instant the first one strikes the mirror) traveling from B to A. The round-trip travel time is measured by the observer at A, and he already knows the distance AB because he measured it beforehand (and then controlled the speed of the light clock to ensure that the mirror was just passing B at the instant the first beam hit it). So we have two light beams each covering the same distance; if we assume that both beams travel at the same speed in the unprimed frame (even if we don't assume that that speed is c), then we can simply divide the round-trip time by the round-trip distance (2 * AB) to get the beam speed. Fine. See below for further comment.

altergnostic said:
Later you state that T_AB = T_BA, but that is an assumption.

Only in the sense that we assume that both light beams (the one from A to B and the one from B to A) travel at the same speed. Do you challenge that assumption? Both beams are "observed" in your sense--one endpoint of each beam is directly observed by the observer at A. It's impossible for *both* endpoints of either beam to be directly observed by the same observer, so if that's your criterion for a beam being "directly observed", then no beam is ever directly observed. But if you accept that *receiving* a beam counts as directly observing it, then *emitting* a beam should also count as directly observing it; either one gives the observer direct knowledge of one endpoint of the beam.

altergnostic said:
The observer has to calculate T_AB from the observed time of event B, which is the local or proper time of event B plus the time it takes for that event to be seen at A.

But how do we know the time it takes for that event to be seen at A? Are you assuming that the beam from B to A travels at c? If so, then why not also assume that the beam from A to B travels at c? What makes a received beam any different from an emitted beam?

By contrast, I am only assuming that the two beams (A to B and B to A) travel at the *same* speed, *without* assuming what that speed is (we *calculate* that by dividing round-trip distance by round-trip time, as above). That seems like a much more reasonable approach, since it does not require assuming that there is any difference between an emitted beam and a received beam.

altergnostic said:
We know T_BA as seen from A from experiment, the speed of any directly detected light must be c.

But only one endpoint of the light is directly detected. Why should received light count as directly detected but not emitted light?

altergnostic said:
We don't know T_AB as seen from A because T_AB is only observed after T_BA

No, they are both "observed" (by any reasonable definition of "observed") at the same time, when the beam from B to A is received and its time of reception is observed. At that point the observer knows the round-trip travel time and the round-trip distance and can calculate the beam speed.

altergnostic said:
T_AB must be calculated in this setup.

So must T_BA. The observer doesn't directly observe the emission of the beam from B to A, any more than he directly observes the reception of the beam from A to B. He has to calculate the times of both those events. The way he does that is to use the fact that both events occur at the same instant, by construction.

altergnostic said:
Of course, if the observer at rest were to send a beam of light towards B, that would take the same time as a beam would need to come back from B to A.

Unbelievable; you now *admit* this, yet you were arguing that we could *not* assume this before.

altergnostic said:
But notice the very important fact here that, if that was the case, the time of event B as seen from B would NOT be 1s (the time light takes to cross y'), but actually 1.12s (the time it would take for light to cross h').

Which it is; the time of event B, *in the unprimed frame*, *is* 1.12s (if we allow v, the velocity of the light clock relative to the observer, to be set appropriately to 0.45 instead of 0.5, per the comments of DaleSpam, harrylin, and myself). The time of event B, in the *primed* frame, is 1s; but that's not what the observer at A is interested in. He's interested in the time of event B in his frame, the unprimed frame, and that time is different from the time of event B in the primed frame because of time dilation. Which, of course, requires you to know the velocity of the light clock relative to the observer, contrary to your repeated erroneous claim that you don't.
 
  • #151
altergnostic said:
You misinterpret my assertion that we can ditch the velocity of the light clock to mean that it is an unknown that must enter the equations nonetheless. No, I mean that we don't need it to solve at all. To determine the speed of the beam all the observer needs to know is the distance teavelled over the observed time
No matter how you try to get rid of it, it is there anyway since both the distance traveled and the observed time depend on the speed of the clock.
 
  • #152
Giving 1.12 to the time it takes the beam to travel from A to B as seen from A is a mistake. That would only be true if the time of event B were also 1.12s. If you send a light beam from A to B, B would receive it at t'=1.12s. But, in the proposed setup, the time of this event in the clock's frame is t'=1s. Folliwung what has been stated in this thread, the time of event B can be either 1s or 1.12s as seen from the clock's frame and in both cases the speed of the beam as seen from A would be c, but this is only possible if light crosses the distance h' (the hypotenuse) as seen in the clock's frame in one case and the distance y' in the other case, but it is clear that in this setup the beam crosses y' in the clock's frame.

I really don't know how else to state this, but as a last resort, I will ask you to ignore the beam completely and just analyse the events as seen from A, when x is in line with AB, as if no beam was causing the events at all:
A0 = A'0 = 0,0,0
B1 = B'1+X = 2.12,1.12,0
While B happens at t'=1s as recorded from B itself.

What would be the presumed speed an object would need, as seen from A, to travel from event A0 to B1, if it was to leave A at t=0s and reach B at the time of event B (TB1 = 2.12s)?

TB1 = 2.12
X = 1.12
VAB = X/TB1 = 0.528

The observer can subtract the delay caused from BA (the time light takes to travel from B to A) to find the time of the event as measured by a clock placed at B:

T'B = TB - TBA = 2.12 - 1.12 = 1s

If you calculate the speed of the beam straight from the times of events and the given distances, that's what you would find, and as the observer standing at A only has access to the events themselves, that's how he would calculate it.

We can only disagree on two points, I think:

1: The given distance is not correct or useful or consistent with SR

2: The observed time for B1 as seen from A is not the local or proper time of the event plus the time separation between A and B.

Regarding 1, I remind you that any given V implies a given L, which L I'm giving as the distance from A to B (or B to A) measured locally - a proper distance? I don't see why wouldn't we be allowed to be given this length if we are given a relative V in other situations.

Regarding 2, I can't see how this isn't the case. The only argument against this is that the primed time is not 1s but 1.12s, which is inconsistent with the light clock's own measurements.

This thread is way too long already and I think that if we haven't reached an agreement yet, we won't reach it anytime. Maybe there's an experiment out there that actually determines the speed of an undetected (or indirectly detected) light beam so we could check this, but I believe that this hasn't been done at all. Every experiment built to determine the speed of light that I know about works by measuring the return time or some other setup that relies o direct detection or emission. I repeat that the observer at A is not the source nor the receiver of the beam. The source is the bottom mirror and the receiver is the top mirror. The observer at A is the receiver of the signal traveling at c from B1 to A0. The mirror at B is the receiver of the beam traveling at c from A'0 to B'1 (which equals CB).

The postulate of the constancy of the speed if light necessarily applies to those light paths.
 
  • #153
altergnostic said:
Giving 1.12 to the time it takes the beam to travel from A to B as seen from A is a mistake. That would only be true if the time of event B were also 1.12s. If you send a light beam from A to B, B would receive it at t'=1.12s. But, in the proposed setup, the time of this event in the clock's frame is t'=1s.

You keep on mixing up quantities in different frames. When we say that the "time" for the beam to travel from A to B is 1.12s, we mean in the unprimed frame; i.e., t = 1.12s. That is perfectly consistent with that time being 1s in the primed frame; i.e., t' = 1s.

PAllen said:
Folliwung what has been stated in this thread, the time of event B can be either 1s or 1.12s as seen from the clock's frame

No, it can't. Where are you getting that from? The time of event B (event B1 in my nomenclature) is 1.12s in the unprimed frame (observer's frame), and 1s in the primed frame (clock frame). No one has said that the time of event B1 is 1.12s in the primed frame.

PAllen said:
analyse the events as seen from A, when x is in line with AB, as if no beam was causing the events at all:
A0 = A'0 = 0,0,0
B1 = B'1+X = 2.12,1.12,0
While B happens at t'=1s as recorded from B itself.

What does "recorded from B itself" mean? Who is doing the recording? If the observer at B doing the recording is at rest relative to the observer at A, then he will record t = 1.12s. To record t' = 1s, he would need to be moving with the light clock, i.e., at an angle to the x-axis with the orientation of axes you are using. That means such an observer is not "at B" except at the instant when he records the arrival of the light beam there.

Also, I don't understand your coordinate values. Is the first number supposed to be time? If so, where does 2.12 come from?

I can't even make sense of the rest of your analysis, because I don't understand where you're getting the initial numbers it's based on.

PAllen said:
I repeat that the observer at A is not the source nor the receiver of the beam. The source is the bottom mirror and the receiver is the top mirror.

But the observer at A is co-located with the bottom mirror when it emits the light beam, so he can directly observe its time of emission by any reasonable definition of "directly observe". By your extremely strict definition of "directly observe", practically no events are ever directly observed.

PAllen said:
The observer at A is the receiver of the signal traveling at c from B1 to A0. The mirror at B is the receiver of the beam traveling at c from A'0 to B'1 (which equals CB).

The postulate of the constancy of the speed if light necessarily applies to those light paths.

And that, all by itself, is enough to show that *all* the other light beams in your scenario also move at c. That was one of the points of my various posts analyzing the scenario. But I think you are right that, if we haven't reached agreement on that point by now, we're not likely to.
 
  • #154
PeterDonis said:
Yes, that's true, but you did not specify the upward speed of the projectile in the unprimed (observer) frame. You specified it in the primed (clock) frame. (Btw, I mis-stated this somewhat in my previous post; I said that you specified [itex]v_p[/itex], but I should have said that you specified [itex]v'_p[/itex]. I can go back and continue the analysis I was doing in my last post with that corrected, but it may not be worth bothering.)

No problem, that was an honest mistake. Don't bother correcting it.
And I didn't give the upward velocity in the unprimed frame because the goal is to find the speed of the beam in the first place. And we can find it since I gave the distances and times you need to do so.

So before you do this vector addition, you have to first transform the upward speed of the projectile from the primed to the unprimed frame.

You don't need to do this at all, since we are calculating speeds from given distances and times, not from different speed vectors.

The upward distance (AB in the primed frame; BC in the unprimed frame, since the clock is moving in that frame) does not change when you change frames, but the *time* does, because of time dilation

Once again, the distance does change between frames. The distance marks are clear and visible for both frames. From the clock's measurements, AB = CB = y'. For the distant observer, event B1 occurs h' lightseconds away from A. This is direct visual data. Also, time dilation effects in this setup occur because of the constant speed of the signal from B to A, not the speed of the beam - and that is the unknown we are seeking.


so the upward speed of the projectile (i.e., the upward *component* of its velocity) is different in the unprimed frame than in the primed frame. So you do need to know the relative velocity of the light clock and the observer; without that you can't transform the upward velocity in the primed frame to the upward velocity component in the unprimed frame.

But you don't have to transform upward components to find the observed speed of the beam! All you have to do is plot the given distance over the observed time, and since we know the time of the event B as seen from the light clock's frame, we can add the time the signal takes to reach A from B to find the observed time of event B as seen from A. You don't need to separate the motion into vector components at all, you have the time and distance of the event at B, you can calculate the observed speed straight from that.



Yes, let's do that. We have a light beam traveling from A to B, and a second light beam (the one that is emitted at the instant the first one strikes the mirror) traveling from B to A. The round-trip travel time is measured by the observer at A, and he already knows the distance AB because he measured it beforehand (and then controlled the speed of the light clock to ensure that the mirror was just passing B at the instant the first beam hit it). So we have two light beams each covering the same distance; if we assume that both beams travel at the same speed in the unprimed frame (even if we don't assume that that speed is c), then we can simply divide the round-trip time by the round-trip distance (2 * AB) to get the beam speed. Fine. See below for further comment.

But you can't assume both beams travel at the same speed! That's the point of the setup. You have to SHOW that. Otherwise you are assuming what you are trying to prove. If you are at rest in A relative to B and send a beam towards B, it will take 1.12s to get there, but if you are at A moving along with a mirror 1 ls away and send a beam towards the mirror, it takes 1s to reach it, even if it is coincidentally at B.
The bottom line is that the time of event B in the primed frame is 1 and that same event is observed at A when light from that event reaches A, after crossing BA. If the event at B = 1s was self generated (if it wasn't the outcome of any reflection event, like manually turning on a flash of light),
how would you find the observed time for event B as seen from A?


Only in the sense that we assume that both light beams (the one from A to B and the one from B to A) travel at the same speed. Do you challenge that assumption? Both beams are "observed" in your sense--one endpoint of each beam is directly observed by the observer at A. It's impossible for *both* endpoints of either beam to be directly observed by the same observer, so if that's your criterion for a beam being "directly observed", then no beam is ever directly observed. But if you accept that *receiving* a beam counts as directly observing it, then *emitting* a beam should also count as directly observing it; either one gives the observer direct knowledge of one endpoint of the beam.
You can't calculate the speed of light from the time of emission, you need a distance, a time of emission and a time of reception. The reception is the observation, not the emission. And although emission gives you knowledge of the coordinates of one endpoint of a beam (since you can determine the place and time of emission as you please), it is far from enough to determine any speed, any distance traveled and any timr of travel, so we absolutely need the reception coordinates.

You see, the observer moving along with the bottom mirror in the clock only knows T'B because it is half the return time (T'D), so you need both the coordinates of emission and reception to determine anything. Now, the observer at A only knows the emission coordinates for the beam (0,0,0). The next piece of information he receives is the light coming from *event B, from which he must calculate the coordinates of reception!


But how do we know the time it takes for that event to be seen at A? Are you assuming that the beam from B to A travels at c?
Yes!

If so, then why not also assume that the beam from A to B travels at c? What makes a received beam any different from an emitted beam?
Finally the fundamental question!
What makes it different is the operation. When we determine the speed if light, we take the distance from the emitter over the time of detection, which is measured locally relative to the point of detection. We are always at rest relative to the point of detection (this is also true for emission). But the detector at B is in relative motion wrt the observer at A, so he is not ar rest relative to the point of detection. This is the fundamental reason, I think, that the speeds are not the same. If you are teavelling along with the clock, you are at rest relative to the point of detection and of emission, so light is always going at c, since all motion is given to the light. If the detector is in relative motion, you are not at rest relative to the point of detection, so you can't give all motion to light. Does this make any sense? Do you ser how this does not violate the light postulate? Light is constant relative to source or detector, but the observer at A is neither source nor detector of the beam going from A to B - the source is the bottom mirror and the detector is the top mirror, and they are both moving relative to A.

By contrast, I am only assuming that the two beams (A to B and B to A) travel at the *same* speed, *without* assuming what that speed is (we *calculate* that by dividing round-trip distance by round-trip time, as above). That seems like a much more reasonable approach, since it does not require assuming that there is any difference between an emitted beam and a received beam.

Assuming the speed is the same as seen from A is the problem. You can't make that assumption. You can assume the speed from A to B as seen fron B is the same as the speed from B to A as seen from A, though, but this is not what the setup demands.



But only one endpoint of the light is directly detected. Why should received light count as directly detected but not emitted light?

See above.



No, they are both "observed" (by any reasonable definition of "observed") at the same time, when the beam from B to A is received and its time of reception is observed. At that point the observer knows the round-trip travel time and the round-trip distance and can calculate the beam speed.
That is what I meant. I just point out that the roundtrip can't be split in half to determine any speed here. Theory and experiment clearly shows that the speed from B to A must be c, the rest must be given to AB.


So must T_BA. The observer doesn't directly observe the emission of the beam from B to A, any more than he directly observes the reception of the beam from A to B. He has to calculate the times of both those events. The way he does that is to use the fact that both events occur at the same instant, by construction.

Correct, but he knows the distance AB and he knows that directly observed light must travel at c. T_BA is simply AB/c. This is where the postulate of SR makes the problem possible to solve.



PeterDonis said:
Yes, that's true, but you did not specify the upward speed of the projectile in the unprimed (observer) frame. You specified it in the primed (clock) frame. (Btw, I mis-stated this somewhat in my previous post; I said that you specified [itex]v_p[/itex], but I should have said that you specified [itex]v'_p[/itex]. I can go back and continue the analysis I was doing in my last post with that corrected, but it may not be worth bothering.)

No problem, that was an honest mistake. Don't bother correcting it.
And I didn't give the upward velocity in the unprimed frame because the goal is to find the speed of the beam in the first place. And we can find it since I gave the distances and times you need to do so.

So before you do this vector addition, you have to first transform the upward speed of the projectile from the primed to the unprimed frame.

You don't need to do this at all, since we are calculating speeds from given distances and times, not from different speed vectors.

The upward distance (AB in the primed frame; BC in the unprimed frame, since the clock is moving in that frame) does not change when you change frames, but the *time* does, because of time dilation

Once again, the distance does change between frames. The distance marks are clear and visible for both frames. From the clock's measurements, AB = CB = y'. For the distant observer, event B1 occurs h' lightseconds away from A. This is direct visual data. Also, time dilation effects in this setup occur because of the constant speed of the signal from B to A, not the speed of the beam - and that is the unknown we are seeking.


so the upward speed of the projectile (i.e., the upward *component* of its velocity) is different in the unprimed frame than in the primed frame. So you do need to know the relative velocity of the light clock and the observer; without that you can't transform the upward velocity in the primed frame to the upward velocity component in the unprimed frame.

But you don't have to transform upward components to find the observed speed of the beam! All you have to do is plot the given distance over the observed time, and since we know the time of the event B as seen from the light clock's frame, we can add the time the signal takes to reach A from B to find the observed time of event B as seen from A. You don't need to separate the motion into vector components at all, you have the time and distance of the event at B, you can calculate the observed speed straight from that.



Yes, let's do that. We have a light beam traveling from A to B, and a second light beam (the one that is emitted at the instant the first one strikes the mirror) traveling from B to A. The round-trip travel time is measured by the observer at A, and he already knows the distance AB because he measured it beforehand (and then controlled the speed of the light clock to ensure that the mirror was just passing B at the instant the first beam hit it). So we have two light beams each covering the same distance; if we assume that both beams travel at the same speed in the unprimed frame (even if we don't assume that that speed is c), then we can simply divide the round-trip time by the round-trip distance (2 * AB) to get the beam speed. Fine. See below for further comment.

But you can't assume both beams travel at the same speed! That's the point of the setup. You have to SHOW that. Otherwise you are assuming what you are trying to prove. If you are at rest in A relative to B and send a beam towards B, it will take 1.12s to get there, but if you are at A moving along with a mirror 1 ls away and send a beam towards the mirror, it takes 1s to reach it, even if it is coincidentally at B.
The bottom line is that the time of event B in the primed frame is 1 and that same event is observed at A when light from that event reaches A, after crossing BA. If the event at B = 1s was self generated (if it wasn't the outcome of any reflection event, like manually turning on a flash of light),
how would you find the observed time for event B as seen from A?


Only in the sense that we assume that both light beams (the one from A to B and the one from B to A) travel at the same speed. Do you challenge that assumption? Both beams are "observed" in your sense--one endpoint of each beam is directly observed by the observer at A. It's impossible for *both* endpoints of either beam to be directly observed by the same observer, so if that's your criterion for a beam being "directly observed", then no beam is ever directly observed. But if you accept that *receiving* a beam counts as directly observing it, then *emitting* a beam should also count as directly observing it; either one gives the observer direct knowledge of one endpoint of the beam.
You can't calculate the speed of light from the time of emission, you need a distance, a time of emission and a time of reception. The reception is the observation, not the emission. And although emission gives you knowledge of the coordinates of one endpoint of a beam (since you can determine the place and time of emission as you please), it is far from enough to determine any speed, any distance traveled and any timr of travel, so we absolutely need the reception coordinates.

You see, the observer moving along with the bottom mirror in the clock only knows T'B because it is half the return time (T'D), so you need both the coordinates of emission and reception to determine anything. Now, the observer at A only knows the emission coordinates for the beam (0,0,0). The next piece of information he receives is the light coming from *event B, from which he must calculate the coordinates of reception!


But how do we know the time it takes for that event to be seen at A? Are you assuming that the beam from B to A travels at c?
Yes!

If so, then why not also assume that the beam from A to B travels at c? What makes a received beam any different from an emitted beam?
Finally the fundamental question!
What makes it different is the operation. When we determine the speed if light, we take the distance from the emitter over the time of detection, which is measured locally relative to the point of detection. We are always at rest relative to the point of detection (this is also true for emission). But the detector at B is in relative motion wrt the observer at A, so he is not ar rest relative to the point of detection. This is the fundamental reason, I think, that the speeds are not the same. If you are teavelling along with the clock, you are at rest relative to the point of detection and of emission, so light is always going at c, since all motion is given to the light. If the detector is in relative motion, you are not at rest relative to the point of detection, so you can't give all motion to light. Does this make any sense? Do you ser how this does not violate the light postulate? Light is constant relative to source or detector, but the observer at A is neither source nor detector of the beam going from A to B - the source is the bottom mirror and the detector is the top mirror, and they are both moving relative to A.

By contrast, I am only assuming that the two beams (A to B and B to A) travel at the *same* speed, *without* assuming what that speed is (we *calculate* that by dividing round-trip distance by round-trip time, as above). That seems like a much more reasonable approach, since it does not require assuming that there is any difference between an emitted beam and a received beam.

Assuming the speed is the same as seen from A is the problem. You can't make that assumption. You can assume the speed from A to B as seen fron B is the same as the speed from B to A as seen from A, though, but this is not what the setup demands.



But only one endpoint of the light is directly detected. Why should received light count as directly detected but not emitted light?

See above.



No, they are both "observed" (by any reasonable definition of "observed") at the same time, when the beam from B to A is received and its time of reception is observed. At that point the observer knows the round-trip travel time and the round-trip distance and can calculate the beam speed.
That is what I meant. I just point out that the roundtrip can't be split in half to determine any speed here. Theory and experiment clearly shows that the speed from B to A must be c, the rest must be given to AB.


So must T_BA. The observer doesn't directly observe the emission of the beam from B to A, any more than he directly observes the reception of the beam from A to B. He has to calculate the times of both those events. The way he does that is to use the fact that both events occur at the same instant, by construction.

But he knows the distance AB and he knows that directly observed light must travel at c. T_BA is simply*

Unbelievable; you now *admit* this, yet you were arguing that we could *not* assume this before.
This applies if the observer and the point B are at rest wrt each other.
See above.

Which it is; the time of event B, *in the unprimed frame*, *is* 1.12s (if we allow v, the velocity of the light clock relative to the observer, to be set appropriately to 0.45 instead of 0.5, per the comments of DaleSpam, harrylin, and myself). The time of event B, in the *primed* frame, is 1s; but that's not what the observer at A is interested in. He's interested in the time of event B in his frame, the unprimed frame, and that time is different from the time of event B in the primed frame because of time dilation. Which, of course, requires you to know the velocity of the light clock relative to the observer, contrary to your repeated erroneous claim that you don't.

I think I have answered this above, but just for good measure, notice I said it must be 1s as seen from B, which would be in the primed frame. But we know that the mirror at B must detect the beam at T=1s measuring from its internal clock, and si the event B must be seen by the observer at A at T=T'AB+TBA.
Notice that T'AB = CB and TAB is not even measurable from A. TAB is strictly a measurement made in the clock's frame, or more precisely, in the top mirror's frame, since this detection only happens there. The observer at A detects the signal from B to A, and from the given distance and the light speed postulate, he can subtract the time it took light to reach him from event B and find the time of the event in the primed frame. The times are different indeed, but I don't know if I should call the reason "time dilation".
Anyway, I'll wait for your follow-up.
 
  • #155
altergnostic said:
Giving 1.12 to the time it takes the beam to travel from A to B as seen from A is a mistake. That would only be true if the time of event B were also 1.12s. If you send a light beam from A to B, B would receive it at t'=1.12s.
You are mixing up quantities in different frames. B receives it at t=1.12 (wrt the frame where the clock is moving). B receives it at t'=1 (wrt the frame where the clock is stationary). That is the whole point of the exercise.
altergnostic said:
This thread is way too long already and I think that if we haven't reached an agreement yet, we won't reach it anytime.
Yes, that is true. However, since the universe disagrees with your position, I will stick with mine for now. I would rather disagree with you than disagree with the universe.
 
  • #156
altergnostic said:
Once again, the distance does change between frames.

Only distances parallel to the relative motion are affected by length contraction. The distance A'B' (in the primed frame) and CB (in the unprimed frame) are perpendicular to the relative motion, so they don't change, and A'B' = CB by the geometry of the problem.

altergnostic said:
The distance marks are clear and visible for both frames. From the clock's measurements, AB = CB = y'.

You don't measure distance directly from clock measurements. You have to have a speed. You are basically allowing the speed of light beams to be c when you want it to be, but insisting that the speed of other light beams is not c when you don't want it to be.

Also, shouldn't this be A'B' = CB? If both of these distances are in the unprimed frame, they are *not* equal; they can't be, because AB is the hypotenuse of a right triangle and CB is one of its legs. I don't understand what you're doing here.

altergnostic said:
For the distant observer, event B1 occurs h' lightseconds away from A. This is direct visual data.

Huh? Who is the "distant observer"? Is he located at B and at rest relative to the observer at A (i.e,. at rest in the unprimed frame)? If so, why are you assigning a distance in the primed frame to what he observes?

altergnostic said:
Also, time dilation effects in this setup occur because of the constant speed of the signal from B to A

Time dilation is not a "travel time delay" effect. It is what is left over *after* you have subtracted out all effects from signal travel time delay.

altergnostic said:
since we know the time of the event B as seen from the light clock's frame, we can add the time the signal takes to reach A from B to find the observed time of event B as seen from A.

You can't add times in different frames and get a meaningful answer. How many times does this need to be repeated?

altergnostic said:
You don't need to separate the motion into vector components at all, you have the time and distance of the event at B, you can calculate the observed speed straight from that.

In the primed frame, yes. In the unprimed frame, no.

altergnostic said:
But you can't assume both beams travel at the same speed! That's the point of the setup. You have to SHOW that. Otherwise you are assuming what you are trying to prove.

This really gets to the issue of what counts as a "directly observed" light beam, since you agree that any directly observed beam does travel at c. I claim that both beams in this case are directly observed; but you want to say that only one is. See below for further comment.

altergnostic said:
If you are at rest in A relative to B and send a beam towards B, it will take 1.12s to get there, but if you are at A moving along with a mirror 1 ls away and send a beam towards the mirror, it takes 1s to reach it, even if it is coincidentally at B.

Unbelievable. Now you *agree* that T_AB (in the unprimed frame) is 1.12s, and T'_AB (in the primed frame) is 1s. But you were arguing before that this is *not* true. Do you read your own posts?

altergnostic said:
The bottom line is that the time of event B in the primed frame is 1 and that same event is observed at A when light from that event reaches A, after crossing BA. If the event at B = 1s was self generated (if it wasn't the outcome of any reflection event, like manually turning on a flash of light),
how would you find the observed time for event B as seen from A?

*I* would find the observed time for event B as seen from A using the standard SR formulas, which I have already done several times in this thread. You don't appear to like that method, so let's try this one: the beam from B to A is directly detected by A; therefore its speed should be c, as seen by A, according to your own claim that any "directly detected" light beam travels at c. A also knows the distance from B to A; it is 1.12 light seconds (for the numbers we are currently using). Therefore the time of event B, according to A, is 1.12s before the time he receives the light beam.

As far as I can tell, you agree with the above; but then you want to go on and claim that, if A starts his clock at zero when the first light beam (from A to B) is *emitted*, he will receive the second light beam (from B to A) at t = 2.12s, because the first light beam will take 1s to travel, *according to A*. But that beam also covers 1.12 light seconds of distance, according to A, so it covers 1.12 light seconds in 1 second, according to A; so you are claiming that light can travel faster than light. Is this what you're claiming?

altergnostic said:
You can't calculate the speed of light from the time of emission, you need a distance, a time of emission and a time of reception. The reception is the observation, not the emission.

In other words, you are claiming that it is impossible to directly observe the emission of light?

altergnostic said:
And although emission gives you knowledge of the coordinates of one endpoint of a beam (since you can determine the place and time of emission as you please), it is far from enough to determine any speed, any distance traveled and any timr of travel, so we absolutely need the reception coordinates.

The same would be true if we only had the reception coordinates, wouldn't it? We would need *both* sets of coordinates, in the *same* frame, to calculate the speed, right? Oh, wait:

altergnostic said:
You see, the observer moving along with the bottom mirror in the clock only knows T'B because it is half the return time (T'D), so you need both the coordinates of emission and reception to determine anything.

And yet you are claiming that the observer at A somehow "directly knows" that the beam he receives from B took 1.12s to get to him, even though he doesn't know the coordinates of emission. In other words, again you are picking and choosing when you can assume light travels at c and when you can't; but yet you also claim that you can't calculate a speed at all unless you know both the emission *and* the reception coordinates. You seem to me to be contradicting yourself.

altergnostic said:
Now, the observer at A only knows the emission coordinates for the beam (0,0,0). The next piece of information he receives is the light coming from *event B, from which he must calculate the coordinates of reception!

But you did not state what the coordinates of event A2 (the event where the observer at A receives the light signal from B) were; you have claimed to calculate them by adding 1s to 1.12s. You need to justify this calculation. Alternately, if you change your ground and claim that T_A2 = 2.12s is part of your statement of the problem, you need to show how that is consistent with the other givens. You haven't done any of that. Again, you're picking and choosing numbers to suit your claims, without backing them up.

altergnostic said:
What makes it different is the operation. When we determine the speed if light, we take the distance from the emitter over the time of detection, which is measured locally relative to the point of detection.

What does "measured locally relative to the point of detection" mean?

altergnostic said:
We are always at rest relative to the point of detection (this is also true for emission).

Then why is emission treated differently from detection?

altergnostic said:
But the detector at B is in relative motion wrt the observer at A, so he is not ar rest relative to the point of detection. This is the fundamental reason, I think, that the speeds are not the same. If you are teavelling along with the clock, you are at rest relative to the point of detection and of emission, so light is always going at c, since all motion is given to the light. If the detector is in relative motion, you are not at rest relative to the point of detection, so you can't give all motion to light. Does this make any sense?

For a "projectile" moving slower than light, yes; it amounts to saying that the observed speed of the projectile depends on your motion relative to its source.

For light, no; the speed of light is independent of the motion of the source. That is what the null result for the Michelson-Morley experiment means; and that experiment has been repeated with greater and greater accuracy, and the null result continues to hold.

If you ran a "Michelson-Morley experiment" using slower-than-light projectiles in the apparatus instead of light, you would *not* get a null result; you would observe different speeds for the two projectiles (moving on perpendicular trajectories) if you were in motion relative to the apparatus.

altergnostic said:
I just point out that the roundtrip can't be split in half to determine any speed here. Theory and experiment clearly shows that the speed from B to A must be c, the rest must be given to AB.

But you have to determine what "the rest" is, and you are trying to do it by mixing numbers from different frames.

altergnostic said:
I think I have answered this above, but just for good measure, notice I said it must be 1s as seen from B, which would be in the primed frame.

Yes.

altergnostic said:
But we know that the mirror at B must detect the beam at T=1s measuring from its internal clock, and si the event B must be seen by the observer at A at T=T'AB+TBA.

No; you're adding numbers from different frames, which is meaningless. What you should be doing is T=T_AB + T_BA = gamma (T'_AB) + T_BA, where gamma is the gamma factor corresponding to the light clock velocity relative to the observer.

altergnostic said:
Notice that T'AB = CB and TAB is not even measurable from A. TAB is strictly a measurement made in the clock's frame, or more precisely, in the top mirror's frame, since this detection only happens there.

This applies to T'_AB, but *not* to T_AB; the mirror can't "directly measure" a time in the unprimed frame, only in the primed frame.

altergnostic said:
The times are different indeed, but I don't know if I should call the reason "time dilation".

Time dilation *is* the reason that T'_AB does not equal T_AB; it *is* the reason why I wrote T_AB = gamma (T'_AB) above. Working things out from the geometry of the problem that you gave shows that gamma (T'_AB) = T_AB = T_BA, which means that both light beams (A to B and B to A) travel at c as seen from the unprimed frame. We already know that the beam from A to B travels at c as seen from the primed frame; we then have to calculate the coordinates of event A2 (where the beam from B to A is received by A) in the primed frame to show that the beam from B to A travels at c as seen from the primed frame.

Having said all that, I want to go back to your original claim. Your original claim is different from what you appear to be claiming now. Your original claim was that the standard SR picture of the light clock is inconsistent. I have now produced several analyses that show that the standard SR picture *is* consistent.

Now you have shifted your ground, and you are saying that the standard SR picture makes unwarranted assumptions (that the speed of all light beams is c, not just directly detected ones). I have also shown that the assumptions aren't what you are claiming they are (they are things like translation and rotation invariance; things like the speed of all light beams being c are *derived* claims, not fundamental assumptions, if you start with the assumption of translation and rotation invariance). But regardless of the assumptions, the fact is that SR matches experiments, as DaleSpam pointed out. Your claims, such as the light beam from A to B taking only 1s (in the unprimed frame) to travel 1.12 light seconds (in the unprimed frame), do *not* match experiments; if we actually ran a light clock experiment in which the distance from A to B, in the unprimed frame, was 1.12 light seconds, we would *not* get the timing results you have claimed; we would get the results I derived using the standard SR formulas.

So I'm not sure where you are going with this thread. Your original claim has been shown to be wrong; the standard SR model of a light clock is consistent. Your claims about the event coordinates are wrong, because they don't match the standard SR model, which agrees with experiment. What now?
 
  • #157
altergnostic, several people have repeated the claim that the experimental evidence supports SR. In fact, if you are uncomfortable with the light-speed postulate of SR then you could easily NOT assume it, make a general theory of all possible transformations between inertial frames, and use experimental data to set the parameters in such a general theory.

In Robertsons famous paper he did exactly that and demonstrated that SR could be deduced to within about 0.1% from the Michelson Morely, Ives Stillwell, and Kennedy Thorndike experiments even without making Einstein's assumptions. See: http://rmp.aps.org/abstract/RMP/v21/i3/p378_1

I strongly recommend that you read that paper as well as the wealth of experimental evidence listed here:
https://www.physicsforums.com/showthread.php?t=229034
 
  • #158
I hold my claim that the standard light clock diagram is inconsistent.

If I understand every claim correctly, the basic disagreement is that, if the distance AB is 1.12ls, then light should take 1.12s to travel that distance regardless of direction, which is basically saying that the speed of light is c regardless of the speed of the source. What seems hard to grasp is that I am not advocating against this assumption.

It has been said that if I simply do the MM interferometer analysis I will have solved this setup without any contradiction. I disagree.

It has also been said that the speed from A to B has been calculated repeatedly in this thread, but I disagree, and in many places it has been admitted that that speed was assumed based on the distance AB (not calculated), but the purpose of my setup is precisely to have the necessary givens so we can calculate that speed and check that assumption.

Another argument is that I am mixing frames by adding primed and unprimed times and that that is not allowed. Although that is generally true, sometimes it is allowed. Of course we can't mix variables that are being measured, but we can add a given with an observation. We are simply taking the proper time of an event and taking into account how long it takes for that event to be seen at another point AB away. If the time (as shown on a clock at B) of an event at B is 0s and light takes 1.12s to get to A, than the observed time for that event as seen from A is 1.12s. Likewise, if the time of the event is 1s at B, the observed time will be 2.12s. That is all I am saying.

It has been said that B receives the beam at 1.12s in the observer at A's frame, and 1s in the clock's frame (or the frame of the mirror at B). But that last is a given, and the former is an assumption.

If we have an observer at B, at t'=1s the beam appears to come from the stationary mirror at C. At t=1s, B sees the light of the beam on the mirror at C, 1 light-second away.
The path of detected light in the primed frame is CB. But from the point of view of the observer at A, it is the signal, not the beam, that comes from B, 1.12 light-seconds away. The path of the detected light in the unprimed frame is BA. This is what is observed.

The speed of whatever is describing AB, so far, is unknown, as a matter of observations. The question is if the observer at A can assume that the time the beam takes to go from A to B is 1.12s based on his observations. And what are his observations?
He knows the distance AB and the time light takes to reach him from any event at the point B. He receives a direct signal from B, but what is the observed time of the event at B? In a real experiment, we would find that number directly, but here we have to use logic to determine it. I say that, from A, the observed time time of event B is simply the time light takes to cross from B to A (tBA) + the proper time of emission:

tB = tBA + t'B
or
t'B = tB – tBA
which is
t' = t – ct
which is simply a way to find the time on a distant synchronized clock:
t'B = 0.5(tA1 + tA2)
t'B = 0.5(0 + 2.24) = 1.12s
Hence every event at B will be observed 1.12s later at A:
t' = t – AB
and if the reflection event at the point B occurs at t'=1s, then it will be observed in A at:
1 = t – 1.12
t = 2.12s

So I hope you see there is no frame mixing. We are not adding quantities that are being measured in different frames. t'B is not (only) being measured in the primed frame, but it is the time of the clock at B given by the standard synchronization method.

The observer at A can only conclude that the time of the detection at B is 1s, not 1.12s. Please note that event B is observed at A when t=2.12s and that the beam is reflected from the mirror at B when t=1s. This method applies to anything traveling at any speed between the mirrors (or to nothing traveling at all) because it is related only to the observation of events, regardless of the cause of these events.

For an observer at B:
V'beam = tCB = c
For an observer at A:
Vsignal = tBA = c
and
apparent Vbeam = AB/(tB – tA) = 1.12/2.12 = 0.528c

Now, he knows that the time of detection at B is not 2.12s, but 1s, so he could try to calculate the speed of the beam like this:
calculated Vbeam = AB/(t'B - t'A) = 1.12/1 = 1.12c

But that is a mixing of frames after all. We are no longer using given instants in time of events or observations, but elapsed periods between events, and a period is a measurement, and that measurement does not belong to the observer A - he has transformed an observed period into a directly detected period, or the period as measured by A into the period as measured by B - but hasn't transformed the distance. Therefore, AB no longer applies, since he has to use the distance as observed by B also. That distance can be easily found either by directly using the given primed distance (CB or y' or 1ls) or by turning back to the light postulate and finding the distance from the primed time:
x' = ct'
x' = 1 = y'
So everything's double checked.

If at point B there was a clock and a camera, the signal from B to A could carry a photograph of the clock at B and its surroundings and the observer at A would receive direct visual information showing the clock at B marking t'=1s and the mirror reflecting off the beam, and everything would be triple checked.

Now, concerning the interferometer, the path AB is not observed nor calculated like in our setup at all. AB was assumed to be the path described by the beam in the ether frame, where light travels at c. It is the path of the beam as seen from an absolute frame. But of course, from the interferometer's point of view, light always reaches the detector directly, like I have been saying. The beam's speed is not being determined by distant events, but by local detections. If our setup was equivalent to the interferometer's, the detected beam would describe CBC and we would have no evidence of path AB at all (just like Michelson and Morley didn't), since we wouldn't be able to determine relative motion. And if we wanted to, we would have to place an observer in a moving frame, just like we are doing here, and we fall back to my analysis.

We can't simply assume that path AB is being described by the beam at c as seen by the observer at A because, unlike the ether, he is not present everywhere and must directly receive incoming light to determine any coordinates. Received light is always measured to travel at c, which was thought to imply an absolute ether, but it sounds much more Einsteinian to specify c as the speed of light as measured by any observer (i.e.: by direct detection). Einstein's original claim, that the speed of light is the same regardless of the speed of the source, sounds perfect to me, and I think it is absurd to conclude that the postulate applies to the speed of undetected or indirectly detected light, since Einstein never even tried to describe it that way. He actually required that we place observers everywhere, so that light going in any arbitrary direction was actually directly detected, and it is to that light that we assign c.

Objects and events are seen with light and it is with this light that we determine their velocities. If a beam traveling in an arbitrary direction is to be observed with light bouncing off of it (just like an ordinary object) and not directly detected as usual, it is not your standard light anymore, it is the v in v/c, since only the incoming light is that c - it is being detected, not being measured. That c in the denominator is the tool with which we measure other things, and the tool with which we are measuring the speed of the beam from A to B. And we can't have c/c. The denominator is the light with which we see and the numerator is the speed of what we are seeing with that light.

The last thing that I think may need clarification is why I ignore the speed of the light clock in my setup. If we are given that number, we will tend to solve like it is always done and not really think the whole problem through. My givens are analogous to a given velocity, since we have fixed times and distances, but I require that the observer's frame is aligned with the frame of the source at B and that both frame's x-axis are in line with AB, since that is the easiest way to find unknowns for AB (we can simply ignore y and z and use the coordinates of each event to find AB).
I am simply requiring B's frame of reference to be obtained from A's frame by a standard Lorentz transformation.

I hope I made it clear how this setup differs from the assumptions and calculations of the standard light-clock and MM diagrams.
 
  • #159
altergnostic said:
which is basically saying that the speed of light is c regardless of the speed of the source. What seems hard to grasp is that I am not advocating against this assumption.

Oh, really? You mean I can freely use that assumption when analyzing any of these scenarios? Great! That makes things a *lot* simpler. :smile:

altergnostic said:
We are simply taking the proper time of an event and taking into account how long it takes for that event to be seen at another point AB away.

The proper time of the event only matches coordinate time in one particular frame, so you still can't add it to a coordinate time in some other frame and expect to get a meaningful answer.

altergnostic said:
If the time (as shown on a clock at B) of an event at B is 0s and light takes 1.12s to get to A, than the observed time for that event as seen from A is 1.12s.

Only if the clock at B and the clock at A are mutually at rest and synchronized. But the "clock at B" that you have been referring to is moving relative to the observer at A.

altergnostic said:
Likewise, if the time of the event is 1s at B, the observed time will be 2.12s. That is all I am saying.

And it's still wrong no matter how many times you repeat it. See above and further comments below.

altergnostic said:
It has been said that B receives the beam at 1.12s in the observer at A's frame, and 1s in the clock's frame (or the frame of the mirror at B). But that last is a given, and the former is an assumption.

Yes, the last is a given. No, the former is *not* an assumption. It's a calculation. Since you have said you agree that the speed of light in an inertial frame is c regardless of the motion of the source, the calculation is simpler than what I have posted before. The givens are:

(1) Light pulse 1 is emitted by the light clock source/detector at the instant that it passes the observer at A. That event occurs at time 0 in both the observer frame and the light clock frame.

(2) The distance from A to B is 1.12 light seconds in the observer frame.

Therefore, we can immediately calculate:

(3) Light pulse 1 reaches B at time t = 1.12s in the observer frame, since it is covering a distance of 1.12 light seconds and travels at c.

Since you already agree that light pulse 2 takes 1.12s to travel from B back to A in the observer frame, that makes it clear that light pulse 2 arrives at A at time t = 2.24s in the observer frame, *not* t = 2.12s.

I won't even bother commenting on the rest of your post; the error you are making should be clear from the above.
 
  • #160
On re-reading, there is one other error that seems to me to be worth commenting on:

altergnostic said:
If we have an observer at B, at t'=1s the beam appears to come from the stationary mirror at C. At t=1s, B sees the light of the beam on the mirror at C, 1 light-second away.
The path of detected light in the primed frame is CB.

No, it isn't. The triangle diagram you drew is a diagram of the spatial geometry in the unprimed frame, *not* the primed frame. The point you have labeled C is the location that the light clock source/detector is at, in the unprimed frame, at the time when light pulse 1 hits the mirror. It is *not* the location of the source/detector in the primed frame, because in the primed frame the source/detector and the mirror (i.e., the entire light clock assembly) are at rest.

The spatial geometry in the primed frame would be a *different* diagram, in which the positions of the observer at A would lie on a line going out to the left, the spatial path of light pulse 1 would be a line straight up, and the spatial path of light pulse 2 would be the hypotenuse of a right triangle whose legs are the path of light pulse 1 and the path of the observer at A. Any reasoning about spatial paths and lengths in the primed frame would have to be done using this other diagram, *not* the diagram you drew.
 
  • #161
altergnostic said:
[..] It has been said that if I simply do the MM interferometer analysis I will have solved this setup without any contradiction. I disagree. [..]
Please do so - even if I was wrong and one or two issues remain, it will enormously clear up this discussion. It still appears that you disagree about almost everything, which makes it difficult to untangle the mess.
 
Last edited:
  • #162
altergnostic said:
If I understand every claim correctly, the basic disagreement is that, if the distance AB is 1.12ls, then light should take 1.12s to travel that distance regardless of direction, which is basically saying that the speed of light is c regardless of the speed of the source. What seems hard to grasp is that I am not advocating against this assumption.
If the distance is 1.12 ls and the speed is c regardless of direction then the round trip time is clearly 2.24 s.

Furthermore, even without assuming the speed is c, experiments confirm the round trip time (aka the two way speed of light) so any value you choose other than 2.24 s is contrary to experiment. See the Robertson paper I posted earlier.


altergnostic said:
I am simply requiring B's frame of reference to be obtained from A's frame by a standard Lorentz transformation.
Please post the Lorentz transform from A to B then. You will see that your claims are inconsistent with the Lorentz transform.
 
  • #163
DaleSpam said:
If the distance is 1.12 ls and the speed is c regardless of direction then the round trip time is clearly 2.24 s.

Furthermore, even without assuming the speed is c, experiments confirm the round trip time (aka the two way speed of light) so any value you choose other than 2.24 s is contrary to experiment. See the Robertson paper I posted earlier.

A beam describing ABA would indeed take 2.24s for the round trip, as is confirmed by experiment, but this is not what is happening here. The observer at A is not the emitter, and from the point of view of the emitter, the path is CBC, not ABA. The observer at A only has the distance AB and a signal from B to A, but he has no direct information on the path from A to B, he must calculate it from the time he receives the signal from B, and we are disagreeing on that reception time, so we have to clear this up. Would you agree that, if a stationary clock placed at B is synchronized with the clock at A, we can find the reception time by taking the time of the event as shown on the clock at B and adding the time it takes the signal from that event to get to A? Or, likewise, we can find the time of the event on the stationary clock at B by taking the reception time and subtracting the time it takes for light to cross the distance AB? Isn't this how we find the times of stationary synchronized clocks? For instance, to synchronize the clocks at A and B we would take a roundtrip measurement (2.24s, like you said) and half that value to get the time separation of the clock at B, so we know that a tick of the clock at B is observed 1.12s later at A. After that synchronization, we can calculate the time of any event at B from A simply by subtracting 1.12s from the reception time, don't you agree? Since the observer at A receives the signal from B 1.12s later than the time of emission, and the time of emission (according to the clock at B - which is stationary and synchronized with the clock at A) is 1s, the observer at A must receive that signal at 2.12s. I can't see it any other way. If the reception time was 2.24s than the emission time would have to be 1.12s and that is not in agreement with what is shown on the clock at B. If you are right, either the clocks at A and B are out of sync, or the clock at B is time dilated (and I don't see how that can be true) or the event at B occurs at 1.12s from the point of view of B, which would then be in disagreement with the light-clock time for that event, which is insane since the event at B happens at the same spacetime coordinates for both the light-clock and the clock-signaler at B.

Please post the Lorentz transform from A to B then. You will see that your claims are inconsistent with the Lorentz transform.

You misunderstand me (or I wasn't clear). What I meant is that this frame alignment is what would allow us to apply standard lorentz transforms. I am simply requiring that both frames x-axis are aligned with AB, no calculations needed for this requirement, it is standard procedure in most SR problems and it helps to simplify things a bit.
 
  • #164
altergnostic said:
The observer at A is not the emitter

Doesn't matter. The observer at A is co-located with the emitter at the instant of emission. So the path of the light, in the unprimed frame, *is* ABA.

altergnostic said:
and from the point of view of the emitter, the path is CBC

No, it's C'B'A', because "from the point of view of the emitter" means in the primed frame, *not* the unprimed frame. The geometry in the primed frame is *different*; it does *not* look like the triangle diagram you drew.

altergnostic said:
Would you agree that, if a stationary clock placed at B is synchronized with the clock at A, we can find the reception time by taking the time of the event as shown on the clock at B and adding the time it takes the signal from that event to get to A?

Yes, *if* the clock at B is at rest relative to the clock at A and synchronized with it.

altergnostic said:
Or, likewise, we can find the time of the event on the stationary clock at B by taking the reception time and subtracting the time it takes for light to cross the distance AB?

For a *stationary* clock at B, yes.

altergnostic said:
the time of emission (according to the clock at B - which is stationary and synchronized with the clock at A)

No, it isn't. Your "clock at B" that reads 1s when light pulse 1 arrives is moving with the light clock; it's the "clock" on the light clock's mirror that records when light pulse 1 arrives. It's not stationary and synchronized with the clock at A. A *stationary* clock at B, that was synchronized with observer A's clock, would record a time t = 1.12s when light pulse 1 arrives at the mirror.

altergnostic said:
the event at B happens at the same spacetime coordinates for both the light-clock and the clock-signaler at B.

I don't know what you mean by "the clock-signaler at B". Do you mean an observer *stationary* at B, who emits light pulse 2 back to A? If so, then your statement is incorrect; the clock-signaler's clock will read t = 1.12s when light pulse 1 arrives at the mirror, as I said above. The clock-signaler's clock is not synchronized with the moving mirror's clock, nor are his spatial coordinates the same as those of the light clock. The *event* is the same, but it is described by different coordinates (i.e., a different set of 4 numbers t', x', y', z') in the primed frame than in the unprimed frame.

You apparently do not understand how frames in relative motion work. The only event that has the same spacetime coordinates (i.e., the same set of 4 numbers t, x, y, z) in both frames is the origin, the event at which light pulse 1 is emitted by the light clock source/detector at the instant it is spatially co-located with the observer at A. Every other event in the spacetime has *different* coordinates in the two frames. I suggest a review of a basic relativity textbook, such as Taylor & Wheeler's Spacetime Physics.
 
  • #165
harrylin said:
Please do so - even if I was wrong and one or two issues remain, it will enormously clear up this discussion. It still appears that you disagree about almost everything, which makes it difficult to untangle the mess.

Harry, that analysis does not apply to this setup at all, that is my point. The only possible way to do that is like it is always done: giving c to AB, so by doing it my arguments and givens are useless. You see, I am putting that very assumption into question with my setup, so I can only do what you ask me to do by giving up what I am concerned about in the first place. Also, it is done all over the place and we can simply google "light clock time dilation interferometer, etc" and we will have tons of results. You can't use that analysis to answer "what is the speed from A to B" since that is a given in that analysis in the first place. Also, MM analysis don't have an observer at A like I have here, and also no possible communication from reflection events to that observer (or any other moving observer for that matter). So I can't possibly relate the interferometer analysis to my setup. If we assume that light travels at c as seen from an absolute ether or in any direction for any frame, my analysis is meaningless since it is intended to check those assumptions.

If we rerun my analysis with a projectile going 0.5c from A to B instead of the beam, would you agree that it stands? Do you agree on A's reception time of 2.12s for the signal from B? If not, are you saying that the time of emission of the signal from B shown on the clock at B is 1.12s? If so, how can that be since at t'=1s the light-clock is reflecting the beam at B? Is that event happening at t'=1s or t'=1.12s, as seen from B? Are you saying we can have two different times for the same event, as seen from B? If so, please explain how, because I can't see how that is possible in this problem.
 
  • #166
Thread locked pending moderation.
 
<h2>1. What is the paradoxical light clock problem in special relativity analysis?</h2><p>The paradoxical light clock problem is a thought experiment used to illustrate the effects of time dilation in special relativity. It involves two identical clocks, one stationary and one moving at a high speed, with a beam of light bouncing between them. According to the theory of special relativity, the moving clock will appear to tick slower than the stationary clock, leading to a paradox where the moving clock appears to be both ticking slower and faster at the same time.</p><h2>2. How does special relativity explain the paradoxical light clock problem?</h2><p>Special relativity explains the paradoxical light clock problem by taking into account the concept of time dilation, which states that time moves slower for objects that are moving at high speeds. This means that the moving clock in the thought experiment will actually tick slower than the stationary clock, and the apparent paradox is resolved.</p><h2>3. What are some real-world examples of time dilation in special relativity?</h2><p>Some real-world examples of time dilation in special relativity include the Global Positioning System (GPS) and particle accelerators. GPS satellites orbit the Earth at high speeds, causing their onboard clocks to experience time dilation. This must be taken into account for accurate GPS calculations. In particle accelerators, particles are accelerated to near the speed of light, causing them to experience time dilation.</p><h2>4. How does the paradoxical light clock problem impact our understanding of time and space?</h2><p>The paradoxical light clock problem, and the theory of special relativity in general, has greatly impacted our understanding of time and space. It has shown that time is not absolute, but rather is relative to the observer's frame of reference. It has also led to the concept of space-time, where time and space are interconnected and can be affected by factors such as gravity and velocity.</p><h2>5. Are there any unresolved questions or criticisms of the paradoxical light clock problem in special relativity analysis?</h2><p>While the paradoxical light clock problem has been widely accepted and used to support the theory of special relativity, there are still some unresolved questions and criticisms. Some argue that the thought experiment oversimplifies the concept of time dilation and does not take into account other factors such as length contraction. Others question the validity of the assumptions made in the thought experiment. However, the paradoxical light clock problem remains a valuable tool in understanding the effects of time dilation in special relativity.</p>

1. What is the paradoxical light clock problem in special relativity analysis?

The paradoxical light clock problem is a thought experiment used to illustrate the effects of time dilation in special relativity. It involves two identical clocks, one stationary and one moving at a high speed, with a beam of light bouncing between them. According to the theory of special relativity, the moving clock will appear to tick slower than the stationary clock, leading to a paradox where the moving clock appears to be both ticking slower and faster at the same time.

2. How does special relativity explain the paradoxical light clock problem?

Special relativity explains the paradoxical light clock problem by taking into account the concept of time dilation, which states that time moves slower for objects that are moving at high speeds. This means that the moving clock in the thought experiment will actually tick slower than the stationary clock, and the apparent paradox is resolved.

3. What are some real-world examples of time dilation in special relativity?

Some real-world examples of time dilation in special relativity include the Global Positioning System (GPS) and particle accelerators. GPS satellites orbit the Earth at high speeds, causing their onboard clocks to experience time dilation. This must be taken into account for accurate GPS calculations. In particle accelerators, particles are accelerated to near the speed of light, causing them to experience time dilation.

4. How does the paradoxical light clock problem impact our understanding of time and space?

The paradoxical light clock problem, and the theory of special relativity in general, has greatly impacted our understanding of time and space. It has shown that time is not absolute, but rather is relative to the observer's frame of reference. It has also led to the concept of space-time, where time and space are interconnected and can be affected by factors such as gravity and velocity.

5. Are there any unresolved questions or criticisms of the paradoxical light clock problem in special relativity analysis?

While the paradoxical light clock problem has been widely accepted and used to support the theory of special relativity, there are still some unresolved questions and criticisms. Some argue that the thought experiment oversimplifies the concept of time dilation and does not take into account other factors such as length contraction. Others question the validity of the assumptions made in the thought experiment. However, the paradoxical light clock problem remains a valuable tool in understanding the effects of time dilation in special relativity.

Similar threads

  • Special and General Relativity
Replies
7
Views
950
  • Special and General Relativity
Replies
14
Views
579
  • Special and General Relativity
Replies
12
Views
1K
  • Special and General Relativity
Replies
15
Views
316
  • Special and General Relativity
Replies
16
Views
597
  • Special and General Relativity
Replies
20
Views
1K
  • Special and General Relativity
Replies
6
Views
2K
  • Special and General Relativity
2
Replies
65
Views
3K
  • Special and General Relativity
Replies
14
Views
1K
  • Special and General Relativity
Replies
21
Views
1K
Back
Top