What is the Effect of Gravity on Einstein's Train in Special Relativity?

In summary, the passengers on a train moving at relativistic speed on a flat planet conducted an experiment to measure the effects of gravity on light beams. Two views emerged, the "stationary preferred" and "passenger preferred", but the latter was deemed incorrect. The paper mentioned in the conversation was also found to be wrong in its explanation of the weight of objects in Einstein's train. The trajectory of objects dropped in the train was found to follow a geodesic, but this was a complicated concept. The concept of relativity of simultaneity was also discussed and applied to an experiment involving a rocket accelerating upward with sideways velocity. In the case of gravity, the same experiment was conducted on a transparent train on the surface of a planet,
  • #141
pervect said:
a is the proper acceleration ##\gamma^2 g## of a point on the block

Note that this is only true on the equipotential surface in which the chosen worldline lies. Other equipotential surfaces have different magnitudes for ##a##. And, as your chart explicitly illustrates, the direction of ##a## can, in general, change as well once you are off the chosen worldline (though it doesn't in my chart).

pervect said:
##\omega## is the proper rotation, which has a magnitude of ##\gamma^2 g v## (I haven't worked out the sign of the rotation) and is oriented about the ##\hat{z}## axis.

This magnitude also varies once you are off the chosen worldline, as does, in general, the orientation of the rotation. Your metric keeps the orientation about the ##\hat{z}## axis, but mine does not. However, to first order, close enough to the chosen worldline, they agree.
 
Physics news on Phys.org
  • #142
pervect said:
an accelerating observer who chooses to use orthonormal basis vectors, but not to Fermi-walker transport them.

I am still working on some computations, but I would observe that this statement cannot be true as it stands, since there are nonzero ##dx^0 dx^i## "cross terms" in the line element, which means that the coordinate direction ##\partial_0## is not orthogonal to all of the ##\partial_i## directions. That means the tetrad ##\partial_0 / | \partial_0 |, \partial_i## is not orthonormal (it is normalized, but not orthogonal). On the reference worldline, the "cross terms" vanish, so the above tetrad is orthonormal on that worldline, but it is not orthonormal elsewhere.
 
  • #143
It occurs to me that this sort of evolving, constructive discussion would really benefit from a wiki rather than this blog format, because then there can be an evolving document that has everything in one place and that continually improves as people like Peter and Pervect contribute to it.

I realize that this is probably wishing for the moon, as wikis are (so I understand) completely different technology from blogs.
 
  • #144
andrewkirk said:
It occurs to me that this sort of evolving, constructive discussion would really benefit from a wiki rather than this blog format
Not sure about that, wiki is generally the definitive answer rather than a discussion.
In any case, as long as we arrive at the solution, it can be sorted later :biggrin: I just wish I wasn't stuck at page 4 :confused:
 
  • #145
andrewkirk said:
this sort of evolving, constructive discussion would really benefit from a wiki

As you suspect, we don't really have the technology for a wiki here at PF. However, the key material from this thread would probably be suitable for a PF Insights article once we have everything sorted out.
 
  • #146
pervect said:
an accelerating observer who chooses to use orthonormal basis vectors, but not to Fermi-walker transport them.

PeterDonis said:
I am still working on some computations, but I would observe that this statement cannot be true as it stands, since there are nonzero ##dx^0 dx^i## "cross terms" in the line element, which means that the coordinate direction ##\partial_0## is not orthogonal to all of the ##\partial_i## directions. That means the tetrad ##\partial_0 / | \partial_0 |, \partial_i## is not orthonormal (it is normalized, but not orthogonal). On the reference worldline, the "cross terms" vanish, so the above tetrad is orthonormal on that worldline, but it is not orthonormal elsewhere.

Let me quote MTW, bg 174, the beginning of exercise 6.8.

MTW said:
An observer moving along an arbitrarily accelerated worldline chooses not to Fermi-Walker transport his orthonormal tetrad. Instead, he allows it to rotate. The anti symmetric rotation (..) splits into a Fermi-Walker part plus a spatial rotation part.

I don't see much difference between my paraphrase of MTW's remark and the original. I strongly suspect that a good part of the difficulties in our communications arise from a fundamental difference between your approach and MTW's approach. My results with explaining MTW's approach in my own words has not been so successful to date, so rather than attempt to explain further I'll refer you to the text. I'd be happy to try to explain again, anyway, if you think it'll help, but judging by my track record to date I'm thinking it would be better to refer you to the textbook and the fuller context in which the textbook's remarks were made.

If you have the time to study this further, you might want to compare the mathematical equations of how MTW uses the tetrad to find the location of a point.
 
  • #147
pervect said:
I don't see much difference between my paraphrase of MTW's remark and the original.

I'm not disputing that you've quoted MTW correctly. I'm saying that their use of the term "orthonormal", strictly speaking, can only be correct on the reference worldline, where the "cross terms" in the metric vanish. If there are nonzero "cross terms" in the metric, the coordinate basis vectors cannot be orthogonal. So MTW's terminology here is a little sloppy.

