| Thread Closed |
Light Clock Problem |
Share Thread | Thread Tools |
| Nov16-12, 06:17 AM | #103 |
|
Mentor
|
Light Clock Problem |
| Nov16-12, 06:20 AM | #104 |
|
|
|
| Nov16-12, 06:31 AM | #105 |
|
Mentor
|
![]() Besides the funny self-contradiction, it is one of the postulates of SR that it is going at c in all frames. We know its speed according to SR, and alternative theories that disagree with SR are not permitted here. |
| Nov16-12, 07:00 AM | #106 |
|
|
OK, I think that we are getting somewhere:
[EDIT: In fact, my answer took care of the spatial rotation misconception] ![]() |
| Nov16-12, 09:16 AM | #107 |
|
|
How do you measure the speed of the train? You take the distance it covers over the time it takes to cover it. This velocity is not the same as marked on the trains own speedometer, for instance. You are on the train and it marks .5c on the speedometer. You cross 1 light second, from your perspective, in 2 seconds. An observer at the embankment would see the train cross that distance in 2 seconds + the time it takes light to reach back to him from that distance (which would be the time marked on the observers watch at the moment he sees the train at that distance). The speed will seem to be slower relative to the speed as seen on the onboard speedometer! I have a diagram on this from a discussion I had a few months ago: ![]() But I'm afraid this will divert us from the topic, maybe this needs a thread itself. |
| Nov16-12, 09:31 AM | #108 |
|
|
|
| Nov16-12, 09:32 AM | #109 |
|
|
|
| Nov16-12, 10:03 AM | #110 |
|
Mentor
|
Note, the standard analysis only purports to be an analysis of the operation of the clock and not an analysis of the subsequent transmission of the results to any observer. Such considerations are irrelevant to the operation, as you have already agreed. |
| Nov16-12, 10:07 AM | #111 |
|
|
I insist that you have to align the x axis with AB and completely ditch the speed of the light clock in the former x axis, since it is actually causing a distraction here. Please note that the observer at the origin doesn't even need to know that speed to calculate anything: He is given the distance AB He knows the primed times, since he has synchronized his watch with the light clock back at the origin. He knows that the reflection at B occurs at t'=1s. He receives the signal event from B at T=t'+ the time it took for the light signal to cross BA and reach him - that is the time he actually sees the signal, and is the time he observes the beam to reach the point B. From the given distances and the observed times he can only observe that the beam crossed AB in T seconds, and then subtract the time it takes light to cross BA to get the primed time - which will be 1s again. This seems all extremely consistent, and in accordance with what we would expect to have by replacing the beam with a projectile. If a projectile hits B at t'=2s, the observer will observe it crossing AB at T=t' + the time it took light to cross BA, and then subtract the time it takes light to cross BA to get the primed time - which will be 2s again. By this method, the primed velocity will make the primed distance smaller than AB (length contraction), and the calculated distance will become y', which again is fully consistent with the setup. Like so: Observed speed of the beam = AB/T = 1.12/2.12 =0.528c Transformed time of event B = t'= 1s We know that light travels at c locally from many many experiments, so to get the distance travelled by light in the primed frame, we just have to figure out the distance light crossed in 1 second (the primed time) = 1lightsecond = y' Do you see my reasoning? You may not agree with it for some reason, but it is very consistent, and all the numbers add up. I can't see any error on it, if you can, please do point it out, since I am not here to defend any preconceived opinion, I'm just going where logic and math has taken me and sharing this with you for open analysis. And just as a footnote, I don't think this contradicts any postulates nor disproves or changes SR in any way. It is simply a setup that hasn't been thought of yet, as far as I know (and I have to share credit for this with harrylin, even if he disagrees with my analysis). Observed light still travels at c. It also travels at c relative to the source. It is undetected light, or indirectly observed light, that I conclude doesn't need to follow the constant, but this is not your ordinary light. It is not the light that enters any known equation as c. This is light moving at a distance. Not a single light equation takes c to be light at a distance, everytime you have c in an equation, that c is referring strictly to light that reaches the observer, which is the light you do transforms with. That's the importance of the signal arriving from B: it is with this light that we observe the beam, and it is with this light that we must do transforms, just like in any other setup. To give the speed of light both for this incoming light and for the beam, as seen in the unprimed frame, is similar to believing that the speed of the man walking inside a moving train is the same for both primed (the train) and unprimed (embankment) frames. If you still think the beam will be observed to go at c from A to B as observed from the observer at the origin A, than you have to explain why wouldn't the speed of a projectile (in place of the the beam) be the same in the primed and unprimed frame as well. Please consider this carefully and think about this with no prejudice (I mean no harm to SR )
|
| Nov16-12, 10:08 AM | #112 |
|
|
I also, once I understood that there was a second light signal involved (from event B1b to A2), did the same kind of computation for that light signal: compute the location of the observer at event A2 (we already know the mirror's location at event B1b because event B1b is co-located with event B1a), and confirm that the spacetime interval between events B1b and A2 is of zero length, again in both frames. ![]() We now have the x axis oriented in such a way that the event coordinates in the unprimed frame are as follows: A0 = D0 = (0, 0, 0) B1a = B1b = (t1, x1, 0) A2 = (t2, 0, 0) D2 = (t2, x2, y2) Our objective is to find t1, x1, t2, x2, and y2, and then compute the spacetime intervals (A0 to B1a), (B1b to A2), and (B1b to D2), and verify that they are all zero. The first thing to note is that the time coordinates are unchanged from my previous analysis; i.e., we still have t1 = 1.16 and t2 = 2.32. The second thing to note is that x1 must be given by the sum of the squares of the x and y coordinates for events B1a/B1b in my previous analysis (since it's the same spatial distance, we've just rotated the axes to put that distance all along one axis); i.e., we must have [tex]x_1 = \sqrt{ 1 + ( 0.58 )^2 } = 1.16[/tex] The third thing to note is that the sum of the squares of x2 and y2 must equal the square of the y coordinate of event D2 in my previous analysis (again, the same spatial distance from the origin, just with the axes rotated); i.e., we must have [tex]x_2^2 + y_2^2 = ( 1.16 )^2 = x_1^2[/tex] This tells us something very important: the distances AB, BD, and AD in your diagram are all *equal*. (We could have seen this directly by noting that the light clock, which moves half as fast as the light pulse, covers distance AD in the same time as the light pulse covers distance AB + BD; therefore AB + BD = 2AD, which combined with AB = BD gives AB = BD = AD.) This means that the angle between lines AB and AD is 60 degrees (since it's an angle of an equilateral triangle), so we must have [tex]\frac{y_2}{x_2} = tan (60 deg) = \sqrt{3}[/tex] Substituting this into the equation above gives [tex]x_2^2 + 3 x_2^2 = x_1^2[/tex] or [tex]2 x_2 = x_1[/tex] Now we can confirm that the spacetime intervals I mentioned are zero. First, we have t1 = x1, so the interval (A0 to B1a) is obviously zero. Similarly, we have t2 - t1 = t1 = x1, so the interval (B1b to A2) is obviously zero. Finally, the interval (B1a to D2) is given by [tex](t_2 - t_1)^2 - (x_2 - x_1)^2 - (y_2 - 0)^2 = ( 1.16 )^2 - ( x_2^2 + y_2^2 ) - x_1^2 + 2 x_2 x_1 = ( 1.16 )^2 - ( 1.16 )^2 - x_1^2 + x_1^2 = 0[/tex] As I said, the answer remains the same. ![]() |
| Nov16-12, 10:13 AM | #113 |
|
|
|
| Nov16-12, 10:21 AM | #114 |
|
|
|
| Nov16-12, 10:23 AM | #115 |
|
|
|
| Nov16-12, 10:27 AM | #116 |
|
|
A better tool for this job, IMO, would be a proper spacetime diagram, since that directly shows both space and time relationships and allows you to draw actual worldlines so you can see how they are related. If you aren't familiar with spacetime diagrams, I would recommend learning them; they really help to remove confusion for scenarios like this one. |
| Nov16-12, 12:42 PM | #117 |
|
|
But please, let's leave this be for now, since we will surely divert from the topic. If you feel this deserves attention and want to discuss it further, I will gladly start a thread on this, but let's please not digress here, since this thread is already dense enough as it is. Deal? |
| Nov16-12, 12:45 PM | #118 |
|
Mentor
|
|
| Nov16-12, 01:04 PM | #119 |
|
|
I suspect you are confused because you think length contraction affects the velocity from frame to frame. It doesn't, because length contraction and time dilation *both* come into play, and their effects cancel when applied to the relative velocity. If you don't see how that works, read through my analysis again, carefully; for example, look at how the coordinates of events A2 and D2 transform between the primed and the unprimed frame, and note that the time and space coordinates change in concert to keep the relative velocity the same. [Edit: To expand on this a little more, events D0 and D2 both lie on the worldline of the light clock source/detector, which is equivalent to the "train"; and events A0 and A2 both lie on the worldline of the observer, which is equivalent to the "ground". Events A0 and D0 are co-located at the origin, so their coordinates drop out of the analysis, and we can use the coordinates of event D2 in the unprimed frame, and A2 in the primed frame, to compute the relative velocity. In the unprimed frame, event D2 has coordinates (t2, x2, y2), and the relative velocity is given by sqrt(x2^2 + y2^2) / t2, which works out to 0.5. In the primed frame, event A2 has coordinates (t2', x2', y2'), and the relative velocity is given by sqrt(x'2^2 + y2'^2) / t2', which works out to 0.5. Then we just have to remember to set the sign appropriately, based on the sign of (x2, y2) or (x2', y2'), which gives v = +0.5 in the unprimed frame and v = -0.5 in the primed frame.] |
| Thread Closed |
| Tags |
| light clock, special relativity, time dilation |
| Thread Tools | |
Similar Threads for: Light Clock Problem
|
||||
| Thread | Forum | Replies | ||
| Light Clock | Special & General Relativity | 8 | ||
| Time dilation explaination with mechanical clock instead of light clock | Special & General Relativity | 55 | ||
| Light Clock Example this is not HW | Special & General Relativity | 14 | ||
| Questions abouut:Special Relativity, Time Dilation, Light Clock, Velocity of light. | Special & General Relativity | 31 | ||
| Light Clock | Special & General Relativity | 7 | ||