SteyrerBrain said:
I guess I understand too little about GR to see the reason for different coordinate systems for a non-inertial object. It can't be the directions of the coordinate axes - these are also not uniquely determined in an inertial frame. Can you give me a hint, where the problem arises?
I don't understand much about GR either, but as I understand it GR does allow you to use any coordinate system you can dream up, and intuitively it's not hard to see some problems with defining the coordinate system of an accelerating observer--for example, how do you want simultaneity to work at each point during the acceleration? At each moment along the object's worldline, should its definition of simultaneity match that of the inertial frame where it's at rest at that moment? If you try to do it this way, you can have problems with planes of simultaneity at different points along the wordline intersecting each other, so that the same event is sometimes assigned multiple time coordinates, and distant clocks can run backwards as coordinate time runs forwards. For instance, suppose I am approaching the Earth at high velocity and then when I get within a certain distance I accelerate rapidly until I am moving away from the Earth at high velocity; if you draw the planes of simultaneity for my instantaneous inertial rest frame shortly before and after I accelerate, you may find that the date on Earth before I accelerate is actually
later than the date on Earth after I accelerate, according to the definition of simultaneity in my instantaneous inertial rest frame at each moment.
And how can your coordinate system be defined physically? For an inertial observer, you can define the coordinates of different events in terms of local readings on a network of rulers and clocks which are at rest relative to the observer, and which are synchronized according to the Einstein convention (assume the speed of light is constant in your own rest frame, so that if you turn on a light at the midpoint of two clocks, they should both read the same time when the light hits them). In this situation, all other inertial frames will agree that the rulers and clocks have the same (constant) velocity as the observer at every moment. But for an accelerating observer, if he has his own network of accelerating rulers and clocks I don't think it's possible that all inertial frames would see the rulers and clocks having the same velocity as the observer at all moments, which would also mean that all inertial frames would not see all the clocks ticking at the same rate or all the rulers being the same length at a given moment. Given this, there doesn't seem to be anyone "natural" way of having the rulers and clocks accelerate, since if there is one frame where all the rulers and clocks are matching the observer's velocity at each moment, this won't be true in other frames, and there's no reason to set it up so this happens in one frame as opposed to another (again, I guess you could try to set it up so that in the instantaneous inertial rest frame of the accelerating observer, all the rulers and clocks were at rest as well, but past a certain distance this might not work because it would require rulers and clocks to move in impossible ways like going backwards in time or faster than light).
SteyrerBrain said:
But still: since the clocks periodically meet at one point (always the starting point), all computations - even based on different coordinate systems - should agree on the time offset between the clocks at this meeting point!? Different definitions of simultaneity can only occur for objects/events, that are apart (as far as I understand).
Wolfgang
Yes, that's definitely true, as long as you are using the correct laws of physics in each coordinate system (you can't assume that the usual rules of SR will work in a non-inertial coordinate system). Like I said, my understanding is that the rules of GR work in any arbitrary coordinate system, although for each new coordinate system I'm guessing you have to first find the correct form of the metric when expressed in that system.