(Note, btw, that MTW only says explicitly that the observer on the reference worldline has an orthonormal tetrad. They do not explicitly say, as far as I can tell, that the tetrad remains orthonormal off the reference worldline, i.e., where some of the ##x^i## spatial coordinates are nonzero. So what they say is not, strictly speaking, wrong; it's just, as I said above, a little sloppy, since they don't point out that "orthonormal" only applies on the reference worldline.)

pervect said:
My results with explaining MTW's approach in my own words has not been so successful to date

You don't need to explain MTW's approach; I understand it, and I think you've captured it pretty well. That's not the issue. The issue is, we want to construct a coordinate chart that covers a region of spacetime beyond the reference worldline and a small "world tube" around it; what properties do we want such a chart to have? And is it even possible for a single chart to have all the properties we would like?

Your chart uses MTW's method, which basically amounts to constructing a chart with the following key properties: surfaces of constant coordinate time in the chart are Euclidean, and all the effects of proper acceleration and rotation can be captured in two spatial vectors ##a## and ##\omega##, which appear in the line element in the form that you quoted.

My chart uses a different method, which is the same to first order as yours and MTW's, so it matches within a sufficiently small "world tube" around the reference worldline, but outside that "world tube" it is different. It has a different set of key properties: the proper acceleration always points in one coordinate direction only (##\chi##), and the number of "cross terms" in the line element is minimized (there is only one, ##d\tau d\psi##, whereas there are two in your chart).

I'm not saying my method is "right" or yours/MTW's is "wrong"; I'm simply exploring what the differences mean.
 
  • #148
I have an approximate series conversion from my coordinates to peter's coordinates, to 3'd order, which I've tested simply by trying several random points , converting my coordinates to peter's coordinates, then converting both coordinates to Minkowskii coordinates and making sure they were close. They won't be exactly the same, because it's just a series approximation.

It demonstrates that our coordinates are different by second-order terms, and that none of them are exactly the same when ##\psi## is not zero.

##(\tau,\chi,\psi)## are my coordinates, ##(\tau^\prime, \chi^\prime, \psi^\prime)## are Peters' coordinates.
[tex]
\tau^\prime \approx \tau+{\frac {gv \left( -\chi\,g+1 \right) \chi\,\psi}{{v}^{2}-1}}+1/3\,{\frac {{g}^{2}{\psi}^{3}{v}^{3}}{ \left( -{v}^{2}+1 \right) ^{2}}}[/tex]
[tex]
\chi^\prime \approx \frac{1}{g} +\chi+1/2\,{\frac { \left( \chi\,g-1 \right) g{\psi}^{2}{v}^{2}}{-{v}^{2}+1}}
[/tex]
[tex]\psi^\prime \approx
\psi+{\frac {{v}^{2}g \left( -\chi\,g+1 \right) \psi\,\chi}{-{v}^{2}+1}}-1/3\,{\frac {{v}^{4}{g}^{2}{\psi}^{3}}{ \left( -{v}^{2}+1 \right) ^{2}}}
[/tex]

As usual, my origin is at ##\chi=\psi=0##, peter's origin has ##\chi^\prime## offset by ##1/g##

A quick outline of the conversion process - we have a forward transformation from my coordinates to Minkowskii coordinates, and a reverse transformation from Minkowskii coordinates to Peter's coordinates, so when we compose the two, after correctly compensating for the different origins, we get a conversion from my coordinates to Peter's. The result is rather ugly, hence the series expansion.
 
  • #149
So I have a fairly basic question. I'm stuck at page 11 of Carroll's Lectures on GR, that's why I don't know the answer :frown: It's incredibly dense with definitions and there are no explanations.

Once you have the metric, how do you, say, measure the length of the floor and ceiling, in the ##y\ /\ \psi## direction (as if using a ruler, not radar)? I think I could integrate at ##\chi=0\text{ or }1/g, \tau=const## to get the length of the floor, but how do you find the ceiling?
 
  • #150
SlowThinker said:
Once you have the metric, how do you, say, measure the length of the floor and ceiling, in the ##y\ /\ \psi## direction (as if using a ruler, not radar)? I think I could integrate at ##\chi=0\text{ or }1/g, \tau=const## to get the length of the floor, but how do you find the ceiling?

First of all, lengths along the floor, or ceiling, or any other constant height in the rocket, are only along the ##\psi## direction in my chart, so you can only integrate at a constant ##\chi## (constant ##\tau## is assumed because you're trying to find length in a surface of constant time) in my chart to find lengths along the floor or any other constant height.

In pervect's chart, the floor/ceiling/any other constant height in the rocket curves, so (except at the center of the block/train) it has a component in the ##\chi## direction as well as the ##\psi## direction. So to find the length along, say, the floor of the rocket in pervect's metric, you would have to find the equation describing the floor of the rocket, and use it and the metric to find the correct integral.

Second, you can't "find" where the ceiling of the rocket is from the information presented so far. That's something that has to be put in by hand; you have to decide, as one of the inputs to the problem, where the ceiling of the rocket is.
 
  • #151
PeterDonis said:
So to find the length along, say, the floor of the rocket in pervect's metric, you would have to find the equation describing the floor of the rocket, and use it and the metric to find the correct integral.
Pervect said something like
pervect said:
a metric is the best and ultimately the only thing needed to describe a coordinate system
So I was wondering how that could work. I could imagine some process of constructing spacelike geodesics from the floor up and then measuring the distance between the resulting points, but it seems like a lot of work, even if I knew how to do it.
Plus, the "up direction" is probably under-defined: in your metric perhaps the ##-\tau## direction is the right one, but I'm not so sure about Pervect's.

PeterDonis said:
First of all, lengths along the floor, or ceiling, or any other constant height in the rocket, are only along the ##\psi## direction in my chart, so you can only integrate at a constant ##\chi## (constant ##\tau## is assumed because you're trying to find length in a surface of constant time) in my chart to find lengths along the floor or any other constant height.
So it's more like "you need a metric and a transformation"?

PeterDonis said:
Second, you can't "find" where the ceiling of the rocket is
Oops, sorry for the confusion. I meant the ceiling of the train's room, not the rocket, but didn't say.
I know it's 3 meters above the train's floor, as seen from the outside. Is a metric enough to find/confirm that the passengers also measure 3 meters?
 
  • #152
SlowThinker said:
So I have a fairly basic question. I'm stuck at page 11 of Carroll's Lectures on GR, that's why I don't know the answer :frown: It's incredibly dense with definitions and there are no explanations.

Once you have the metric, how do you, say, measure the length of the floor and ceiling, in the ##y\ /\ \psi## direction (as if using a ruler, not radar)? I think I could integrate at ##\chi=0\text{ or }1/g, \tau=const## to get the length of the floor, but how do you find the ceiling?

The problem comes in several parts. The first part is this - we have a 4-d space-time, but length is a purely spatial concept. So we have some choices to make here about how we eliminate the time part of the problem.

In making these choices, it helps to keep in mind the "simpler" problem of asking how we measure length on a rotating disk. Recall that torque-free gyroscopes mouned on our block do rotate, so we need to worry about this. There is a lot of literature on this topic, under the name Ehrenfest paradox. This simpler problem is not-so-simple as a perusal of the literature will show, there are a lot of different ideas as to how to go about it.

However, in most cases our block won't be rotating very fast. So if we can ignore the relativistic effects associated with the rotation, we can come up with a much simpler approximate method. This simpler approximate method will ignore any relativistic length contraction effects associated with the rotation. We do have to keep in the back of our mind that we are deliberately ignoring these effects, however.

Using my chart, this simpler method is particularly simple. We take a slice of the block at constant coordinate time ##\tau##, and we eliminate the time dimension by projecting our 4-d metric onto a 3-d metric. I'm not going to give a very careful treatment and hope that the simple intuitive approacht will be satisfactory. Intuitively, when we eliminate the time dimension from my line element, we get ##ds^2 = d\chi^2 + d\psi^2 + dz^2##. This is just the usual metric of Euclidean space. And we know how to measure distances in Euclidean space = distance^2 = ###Delta \chi)^2 + \Delta \psi^2 + \Delta z^2##. The biggest complicating factor is that the block will be curved in these coordinates. So we do need to specify which "distance" we mean - the "straight-line" distance, or the distance along the curved floor.

The more general mathematical technique says that if you have some particular curve in a 3-d space with a 3-d metric, you integrate the line element ds^2 in the 3d metric to get the length of the curve. So measuring the distance consists of specifying what curve you want to find the length of, then integrating the spatial part of the line element ds along that curve. Usually you want the curve to be a straight-line, but perhaps not always, you might want to measure a distance along the floor for instance.

To anticipate some possible objections from Peter, let me say that by "floor of the rocket", we mean the intersection of the worldsheet of the rocket floor (the collection of all worldlines in the floor) intersected by a surface of constant coordinate time. So we are talking about "the" floor of the rocket at some particular time. When you recall that my coordinate time is different from Peter's coordinate time, you can see that the idea of "the floor" is a bit ambiguous because of this issue.

In Peter's chart, the basic ideas are similar, but the concept of "a straight line" turns into the concept of a "geodesic curve", because the space itself is curved. You can read about geeodesics in Caroll, I'm not sure how much sense it will make to you at this point :(. So rather than having a curved floor in a flat space-time, we have a curve where one of the coordinates of the floor is always the same, but the space itself is curved.

In the more general 4-d case, we first need to eliminate the time dimension by one of several techniques. One technique is to use what's called a quotient manifold, which basically says that we consider every point on the quotient manifold to be a worldline in the 4-d manifold. THis process really makes the most sense when we have a metric that is independent of time. Then we need to define what we mean by the "distance between worldlines". While I think this is probably the best technique, I'm not aware of any textbook that goes into it in great detail :(.
 
  • Like
Likes PeterDonis
  • #153
SlowThinker said:
Pervect said something like

So I was wondering how that could work. I could imagine some process of constructing spacelike geodesics from the floor up and then measuring the distance between the resulting points, but it seems like a lot of work, even if I knew how to do it.
Plus, the "up direction" is probably under-defined: in your metric perhaps the ##-\tau## direction is the right one, but I'm not so sure about Pervect's.So it's more like "you need a metric and a transformation"?Oops, sorry for the confusion. I meant the ceiling of the train's room, not the rocket, but didn't say.
I know it's 3 meters above the train's floor, as seen from the outside. Is a metric enough to find/confirm that the passengers also measure 3 meters?

I don't have a lot of time, but I'll say something briefly that I hope will be helpful. A metric gives you the Lorentz interval between two nearby points, and when the two points are space-like separated, this Lorentz interval can be interpreted as a distance - a proper distance. So the metric does tell you the distance between nearby points.

To get the distance between two points that are not nearby, you need to define a curve that connects them. Then the metric gives you an integral that defines the length of the connecting curve. But some thought still needs to be given to the question of "which curve do you want the length of?"
 
  • Like
Likes PeterDonis
  • #154
I've got a question for Peter. I recall seeing some corrections in his post on the shear tensor. I wanted to know if the shear tensor for both our metrics, after all corrections are made, are uniformly zero, as my current thinking leads me to believe should be the case.

Why do I think the shear tensor should be zero? http://arxiv.org/abs/1004.1935 suggests that a Born rigid flow should be shear-free.

Ziyang Hu said:
In this paper we give a new proof, valid for all dimensions, of the classical Herglotz-Noether theorem that all rotational shear-free and expansion-free flows (rotational Born-rigid flows) in Minkowski spacetime are generated by Killing vector fields (isometric flows).

Both of our line elements should be generated by Killing flows, because in both case all of the metric coefficient a function of time. Therefore I'd expect them both to be expansion-free and shear-free. If they are not, there's some problem with my understanding.

On a related note, I believe both of our metrics should represent the same underlying congruence. This congruence is just the integral curve of the time-like Killing vector field. I don't have any formal, rigorous proof that it's unique, but I feel that it should be. My series expansion of Peter's coordinates, which I referred to as ##\tau^\prime, \chi^\prime, \psi^\prime##, seems consistent with the idea of them representing the same congruence. Basically the point is that the transformation from ##\chi## to ##\chi^\prime## and from ##\psi## to ##\psi^\prime## is not a function of time, i.e. ##\tau##. While ##\tau^\prime## is a function of all of (##\tau, \chi, \psi)##, this only means that our parameteriztion of the congruence is different - the underlying congruence is the same, only the labels (i.e. the coordinates) have changed. Thus I believe our two approaches represent the same abstract object with different labels. The series expansion, being only to a finite order (and a low one, at that) doesn't prove this, but it's consistent with the idea.

What remains to be done is to define an operational notion of "space" without any approximations via the quotient manifold method. There is not and cannot be any closed spatial surface that's perpendicular everywhere to our (presumably shared) time-like congruence of worldlines, due to the fact that the congruences have non-zero vorticity. So there is no "hypersurface-orthagonal" spatial surface. So splitting space-time into space+time via the idea of space-like surfaces of simultaneity is going to be impossible (at least if we demand that our space-like surfaces be closed surfaces). Instead, we are led to the approach that identifies all points on the same worldline as "having the same spatial coordinates". This turns the 4-d space-time metric into a 3-d, time-independent, spatial metric.

Google books finds some exposition of the quotient manfiold idea in Rizzi and Ruggiero's book "Relativity in Rotating Frames", a google search for "Rizzi and Ruggiero quotient manifold" should find it. Wikki has a reference to a 2002 paper by the same authors, but unfortunately I haven't been able to track it down. I presume the book has the same material, though. It's quite specialized and pricey however - as well as being rather advanced. R&R do make the rather interesting claim, on pg 200, that this notion of space, which they refer to as "relative space", is the only sort of space which "having an actual physical meaning form an operational point of view".

On a closing note, if this seems to be "way too much work", I can certainly sympathize. I'm more-or-less happy with ignoring the relativistic effects related to rotation and the subsequent Lorentz contraction due to the rotation, even though it's an approximation. The approximate solution I prefer is given by the line element that I gave earlier.
 
  • #155
pervect said:
Both of our line elements should be generated by Killing flows

They are. They're generated by the same Killing flow. We are just using different parameterizations of it.

pervect said:
Therefore I'd expect them both to be expansion-free and shear-free.

The congruence (it's the same for both, see below) does indeed have zero expansion and zero shear. It has non-zero vorticity.

pervect said:
I believe both of our metrics should represent the same underlying congruence.

They do. It's been a number of posts now, but I showed this by deriving the same expression in Minkowski coordinates for both 4-velocity fields. From that expression, I computed the kinematic decomposition and verified that the expansion and shear are zero and the vorticity is nonzero. (I had previously thought the shear was nonzero, but that was an error in computation on my part.)

pervect said:
What remains to be done is to define an operational notion of "space" without any approximations via the quotient manifold method.

I agree that this would be a useful thing to do. However, by analogy with the case of the Langevin congruence (the "rotating disk" congruence), I would expect the "space" defined by this method to be non-Euclidean. (Which is not to say it's the same as the "space" in my metric; I don't know whether it is or not.)
 
  • #156
I've been silently following this thread since it started, but only skimming through it without looking too closely at the maths. But recently I've been attempting to derive my own analysis. I kept going wrong; I couldn't rely on my geometrical intuition to find a solution, because my intuition is trained on Euclidean geometry, not Minkowski geometry. I had a breakthrough once I constructed an analogous problem in Euclidean geometry.

First, some terminology and conventions. I shall use (t, x, y) to denote Rindler coordinates. I shall use column vectors to denote components in Minkowski space (the initial comoving inertial frame at time zero). c=1, and the metric signature is +--. (The fourth z coordinate is suppressed throughout).

Next, my Euclidean analogy. Consider a helical ramp: like a spiral staircase, but with the discrete steps replaced by a continuous ramp. The ramp can be described by the equations[tex]
\begin{align*}
X &= r \cos \omega \theta \\
Y &= r \sin \omega \theta \\
Z &= z + k \theta
\end{align*}
[/tex]The analogy with the relativity problem is
  • radius r is equivalent to Rindler x coordinate (in the direction of the acceleration, "vertical")
  • angle [itex]\theta[/itex] is equivalent to Rindler t coordinate (time)
  • vertical height above the ramp surface z is equivalent to the sliding block's horizontal coordinate that I will denote [itex]\eta[/itex]. Note this direction, in the Euclidean helix analogy, is in the vertical direction, not perpendicular to the ramp surface.
I worked through this ramp example to find a solution that I could translate into the relativistic sliding block example. The translation involved replacing circular trig functions with hyperbolic functions and changing a few signs.

With that prologue out of the way, here's my relativistic solution. A point in the block is given by[tex]
\mathbf{X} = \begin{bmatrix}
x \sinh gt \\
x \cosh gt \\
\eta + vt
\end{bmatrix}
[/tex]So
[tex]

\mathrm{d}\mathbf{X}
=
\begin{bmatrix}
gx \cosh gt \\
gx \sinh gt \\
v
\end{bmatrix} \mathrm{d}t
+
\begin{bmatrix}
\sinh gt \\
\cosh gt \\
0
\end{bmatrix} \mathrm{d}x
+
\begin{bmatrix}
0 \\
0 \\
1
\end{bmatrix} \mathrm{d} \eta
[/tex][tex]
\mathrm{d}\mathbf{X}
=
\begin{bmatrix}
gx \cosh gt \\
gx \sinh gt \\
v
\end{bmatrix} \mathrm{d}t
+
\begin{bmatrix}
\sinh gt \\
\cosh gt \\
0
\end{bmatrix} \mathrm{d}x
+
\left(
\frac{gx}{g^2x^2-v^2}
\begin{bmatrix}
v \cosh gt \\
v \sinh gt \\
gx
\end{bmatrix}
-
\frac{v}{g^2x^2-v^2}
\begin{bmatrix}
gx \cosh gt \\
gx \sinh gt \\
v
\end{bmatrix}
\right)
\mathrm{d} \eta
[/tex][tex]
\mathrm{d}\mathbf{X}
=
\begin{bmatrix}
gx \cosh gt \\
gx \sinh gt \\
v
\end{bmatrix}
\left( \mathrm{d}t - \frac{v \, \mathrm{d} \eta}{g^2x^2-v^2} \right)
+
\begin{bmatrix}
\sinh gt \\
\cosh gt \\
0
\end{bmatrix} \mathrm{d}x
+
\begin{bmatrix}
v \cosh gt \\
v \sinh gt \\
gx
\end{bmatrix}
\left( \frac{gx \, \mathrm{d} \eta}{g^2x^2-v^2} \right)
[/tex]Edit: there is an error in what follows. Please ignore and read a post corrected lower down which continues from this point.In the above equation note that the three vectors are mutually orthogonal, the first is timelike and the other two are spacelike, therefore we can read off[tex]
ds^2 = \left( g^2x^2-v^2 \right)
\left( \mathrm{d}t - \frac{v \, \mathrm{d} \eta}{g^2x^2-v^2} \right)^2
- \mathrm{d}x^2
- \left( \frac{gx}{g^2x^2-v^2} \right)^2 \, \mathrm{d} \eta^2
[/tex]Not only that, but the first vector is parallel to the congruence of "block" worldlines (obtained by putting [itex]\mathrm{d}x = \mathrm{d} \eta = 0 [/itex]), and the other two vectors are orthogonal to the congruence and the two vectors' magnitudes are independent of [itex]t[/itex]. Therefore we can say that the metric for the quotient manifold that represents stationary "space" according to a "block" observer is [tex]
ds^2 = \mathrm{d}x^2 + \left( \frac{gx}{g^2x^2-v^2} \right)^2 \, \mathrm{d} \eta^2
[/tex]
If you want to take this a step further and find some isotropic coordinates, by my calculation (details omitted here), you can perform the substitution[tex]
\begin{align*}
h &= \exp \left( \tfrac{1}{2} g^2x^2 \right) \, x^{-v^2} \, \cos g \eta \\
k &= \exp \left( \tfrac{1}{2} g^2x^2 \right) \, x^{-v^2} \, \sin g \eta \\
\end{align*}
[/tex]and get, I think,[tex]
ds^2 = \left( \frac{gx \, \exp \left( -\tfrac{1}{2} g^2x^2 \right) \, x^{v^2}}{g^2x^2-v^2} \right)^2
\left( \mathrm{d}h^2 + \mathrm{d}k^2 \right)
[/tex]
It's possible I've made a mistake in my calculation, but I think the method is correct.

Finally, as a sanity check, along a worldline of the congruence, putting [itex]\mathrm{d}x = \mathrm{d} \eta = 0 [/itex] we get[tex]
\frac{\mathrm{d}\mathbf{X}}{\mathrm{d}t}
=
\begin{bmatrix}
gx \cosh gt \\
gx \sinh gt \\
v
\end{bmatrix}
[/tex]so the 4-velocity is the unit vector[tex]
\frac{\mathrm{d}\mathbf{X}}{\mathrm{d}\tau}
=
\frac{1}{\sqrt{g^2x^2-v^2}}
\begin{bmatrix}
gx \cosh gt \\
gx \sinh gt \\
v
\end{bmatrix}
[/tex]in which the [itex]Y[/itex]-component is time-independent, as it ought to be (for conservation of the [itex]Y[/itex]-component of 4-momentum).
 
Last edited:
  • Like
Likes SlowThinker
  • #157
DrGreg said:
[tex]
ds^2 = \left( g^2x^2-v^2 \right)
\left( \mathrm{d}t - \frac{v \, \mathrm{d} \eta}{g^2x^2-v^2} \right)^2
- \mathrm{d}x^2
- \left( \frac{gx}{g^2x^2-v^2} \right)^2 \, \mathrm{d} \eta^2
[/tex]
It would make more sense if there was an additional ##\left( g^2x^2-v^2 \right)## factor at the last term. In fact it seems it is used in the subsequent calculation?

Other than that, it's pretty amazing, I think I almost get it :biggrin:
 
  • #158
SlowThinker said:
It would make more sense if there was an additional ##\left( g^2x^2-v^2 \right)## factor at the last term. In fact it seems it is used in the subsequent calculation?

Other than that, it's pretty amazing, I think I almost get it :biggrin:
Oops, I think you are right, which invalidates much of what follows. Stand by for a correction that I will issue shortly...
 
  • #159
There was an error in my previous long post, the final paragraphs should read as follows...

Edit: this is still wrong; see post #164

In the above equation note that the three vectors are mutually orthogonal, the first is timelike and the other two are spacelike, therefore we can read off[tex]
ds^2 = \left( g^2x^2-v^2 \right)
\left( \mathrm{d}t - \frac{v \, \mathrm{d} \eta}{g^2x^2-v^2} \right)^2
- \mathrm{d}x^2
- g^2x^2 \, \mathrm{d} \eta^2
[/tex]Not only that, but the first vector is parallel to the congruence of "block" worldlines (obtained by putting [itex]\mathrm{d}x = \mathrm{d} \eta = 0 [/itex]), and the other two vectors are orthogonal to the congruence and the two vectors' magnitudes are independent of [itex]t[/itex]. Therefore we can say that the metric for the quotient manifold that represents stationary "space" according to a "block" observer is [tex]
ds^2 = \mathrm{d}x^2 + g^2x^2 \, \mathrm{d} \eta^2
[/tex]
If you want to take this a step further and find some isotropic coordinates, by my calculation (details omitted here), you can perform the substitution[tex]
\begin{align*}
h &= x \, \cos g \eta \\
k &= x \, \sin g \eta \\
\end{align*}
[/tex]and get[tex]
ds^2 = \mathrm{d}h^2 + \mathrm{d}k^2
[/tex]So the quotient space is just flat Euclidean space in which [itex](x, g\eta)[/itex] are polar coordinates.

Finally, as a sanity check, along a worldline of the congruence, putting [itex]\mathrm{d}x = \mathrm{d} \eta = 0 [/itex] we get[tex]
\frac{\mathrm{d}\mathbf{X}}{\mathrm{d}t}
=
\begin{bmatrix}
gx \cosh gt \\
gx \sinh gt \\
v
\end{bmatrix}
[/tex]so the 4-velocity is the unit vector[tex]
\frac{\mathrm{d}\mathbf{X}}{\mathrm{d}\tau}
=
\frac{1}{\sqrt{g^2x^2-v^2}}
\begin{bmatrix}
gx \cosh gt \\
gx \sinh gt \\
v
\end{bmatrix}
[/tex]in which the [itex]Y[/itex]-component is time-independent, as it ought to be (for conservation of the [itex]Y[/itex]-component of 4-momentum).Thanks to @SlowThinker for rapidly finding the error in my orginal version. This version is much simpler, more credible, and makes more sense. It's also a little surprising as I wasn't expecting the quotient space to turn out flat. (Unless I've made another mistake...)
 
Last edited:
  • #160
SlowThinker said:
Pervect said something like

So I was wondering how that could work. I could imagine some process of constructing spacelike geodesics from the floor up and then measuring the distance between the resulting points, but it seems like a lot of work, even if I knew how to do it.
Plus, the "up direction" is probably under-defined: in your metric perhaps the ##-\tau## direction is the right one, but I'm not so sure about Pervect's.So it's more like "you need a metric and a transformation"?

I wanted the transformation to "avoid a lot of work". In this particular case, one could, in theory at least, envision using the metric to determine the readings of a virtual "inertial guidance system", mathematical computations which would give you both the linear and rotational accelerations around 3 spatial axes, a total of 6 acceleration components. . This information would be encoded in the Christoffel symbols. If the virtual "inertial guidance system" gave the same readings, the path followed by the observer at the coordinate origin should be the same too. However, while I know what Christoffel symbols correspond to linear and rotational acceleration in my metric (it's derived in MTW), it's not terribly clear to me how to do the same derivation in Peter's metric, it doesn't follow the conventions used in my textbook so I can't apply the textbook results directly. Actually, I could probably take a pretty good guess, but since it would still be a guess, it wouldn't serve the purposes of convincing anyone of anything. So it was much easier and more productive to ask for the already known generating transformation.

The other point you make is a good one. Suppose you have a flat piece of paper. You know the spatial metric is dx^2 + dy^2. But that doesn't change if you rotate the paper, so you don't know whether the x-axis is pointing "up" or "to the right" just given the metric. But you do know that the distance between any two points on the paper is ##\sqrt{\Delta x^2 + \Delta y^2}##, regardless of which way the x-axis points.
 
  • #161
DrGreg said:
A point in the block is given by
$$
\mathbf{X} = \begin{bmatrix} x \sinh gt \\ x \cosh gt \\ \eta + vt \end{bmatrix}
$$

Comparing this with my post #68, which has ##t = \gamma \left( \tau + v \psi \right)##, ##x = \chi##, and ##y = \gamma \left( \psi + v \tau \right)##, it looks like your ##\eta## is just ##\psi / \gamma##, i.e., you've just labeled the points in the block along the ##y## direction with a parameter that is scaled by a factor of ##\gamma## compared to mine. However, I think this may only be true on the bottom of the block, where ##gx = 1##. See below.

DrGreg said:
$$
\mathrm{d}\mathbf{X} = \begin{bmatrix} gx \cosh gt \\ gx \sinh gt \\ v \end{bmatrix} \left( \mathrm{d}t - \frac{v \, \mathrm{d} \eta}{g^2x^2-v^2} \right) + \begin{bmatrix} \sinh gt \\ \cosh gt \\ 0 \end{bmatrix} \mathrm{d}x + \begin{bmatrix} v \cosh gt \\ v \sinh gt \\ gx \end{bmatrix} \left( \frac{gx \, \mathrm{d} \eta}{g^2x^2-v^2} \right)
$$

When these three basis vectors are normalized to be unit vectors, the first and second appear to be the same as ##\hat{e}_0## and ##\hat{e}_1## from my post #68. (My ##\hat{e}_0## is also the 4-velocity that pervect found.) The third vector above, when normalized, is not, however, the same as my ##\hat{e}_2##, which in your notation would be

$$
\hat{e}_2 = \frac{1}{\sqrt{g^2 x^2 - v^2}} \begin{bmatrix} gxv \cosh gt \\ gxv \sinh gt \\ 1 \end{bmatrix}
$$

On the bottom of the block, where ##gx = 1##, the two basis vectors match; but for other values of ##x## (my ##\chi##), they don't. Your basis vector is clearly "nicer" in that, as you say, it remains orthogonal to the other two everywhere, not just where ##gx = 1##. However, that raises a question: why didn't I get the same vector for ##\hat{e}_2## in post #68 as you got above? My vector ##\mathbf{X}## there was

$$
\mathbf{X} = \begin{bmatrix} \chi \sinh g \gamma \left( \tau + v \psi \right) \\ \chi \cosh g \gamma \left( \tau + v \psi \right) \\ \gamma v \tau + \gamma \psi \end{bmatrix}
$$

which, after making the substitutions I gave above, gives exactly the same ##\mathbf{X}## as you got, not just on the bottom of the block where ##gx = 1##, but everywhere. But taking ##\partial_{\psi}## of the above and normalizing gives my ##\hat{e}_2##, not your third basis vector.

I think the answer is that, when taking derivatives to obtain your basis vectors, you assumed that neither of the first two components of your ##\mathbf{X}## were functions of ##\eta##, whereas it's obvious that all three components of my ##\mathbf{X}## are functions of ##\psi##. I'm not sure how to resolve the apparent discrepancy implied by all of this.
 
  • #162
DrGreg said:
therefore we can read off
$$
ds^2 = \left( g^2x^2-v^2 \right) \left( \mathrm{d}t - \frac{v \, \mathrm{d} \eta}{g^2x^2-v^2} \right)^2 - \mathrm{d}x^2 - g^2x^2 \, \mathrm{d} \eta^2
$$

If we expand this out, we get

$$
ds^2 = \left( g^2x^2-v^2 \right) \mathrm{d}t^2 - 2 v \mathrm{d}t \mathrm{d}\eta - \left( g^2 x^2 - \frac{v^2}{g^2x^2 - v^2} \right) \mathrm{d} \eta^2 - \mathrm{d}x^2
$$

If we use the definitions for my ##\tau##, ##\chi##, and ##\psi## to convert this into an expression in my coordinate chart, I think it comes out the same as what I gave in post #79.
 
  • #163
DrGreg said:
the quotient space is just flat Euclidean space in which ##(x, g\eta)## are polar coordinates.

I see the formal analogy here, but I'm not sure if I agree with the physical interpretation. The coordinate ##\eta## is not periodic, as ##\theta## is in polar coordinates; we don't go back to the same point on the block if we go from ##\eta = 0## to ##\eta = 2 \pi## or some other positive constant. But that periodic property is what makes the polar coordinates ##(r, \theta)## a valid alternate representation of a Euclidean plane.
 
  • #164
Oops again. Not my lucky day.

In my haste to correct my error in post #156, I overcorrected in post #159 and still got it wrong. I now think the correct answer for the quotient space metric should be [tex]
\mathrm{d}s^2 =
\mathrm{d}x^2
+ \frac{g^2x^2}{g^2x^2-v^2} \, \mathrm{d} \eta^2
[/tex]
That can be made isometric but it's a really ugly and complicated expression, so I won't bother here.
 
  • #165
DrGreg said:
I now think the correct answer for the quotient space metric should be
$$
\mathrm{d}s^2 = \mathrm{d}x^2 + \frac{g^2x^2}{g^2x^2-v^2} \, \mathrm{d} \eta^2
$$

Expanding the entire metric out would then change what I posted in post #163 to

$$
\mathrm{d}s^2 = \left( g^2 x^2 - v^2 \right) \mathrm{d}t^2 - 2 v \mathrm{d}t \mathrm{d}\eta - \mathrm{d}\eta^2 - \mathrm{d}x^2
$$

I'll have to go back and recheck my computation of how that transforms into my ##\tau##, ##\chi##, ##\psi## coordinates.
 
  • #166
The "simpler" approach is confusing me greatly. Do we have a final, corrected, proposed line element for the 4-d metric in "observer" coordinates to check? Even better would be both the 4-d line-element and the transform that give the value of Minkowskii coordinates as a function of "observer" coordinates. Additional useful information would be [change] what values of the observer coordinates make the line element diagonal and non-singular, assuming there are some. This would be what I'd call the "origin" of the coordinate system, while I put it at (0,0), that seems to be the exception rather than the rule in this thread.
 
  • #167
pervect said:
Do we have a final, corrected, proposed line element for the 4-d metric in "observer" coordinates to check?

What we have, as far as I can tell, are three proposed coordinate charts and associated line elements: (1) mine, (2) yours, and (3) DrGreg's. Here are brief descriptions of how it looks to me like those three charts and line elements were derived, and their key properties:

(1) My approach was to take the transform from Minkowski ##T, X, Y## to Rindler ##t, x, y## coordinates, ##T = x \sinh gt##, ##X = x \cosh gt##, and "boost" it in the ##y## direction with velocity ##v##. By "boost" here I mean defining new coordinates ##\bar{\tau}, \bar{\psi}## using the ansatz ##t = \gamma \left( \bar{\tau} + v \bar{\psi} \right)## and ##y = \gamma \left( v \bar{\tau} + \bar{\psi} \right)##. I defined ##\bar{\chi} = x## as a third coordinate just for clarity. I then derived a line element and a set of normalized coordinate basis vectors ##\hat{e}_0##, ##\hat{e}_1##, ##\hat{e}_2##; those three vectors are each in "coordinate" directions ##\partial_{\bar{\tau}}##, ##\partial_{\bar{\chi}}##, ##\partial_{\bar{\psi}}##, but ##\hat{e}_0## and ##\hat{e}_2## are not, in general, orthogonal (though ##\hat{e}_1## is orthogonal to both).

The key property that this chart shares with Rindler coordinates is that the ##\bar{\chi}## direction is the direction of proper acceleration, and surfaces of constant ##\chi## are surfaces of constant "altitude" in the rocket/block. However, the spatial part of this metric is not Euclidean.

(2) Your approach was to derive Fermi normal coordinates centered on the worldline of the bottom center of the block (i.e., the center of the bottom surface of the block, the surface that is in contact with the floor of the rocket), with just one change, that you allowed the spatial basis vectors to rotate instead of being Fermi-Walker transported. You obtained coordinates ##\tau, \chi, \psi## with the key property that the spatial part of the metric in this chart is Euclidean, as it must be for a Fermi normal chart (since all of the effects of acceleration and rotation are put into the terms involving ##d\tau##).

The 4-velocity of observers at rest in this chart is the same as that of observers at rest in mine, so both charts describe the same congruence of worldlines "at rest" in the chart, but with different parameterizations. The direction of proper acceleration in this chart is a mixture of the ##\chi## and ##\psi## directions, and surfaces of constant "altitude" in this chart are explicitly curved.

(3) DrGreg's approach was to start with Rindler ##t, x, y## coordinates, and simply define a new coordinate ##\eta## such that ##y = \eta + v t##, leaving ##t## and ##x## unchanged. The ##\eta## coordinate is then obviously just a parameter labeling points along the block according to their ##y## coordinate at time ##t =0## in the Rindler chart. DrGreg then found three basis vectors, the first two of which are the same as my ##\hat{e}_0## and ##\hat{e}_1## (and therefore the 4-velocity of observers at rest in his chart is the same as for ours, so all three charts give different parameterizations of the same congruence of worldlines). His third basis vector is different from my ##\hat{e}_2##, and I think it is also different from your ##\partial_{\phi}## (which is a unit vector in your chart). But his third basis vector has the key property that it is always orthogonal to the other two.

DrGreg's ##t## coordinate is not equal to proper time even for the bottom center of the block (whereas our ##\bar{\tau}## and ##\tau## coordinates are). However, the spatial part of his metric is Euclidean (see post #165). Also, using his three basis vectors and the form of the line element he gave in terms of three cobasis 1-forms each multiplied by one of the basis vectors, the quotient space metric can be "read off", and is evidently not Euclidean (see post #164).

What does all this mean? First of all, since DrGreg's formulation is the only one that gives three orthonormal basis vectors everywhere, it is the only one that defines a true frame field, and therefore it seems to me to be the best candidate for a "block observer's frame". This is bolstered by the fact that it has both of two key properties that your and my formulations each only have one of: the direction of proper acceleration is always in his ##x## direction (and surfaces of constant ##x## are surfaces of constant "altitude"), and the spatial part of his metric is Euclidean. (I had speculated earlier in this thread that it was not possible to find a single chart with both of those properties; evidently I was wrong.)

However, the quotient space metric derived from his basis vectors is not Euclidean, which means that the "space seen by block observers" is not Euclidean; the Euclidean "space" that appears in his metric is really just a reparameterization of the Euclidean space seen by Rindler observers (who are not moving in the ##y## direction, perpendicular to their proper acceleration). This is analogous to the fact that in Born coordinates on a "rotating disk", the Euclidean spatial metric is the one seen by the non-rotating observer at the center of the disk, while the quotient space metric seen by the observers rotating with the disk is non-Euclidean.
 
  • #168
pervect said:
Even better would be both the 4-d line-element and the transform that give the value of Minkowskii coordinates as a function of "observer" coordinates.

DrGreg's formulation doesn't completely define "observer coordinates", because, while his ##x, \eta## are constant along observer worldlines, his ##t## is not the same as any observer's proper time, even on the reference worldline at the bottom center of the block. The obvious simple way to remedy that would be to rescale his ##t## coordinate so that it was the same as observer proper time on the reference worldline (and by extension everywhere on the floor of the rocket/bottom of the block, since his ##g_{tt}## only depends on ##x##). I'll try that out and see what happens.

However, DrGreg's formulation does define a frame field for "block observers"--his three basis vectors (plus the fourth ##\partial_z## vector). As I noted in my previous post, that is something that neither my nor your formulation did. And the frame field, physically, is really what we need in order to understand the physical experience of a "block observer".

pervect said:
Additional useful information would be [change] what values of the observer coordinates make the line element diagonal and non-singular, assuming there are some.

In DrGreg's formulation, there aren't any, because, as you can see from post #165, the coefficient of the ##dt d\eta## term is constant; it doesn't vanish anywhere. This actually makes sense, because the congruence of worldlines describing the block has nonzero vorticity everywhere; it is different in this regard from the "rotating disk" Langevin congruence, which has zero vorticity at the center of the disk. There is no point corresponding to an "axis of rotation" for the block.

pervect said:
This would be what I'd call the "origin" of the coordinate system, while I put it at (0,0), that seems to be the exception rather than the rule in this thread.

The simple reason for that is that both DrGreg and I started from Rindler coordinates, where the origin is on the Rindler horizon, not on the "reference" worldline--that worldline is characterized by ##gx = 1##, not ##x = 0##. You started from Fermi normal coordinates, where the spatial origin is on the reference worldline.

However, there is an underlying point here, which I just mentioned above. There is no natural "origin" for the block if we just look at the points in the block, because there is no "axis of rotation" for the block within the block--the congruence describing the block has nonzero vorticity everywhere. The "zero vorticity" altitude in the block would be at the Rindler horizon, since that is what corresponds to the "axis of rotation". That is why Rindler coordinates place the origin at the Rindler horizon--because that makes things look simplest from the "rotation" point of view.
 
  • #169
PeterDonis said:
Expanding the entire metric out would then change what I posted in post #163 to

$$
\mathrm{d}s^2 = \left( g^2 x^2 - v^2 \right) \mathrm{d}t^2 - 2 v \mathrm{d}t \mathrm{d}\eta - \mathrm{d}\eta^2 - \mathrm{d}x^2
$$

I'll have to go back and recheck my computation of how that transforms into my ##\tau##, ##\chi##, ##\psi## coordinates.
As a check that I haven't made any other errors, this can also be seen directly from my equation [tex]
\mathrm{d}\mathbf{X}
=
\begin{bmatrix}
gx \cosh gt \\
gx \sinh gt \\
v
\end{bmatrix} \mathrm{d}t
+
\begin{bmatrix}
\sinh gt \\
\cosh gt \\
0
\end{bmatrix} \mathrm{d}x
+
\begin{bmatrix}
0 \\
0 \\
1
\end{bmatrix} \mathrm{d} \eta
[/tex][tex]\implies
\mathrm{d}\mathbf{X}
=
\begin{bmatrix}
\cosh gt \\
\sinh gt \\
0
\end{bmatrix} gx \, \mathrm{d}t
+
\begin{bmatrix}
\sinh gt \\
\cosh gt \\
0
\end{bmatrix} \mathrm{d}x
+
\begin{bmatrix}
0 \\
0 \\
1
\end{bmatrix} \left( \mathrm{d} \eta + v \mathrm{d} t \right)
[/tex]which is another orthogonal decomposition, using the "Rindler frame" instead of my "block frame".

I agree with your commentary in posts #167 and #168. It was my objective to find the metric of the quotient space, which, in some senses, best represents the geometry of space (not spacetime). I've come across the quotient space for the Langevin congruence, and was aware it could be used whenever you can find a "stationary-but-not-static coordinate system", but I'd never seen any other practical example, and so was curious to make it work.

As you say, my ##t## coordinate doesn't really tie in very well with a "block observer's" proper time. Maybe it's possible to find a better time cooordinate without upsetting the quotient construction.
 
  • #170
DrGreg said:
Maybe it's possible to find a better time cooordinate without upsetting the quotient construction.

Well, the obvious ansatz is ##t = \gamma \tau##, where ##\gamma = 1 / \sqrt{1 - v^2}##, which gives for the line element

$$
ds^2 = \gamma^2 \left( g^2 x^2 - v^2 \right) \mathrm{d}\tau^2 - 2 \gamma v \mathrm{d}\tau \mathrm{d}\eta - \mathrm{d}\eta^2 - \mathrm{d}x^2
$$

This makes ##\tau## the same as proper time along the worldline of any observer on the bottom of the block/floor of the rocket, where ##gx = 1##. It still isn't the same elsewhere, but that is similar to the situation in Rindler coordinates, where ##t## only matches proper time on worldlines with ##gx = 1##.

I'm not sure how this affects the quotient space construction, though.
 
  • #171
PeterDonis said:
Well, the obvious ansatz is ##t = \gamma \tau##, where ##\gamma = 1 / \sqrt{1 - v^2}##, which gives for the line element

$$
ds^2 = \gamma^2 \left( g^2 x^2 - v^2 \right) \mathrm{d}\tau^2 - 2 \gamma v \mathrm{d}\tau \mathrm{d}\eta - \mathrm{d}\eta^2 - \mathrm{d}x^2
$$

This makes ##\tau## the same as proper time along the worldline of any observer on the bottom of the block/floor of the rocket, where ##gx = 1##. It still isn't the same elsewhere, but that is similar to the situation in Rindler coordinates, where ##t## only matches proper time on worldlines with ##gx = 1##.

I'm not sure how this affects the quotient space construction, though.
I think rescaling any of my coordinates by a constant shouldn't affect the method, so rescaling ##t## (and maybe also ##\eta##) by ##\gamma## (regarding ##v## as constant) should be OK and makes it more physically relevant at ##x = 1/g##.
 
  • #172
DrGreg said:
rescaling ##t## (and maybe also ##\eta##) by ##\gamma## (regarding ##v## as constant) should be OK and makes it more physically relevant at ##x = 1/g##.

I'm not sure ##\eta## should be rescaled. If we rearrange the line element with ##\tau## that I wrote, we get

$$
\mathrm{d} s^2 = \gamma^2 g^2 x^2 \mathrm{d} \tau^2 - \left( \gamma v \mathrm{d} \tau + d \eta \right)^2 - dx^2
$$

which puts all the ##\gamma## factors with the ##\mathrm{d} \tau## factors.
 
  • #173
PeterDonis said:
I'm not sure ##\eta## should be rescaled. If we rearrange the line element with ##\tau## that I wrote, we get

$$
\mathrm{d} s^2 = \gamma^2 g^2 x^2 \mathrm{d} \tau^2 - \left( \gamma v \mathrm{d} \tau + d \eta \right)^2 - dx^2
$$

which puts all the ##\gamma## factors with the ##\mathrm{d} \tau## factors.
A possible reason for rescaling ##\eta## would be that my quotient metric$$
\mathrm{d}s^2 =
\mathrm{d}x^2
+ \frac{g^2x^2}{g^2x^2-v^2} \, \mathrm{d} \eta^2
$$is$$
\mathrm{d}s^2 =
\mathrm{d}x^2
+ \gamma^2 \mathrm{d} \eta^2
$$ locally wherever ##gx=1##.
 
  • #174
DrGreg said:
A possible reason for rescaling ##\eta## would be that my quotient metric
$$
\mathrm{d}s^2 = \mathrm{d}x^2 + \frac{g^2x^2}{g^2x^2-v^2} \, \mathrm{d} \eta^2
$$
is
$$
\mathrm{d}s^2 = \mathrm{d}x^2 + \gamma^2 \mathrm{d} \eta^2
$$
locally wherever ##gx=1##.

So if we define ##\psi = \gamma \eta##, then the quotient space metric becomes

$$
\mathrm{d}s^2 = \mathrm{d}x^2 + \frac{g^2x^2 \left( 1 - v^2 \right)}{g^2x^2 - v^2} \, \mathrm{d} \psi^2
$$

and the full metric becomes

$$
\mathrm{d}s^2 = \frac{g^2 x^2 - v^2}{1 - v^2} \mathrm{d}\tau^2 - 2 v \mathrm{d}\tau \mathrm{d}\psi - \left( 1 - v^2 \right) \mathrm{d}\psi^2 - \mathrm{d}x^2
$$

This still factors into something fairly similar to what I had before:

$$
\mathrm{d}s^2 = \gamma^2 g^2 x^2 \mathrm{d}\tau^2 - \left( \gamma v \mathrm{d}\tau + \frac{1}{\gamma} \mathrm{d}\psi \right)^2 + \mathrm{d}x^2
$$
 
  • #175
pervect said:
[QUOTE="PeterDonis, post: 5274110, member: 197831"

$$
\mathrm{d}s^2 = \frac{g^2 x^2 - v^2}{1 - v^2} \mathrm{d}\tau^2 - 2 v \mathrm{d}\tau \mathrm{d}\psi - \left( 1 - v^2 \right) \mathrm{d}\psi^2 - \mathrm{d}x^2
$$

What I see here is a metric where ##g_{\tau\psi}=v## is never zero at any point, so that ##\partial_\tau## is never orthogonal to ##\partial_\psi## because the dot product of the vectors ##\partial_\tau## and ##\partial_\psi## is not zero as it would need to be for them to be orthogonal

[add]
I.e. if we denote the dual vector to ##\partial_t## as dt, and the dual vector to ##\partial_\psi## as ##d\psi##, the only term in the metric that contributes to the dot product is the ##dt\,d\psi## term, since the product of the vector ##\partial_\mu## and the one form ##d \nu## is the kronecker delta ##\delta^\mu_\nu##
 

Similar threads

Back
Top