- #36
JDoolin
Gold Member
- 723
- 9
PeterDonis said:I think I wasn't clear enough about what I was using the term "distance" to refer to. I should have worded my previous posts more carefully, both for that reason and because there are subtleties involved that I didn't fully consider at first.
Nor is it even well-defined, as you've stated it; the interval between the emission event and the absorption event is null, so there is no "distance" between these events ("distance", in the spatial sense, only applies between spacelike separated events).
If what you meant to say is that the distance, meaning spatial distance, between the *emitter* and the *receiver* can be different in different frames (so it is not an invariant), then I agree, but there is no frame where the events on the emitter and receiver worldlines between which "distance" is measured (i.e., which are crossed by a single line of simultaneity in the frame) will be the emission and absorption *events* (again, because those events are null-separated, not spacelike-separated).
This meaning of "distance"--i.e., distance between emitter and receiver--is what I was using the term "distance," without qualification, to refer to. However, I may not have been clear enough about that, since I was also talking about an observer that sees both emitter and receiver as moving, and "distance" could have been taken to mean the distance to that observer, at some particular time, which is *not* the way I meant it. See below.
Agreed.
Actually, the distance as I was using the term (i.e., distance between emitter and receiver--see above) always goes down; more precisely, if we are in any frame in which emitter and receiver are both moving with some nonzero velocity v, the spatial distance between them, as seen in that frame, will be *less* than the "proper distance" between them in the frame in which they are both at rest. This should be obvious from the fact that Lorentz contraction is the same regardless of which direction the objects are moving.
The above is what I've been talking about when I talk about "distance", and that's why I said that it was possible for the frequency to go up while the distance was going down: if the emitter is moving towards the observer, then the frequency goes up, but the distance between emitter and receiver goes down by Lorentz contraction. My quick back of the envelope check seems to indicate that in this case, the Doppler shift in frequency exactly compensates for the Lorentz contraction, so the product (frequency / c) * (distance between emitter and receiver) does in fact stay constant. (Note the way I stated the product this time--this is what I meant last time, but the term "distance to source" was ambiguous, and that may have caused confusion. Sorry about that.)
The subtlety, of course, is that the above nice compensation only works for a Doppler *blue* shift! For the case where the emitter (and hence also the receiver) is moving *away* from the observer, so there is a Doppler red shift, the nice compensation doesn't work; distance between emitter and receiver goes down (by Lorentz contraction), but frequency *also* goes down! So this product as it stands won't work as an invariant. However, there is something that will; see below.
This is true, but it's not what I was proposing. I was simply saying the following: there is one line of simultaneity that *is* picked out by the problem as different from all the others, namely, the one in the frame in which the emitter and receiver are both at rest. The number of wave crests along that line of simultaneity between emitter and receiver *is* an invariant, because we've specified a particular spacelike line along which to measure it; anyone in any frame can calculate the number and come up with the same answer. The calculation is harder in a frame in which emitter and receiver are moving, because it has to calculate the number of wave crests along an "unnatural" spacelike line for that frame--i.e., one which is *not* a line of simultaneity in that frame. But it can still be done.
You'll note that, with reference to this particular point, I did not just use the term "distance," unqualified; I used the phrase "the number of wave crests counted along a given line of simultaneity, in a given proper distance along that line."
Yes, but one that is the same for all possible (emitter, receiver) pairs, so it does nothing to distinguish them.
You should distinguish between "distance between objects" and "distance between events."
The "unqualified distance" term you are using, is the distance between the emitter and receiver objects. This is the more familiar distance discussed under the heading of "length contraction" or "lorentz contraction", where solid bodies appear to contract in the direction of motion.
But distances can and should also be measured between nonsimultaneous events. For instance in this emission and absorption example, you shouldn't pretend that the distance traveled by the photon is equal to the distance between the emitter and receiver. Why? Because while the photon is under way, the receiver either moves toward or away from the emitter. This means that the distance between the receiver and emitter is irrelevant. It is the distance between the emission EVENT and absorption EVENT which is relevant.
You claimed the "distance between events" is not well-defined, but I disagree. Whenever you do a lorentz transformation, the x, y, and z terms refer to the coordinates of events; not objects. The distance between the emission and absorption events in any given frame is another distance [tex]\sqrt{\Delta x^2+\Delta y^2+\Delta z^2}[/tex]. The LT equations themselves do not distinguish to whom or to what the events occurred. All that is of concern is where and when, relative to a stationary origin.
Now for the snowflake example:
Let's note that this distinction (distance between events vs. distance between objects) should show up in basic "Galilean" relativity as well. We could talk about snowflakes coming down with a driver passing through them. The question is, are the snowflakes really coming straight down, or are they going almost 55 miles per hour horizontally?
The fact is, you could arrange two rulers, one long, nearly horizontal one traveling along with the car, and another short vertical one stationary with the ground, and the snowflake follows the path of both rulers. The top end of the two rulers meet when the snowflake passes the top, and the bottom end of the two rulers meet when the snowflake passes the bottom. (but at every moment, the two rulers and the snowflake align.)
My premise is that both the driver of the car, and the person on the ground use their own rulers and give correct (but different) answers for the distance between those two events. That is the premise behind the galilean transformation, and the lorentz trasformation.
First let me point out my snowflake example above. Who is correct? The guy in the car who thinks the snowflakes are coming right at him, or the person on the ground who thinks the snowflakes are coming straight down? You can pick out a frame of reference that meets some arbitrary criteria, but I think the most sensible criteria is "observer dependence." Use the distance as measured by a ruler in that reference frame, where your observer is. The driver and the person on the ground are equally correct, so long as they make it clear who and where they are.
You may still feel like one of the drivers is incorrect, but remove the planet, and just have the car and the snowflake flying through space. The snowflake is coming at the car at 55 miles per hour and travels a whole second at that speed. That distance is well-defined, even though the events did not happen at the same time.