Transformation of an acceleration vector under a basis change

In summary, the conversation discusses the use of co-basis frame fields in the stationary frame of the Schwarzschild spacetime and the calculation of the 4-velocity and 4-acceleration of a stationary observer in this frame. The conversation then delves into the application of a boost in the r-direction, which is equivalent to a transformation from Schwarzschild to Painleve coordinates. However, there is disagreement among the participants about the validity of this boost and its effect on the metric. One participant suggests that the 4-acceleration of a Painleve observer is zero, while another points out that the boost may only affect the 4-acceleration of the observer whose 4-velocity covector is used in the
  • #1
Mentz114
5,432
292
This thread is spawned from an earlier one
https://www.physicsforums.com/showthread.php?t=647147&page=7

For the stationary ( ie comoving ) frame in the Schwarzschild spacetime the co-basis of the frame field is
[tex]
s_0= \sqrt{\frac{r-2m}{r}}dt,\ \ s_1=\sqrt{\frac{r}{r-2m}}\ dr,\ \ s_2=r\ d\theta,\ \ s_3=r\sin(\theta)\ d\phi
[/tex]
The 4-velocity of the stationary observer in the local frame is [itex]u^\mu=\partial_t[/itex] (or [itex](1,0,0,0)[/itex]).

This, [itex]u^\nu\nabla_\mu u_\nu[/itex], which looks like a covariant vector is
[tex]
a_\mu= \frac{m}{{r}^{\frac{3}{2}}\,\sqrt{r-2\,m}} \ dr
[/tex]
All this is well known. Now we boost the co-basis covectors in the r-direction with velocity [itex]-\sqrt{2m/r}[/itex]. The metric is unchanged in form by this. This gives a new basis h
[tex]
h_0= -dt - \frac{\sqrt{2mr}}{r-2m}\ dr,\ \ h_1=\sqrt{\frac{2m}{r}}\ dt + \frac{r}{r-2m} \ dr,\ \ h_2=s_2,\ \ h_3=s_3
[/tex]
According to my calculations, in this basis the acceleration aµ is now zero. Readers are bound to be sceptical about my calculations but I'm very confident there's been no gross error. If it is an error I'll be happy to have found it.
 
Physics news on Phys.org
  • #2
Mentz114 said:
Now we boost the co-basis covectors in the r-direction with velocity [itex]-\sqrt{2m/r}[/itex]. The metric is unchanged in form by this.
I am highly skeptical of this claim. Have you tried actually working out the metric in the new coordinates?
 
  • #3
He should be right. The metric is indifferent to rotational degrees of freedom (and boosts are "rotations"). Nevertheless, it should be intuitive that a uniform boost of a vector should not change the magnitude of the vector. That said, I'm aware that intuitive results are not necessarily always right.

One thing I'm curious about: why compute the acceleration covector, rather than the acceleration vector?
 
  • #4
Mentz114 said:
Now we boost the co-basis covectors in the r-direction with velocity [itex]-\sqrt{2m/r}[/itex]. The metric is unchanged in form by this.

This boost is equivalent to a transformation from Schwarzschild to Painleve coordinates. This does *not* leave the metric unchanged. [Edit: Actually you can, if you want, do the calculation in the same coordinates; but in that case the physical meaning of the boost is obviously that you are changing observers. So in any case my following comment stands:] Basically what you are doing is showing that the 4-acceleration of a Painleve observer is zero; you are *not* showing that the 4-acceleration of a static observer changes when you transform coordinates.

The Wikipedia page on frame fields in GR has some helpful information:

http://en.wikipedia.org/wiki/Frame_fields_in_general_relativity

It uses the term "Lemaitre observers" for what I'm calling Painleve observers.

Muphrid said:
He should be right. The metric is indifferent to rotational degrees of freedom (and boosts are "rotations").

The metric is invariant under *spatial* rotations. It is *not* invariant under space-time rotations, i.e., boosts.
 
Last edited:
  • #5
Mentz114 said:
This, [itex]u^\nu\nabla_\mu u_\nu[/itex], which looks like a covariant vector is
[tex]
a_\mu= \frac{m}{{r}^{\frac{3}{2}}\,\sqrt{r-2\,m}} \ dr
[/tex]

I'm still working through calculations, but this looks wrong; what you've written looks like the 4-acceleration vector [itex]a^\mu[/itex], not the 4-acceleration covector [itex]a_\mu[/itex]. Remember that in order to compute [itex]u^\mu \nabla_\mu[/itex] you need the 4-velocity *vector* (which you didn't write down in your post), not the covector (which you did write down).
 
  • #6
Thanks for the replies. I'll try to answer the questions but I think now that this is correct.

PeterDonis said:
This boost is equivalent to a transformation from Schwarzschild to Painleve coordinates. This does *not* leave the metric unchanged. Basically what you are doing is showing that the 4-acceleration of a Painleve observer is zero; you are *not* showing that the 4-acceleration of a static observer changes when you transform coordinates.

@DaleSpam, you asked if I'd worked out the new metric. ?
The metric given by [itex]g=-h_0\otimes h_0 + h_1\otimes h_1 + h_2\otimes h_2 + h_3\otimes h_3 [/itex] is the Schwarzschild metric
 
Last edited:
  • #7
PeterDonis said:
I'm still working through calculations, but this looks wrong; what you've written looks like the 4-acceleration vector [itex]a^\mu[/itex], not the 4-acceleration covector [itex]a_\mu[/itex]. Remember that in order to compute [itex]u^\mu \nabla_\mu[/itex] you need the 4-velocity *vector* (which you didn't write down in your post), not the covector (which you did write down).
This [itex]u^\mu \nabla_\mu[/itex] is not the acceleration ( it's the expansion scalar ). The acceleration is [itex]u^\nu\nabla_\nu u_\mu[/itex] which has one free covariant index.

The velocity vector is (1,0,0,0) and the covector is (-1,0,0,0) so uμuμ = -1.
 
  • #8
I don't see why you're using the covariant velocity instead of the contravariant. Isn't it usual to use the contravariant acceleration/velocity?

PeterDonis said:
The metric is invariant under *spatial* rotations. It is *not* invariant under space-time rotations, i.e., boosts.

I don't follow. The whole point of using a metric instead of frame fields is that it removes all six degrees of generalized rotation freedom (i.e. 3 degrees of boost freedom and 3 degrees of spatial rotation freedom).
 
Last edited:
  • #9
Mentz114 said:
This [itex]u^\mu \nabla_\mu[/itex] is not the acceleration ( it's the expansion scalar ).

No, it isn't. It's the directional derivative operator along the 4-velocity [itex]u^\mu[/itex]. It's a scalar, yes, since it contracts the 4-velocity, a vector, with the covariant derivative operator, a covector. The point I was making is that it's the 4-velocity *vector* that appears in it; you only wrote down the *covector*, so I'm not sure what 4-velocity vector components you are using to compute the operator [itex]u^\mu \nabla_\mu[/itex].

Mentz114 said:
The velocity vector is (1,0,0,0) and the covector is (-1,0,0,0) so uμuμ = -1.

No, they aren't. I didn't notice this before, but in looking through the OP, I see that you made the same mistake there. The 4-velocity is a unit vector: (1, 0, 0, 0) is not a unit vector unless r -> infinity (i.e,. unless the metric is Minkowski). For the original coframe s that you wrote down, [itex]s_0[/itex] is the 4-velocity covector (and its corresponding frame vector [itex]s^0[/itex] is the 4-velocity vector). For the boosted coframe you wrote down, you have to rewrite [itex]s_0[/itex] in that frame if you want to express the 4-velocity of a static observer in that coframe (and similarly you have to express [itex]s^0[/itex] in the corresponding frame). What you actually did was (more or less) to compute the 4-acceleration of an observer whose 4-velocity covector is [itex]h_0[/itex], which is a *different* 4-velocity, that of a Painleve observer.
 
  • #10
Muphrid said:
I don't follow. The whole point of using a metric instead of frame fields is that it removes all six degrees of generalized rotation freedom (i.e. 3 degrees of boost freedom and 3 degrees of spatial rotation freedom).

I think you're misunderstanding what metrics and frame fields are. They both express the same physics and the same "degrees of freedom", just in different forms. A metric (by which I think you actually mean a "line element") expresses the physics in terms of a coordinate chart and the basis vectors (or covectors) of that chart. A frame field expresses the physics in terms of the basis vectors (or covectors) carried by a particular family of observers as they travel along their worldlines. There is the same amount of freedom in either form.

Also, whether or not a metric is invariant under a particular set of transformations depends on the specific spacetime geometry under discussion. Schwarzschild spacetime is spherically symmetric, so the metric is invariant under spatial rotations. There are other spacetimes that are not spherically symmetric (such as Kerr spacetime), and their metrics are not invariant under spatial rotations.
 
  • #11
PeterDonis said:
No, it isn't. It's the directional derivative operator along the 4-velocity [itex]u^\mu[/itex]. It's a scalar, yes, since it contracts the 4-velocity, a vector, with the covariant derivative operator, a covector. The point I was making is that it's the 4-velocity *vector* that appears in it; you only wrote down the *covector*, so I'm not sure what 4-velocity vector components you are using to compute the operator [itex]u^\mu \nabla_\mu[/itex].

No, they aren't. I didn't notice this before, but in looking through the OP, I see that you made the same mistake there. The 4-velocity is a unit vector: (1, 0, 0, 0) is not a unit vector unless r -> infinity (i.e,. unless the metric is Minkowski). For the original coframe s that you wrote down, [itex]s_0[/itex] is the 4-velocity covector (and its corresponding frame vector [itex]s^0[/itex] is the 4-velocity vector). For the boosted coframe you wrote down, you have to rewrite [itex]s_0[/itex] in that frame if you want to express the 4-velocity of a static observer in that coframe (and similarly you have to express [itex]s^0[/itex] in the corresponding frame). What you actually did was (more or less) to compute the 4-acceleration of an observer whose 4-velocity covector is [itex]h_0[/itex], which is a *different* 4-velocity, that of a Painleve observer.
Peter,
the metric is Minkowski. We are working in the local frame. I never calculate the scalar [itex]u^\mu \nabla_\mu[/itex]. I'm calculating the covariant derivative of the (co)vector and projecting in the direction of the vector. I used to write it as [itex]u_{\mu;\nu}u^\nu[/itex].

Does this clear up some of your questions ?

It occurs to me that tensors transform like tensors under holonomic transformations, ie we can write
[tex]
dx'^\mu = \frac{\partial x'^\mu}{\partial x^\mu}dx
[/tex]
and going from the coordinate basis to a frame basis is not holonomic.
 
Last edited:
  • #12
This way of doing things is all too modern for me. For me, 4 acceleration is absolute derivative of U along a path. For a constant r,theta,phi world line in SC coordinates this works out to be zero except for the r component which is:

(m/r^2 ) (1-2m/r)^-1

with a norm of: (m/r^2 )(1-2m/r)^(-3/2) [if i haven't made a stupid mistake somewhere].

So, what I thought was claimed was that there was some magic coordinate transform which would make this vector go to zero and its norm vanish, which is clearly impossible.
 
  • #13
Mentz114 said:
Peter,
the metric is Minkowski. We are working in the local frame.

Doesn't matter; in order to calculate the 4-acceleration of a static observer (or indeed of any observer), you have to know the connection coefficients, which means you have to know the actual metric (Schwarzschild), not just the approximate metric in the local frame. If the metric were really Minkowski, you could use the partial derivative operator [itex]\partial_\mu[/itex] instead of the covariant derivative operator [itex]\nabla_\mu[/itex] and simplify your formulas considerably.

Also, if the metric were Minkowski, the first two components of the coframe would not be what you wrote down; they would be (-dt, dr). The fact that you wrote down a different coframe means that you implicitly agree that the spacetime curvature affects the calculation.

Mentz114 said:
I never calculate the scalar [itex]u^\mu \nabla_\mu[/itex]. I'm calculating the covariant derivative of the (co)vector and projecting in the direction of the vector. I used to write it as [itex]u_{\mu;\nu}u^\nu[/itex].

That's fine, but you still have to know the vector components (not just the covector components) to do the projection. What vector components are you using to compute that?
 
  • #14
Mentz114 said:
going from the coordinate basis to a frame basis is not holonomic.

That's true, but you're not going from a coordinate basis to a frame basis. You're going from one frame basis to another frame basis. The first frame basis happens to have vectors pointing in the same direction as the coordinate basis vectors, but that doesn't make it a coordinate basis.
 
  • #15
PeterDonis said:
Doesn't matter; in order to calculate the 4-acceleration of a static observer (or indeed of any observer), you have to know the connection coefficients, which means you have to know the actual metric (Schwarzschild), not just the approximate metric in the local frame. If the metric were really Minkowski, you could use the partial derivative operator [itex]\partial_\mu[/itex] instead of the covariant derivative operator [itex]\nabla_\mu[/itex] and simplify your formulas considerably.
There's nothing approximate here. These are exact calculations. We have the (inverse) metric. It is encoded in the coframe cobasis vectors ( see the tensor product expression I give earlier ).

In the local frame the connection coefficients are Ricci rotation coefficients and they are used in calculating covariant derivs instead of the CS2's.

Also, if the metric were Minkowski, the first two components of the coframe would not be what you wrote down; they would be (-dt, dr). The fact that you wrote down a different coframe means that you implicitly agree that the spacetime curvature affects the calculation.
The global metric is in the coframe, as I said. The tetrad formed from the coframe basis projects the metric to the Minkowski (local) metric.

That's fine, but you still have to know the vector components (not just the covector components) to do the projection. What vector components are you using to compute that?

I stated both, uμ=(1,0,0,0) and uμ=(1,0,0,0).
 
  • #16
PeterDonis said:
That's true, but you're not going from a coordinate basis to a frame basis. You're going from one frame basis to another frame basis. The first frame basis happens to have vectors pointing in the same direction as the coordinate basis vectors, but that doesn't make it a coordinate basis.

Yes, the boost is also non-holonomic. I'm just thinking out loud.
 
  • #17
PAllen said:
This way of doing things is all too modern for me. For me, 4 acceleration is absolute derivative of U along a path. For a constant r,theta,phi world line in SC coordinates this works out to be zero except for the r component which is:

(m/r^2 ) (1-2m/r)^-1

with a norm of: (m/r^2 )(1-2m/r)^(-3/2) [if i haven't made a stupid mistake somewhere].

So, what I thought was claimed was that there was some magic coordinate transform which would make this vector go to zero and its norm vanish, which is clearly impossible.
Well, I can make it vanish by boosting a frame field. This effectively changes the local frame from an accelerating one to a geodesic one. Whatever is going on, I'm not making the components of the same tensor vanish - as you say, that's impossible.
 
  • #18
Mentz114 said:
Well, I can make it vanish by boosting a frame field. This effectively changes the local frame from an accelerating one to a geodesic one. Whatever is going on, I'm not making the components of the same tensor vanish - as you say, that's impossible.

Can you express this as a coordinate transform matrix? Such that I can apply it to the 4-acceleration I computed?

[edit: wait, I see you agree that can't be done. So I bow out because I have not studied frame fields.]
 
Last edited:
  • #19
Mentz114 said:
@DaleSpam, you asked if I'd worked out the new metric. ?
The metric given by [itex]g=-h_0\otimes h_0 + h_1\otimes h_1 + h_2\otimes h_2 + h_3\otimes h_3 [/itex] is the Schwarzschild metric
Hmm, I don't find that very helpful. I cannot even tell what coordinates you are using after your radial boost, and this expression doesn't make it clear to me at all that the form of the metric is unchanged in those coordinates.

Btw, do you intend to have a different boost at each r?
 
  • #20
PAllen said:
Can you express this as a coordinate transform matrix? Such that I can apply it to the 4-acceleration I computed?
I think I am with you here.
 
  • #21
DaleSpam said:
Hmm, I don't find that very helpful. I cannot even tell what coordinates you are using after your radial boost, and this expression doesn't make it clear to me at all that the form of the metric is unchanged in those coordinates.
I calculated that tensor product and the metric is unchanged. What more can I say. If you don't believe me, re-calculate it. It's a frame field so I'm working in local Minkowski coords when the acceleration is calculated.

Btw, do you intend to have a different boost at each r?
Yes, as I stated in the OP the boost is [itex]\sqrt{2m/r}[/itex]

Having thought a bit more about this, I don't think there's anything amiss. The static frame field is accelerating and will always be accelerating from any viewpoint. The boosted static frame is now moving and so is a different physical setup with a different acceleration vector which happens to be zero for the boost I chose. All observers will agree on this too. It just looks as if the same tensor is being considered because the math and the vectors look the same in the local frame. For me the mists have cleared.

Thanks for the responses.
 
Last edited:
  • #22
Let me try to cut through some of the confusion. Let there be a fundamental flat spacetime with basis vectors ##e_t, e_r, e_\phi, e_\theta##. These basis vectors need not be unit--in this case, ##e_\theta \cdot e_\theta = r^2## and ##e_\phi \cdot e_\phi = r^2 \sin^2 \theta##. Define a linear operator ##\underline h## such that

$$\underline h^{-1}(e_t) = (1 - 2M/r)^{1/2} e_t \equiv g_t\\
\underline h^{-1}(e_r) = (1- 2M/r)^{-1/2} e_r \equiv g_r\\
\underline h^{-1}(e_\theta) = e_\theta \equiv g_\theta\\
\underline h^{-1}(e_\phi) = e_\phi \equiv g_\phi$$

This linear operator goes by many names--frame field, displacement gauge field, etc. Let's just call it the h-field. The vectors ##g_\alpha## obey the relationship ##g_\alpha \cdot g_\beta = g_{\alpha \beta}##, so they are the actual coordinate basis vectors, and this gives us the metric in terms of the h-field. ##g_{\alpha \beta} = \underline g(e_\alpha) \cdot e_\beta = \underline h^{-1}(e_\alpha) \cdot \underline h^{-1}(e_\beta)##. Simplified, the metric is ##\underline g(s) = \overline h^{-1} \underline h^{-1}(s)##, for any vector ##s##.

So far so good? So far so good. Now, let us apply an operator ##\underline L## such that its adjoint is equal to its inverse--##\overline L = \underline L^{-1}##--to the h-field. This equally describes spatial rotations as well as Lorentz boosts. This operator may be position dependent. If ##\underline h \mapsto \underline L \underline h##, then the metric goes to

$$\underline g(s) = \underline h^{-1} \underline L^{-1} \overline L^{-1} \overline h^{-1}(s)$$

But again, the adjoint of ##\underline L## is equal to the inverse. The L's cancel, and you recover the original metric. This is what I meant when I said the metric is invariant under rotations and boosts. No rotation or boost to the h-field affects the metric.


Now then, we want to consider a four-velocity that is (edit) ##u = e_t##--this is the gauge-invariant velocity. (Edit: I'm actually a bit puzzled at this point. This implies the time component of the four-velocity in the coordinate basis is no longer unit.) We need the connection, which is ##\underline \omega(e_t) = \frac{M}{r^2} (1-2M/r)^{-1/2} e_{rt}##, so the acceleration is

$$a= u \cdot D u = u \cdot \overline h(\nabla) u + \underline \omega(u) \cdot u$$

I assume ##u## has no dependence on ##\tau##, so that the first term vanishes. Note that ##e_{rt} \cdot e_t = e_r## under this sign convention, so the result is

$$a = \frac{M}{r^2} (1-2M/r)^{-1/2}e_r$$

(Edit: stopping here, since I'm no longer sure of the conclusion that followed.)
 
Last edited:
  • #23
Muphrid, thanks, that is most informative. Although I'm new to this notation I can clearly follow what you're doing.

You're not doing what I was but you have shown that the acceleration for a certain frame field is a tensor and cannot be made to vanish under a boost. But I was calculating the acceleration for a certain h-field (h1 say). Then I boosted the h1-field to get h2 and - lo, I get a zero acceleration for h2. No problem because they are different h fields representing different physical setups.
 
Last edited:
  • #24
Well, it's possible I've made an error in believing that the acceleration has the same transformation law as the inverse h-field. The most rigorous way would be to recalculate the connection ##\underline \omega## for the new h-field and see how that changes the acceleration.

So, to verify things, I would want to figure out the transformation of the connection ##\underline \omega## under this boost. I'm poring over my resources--I think, because this boost is not position dependent, the ##\underline \omega## field transforms by either a simple boost or perhaps by a boost of itself and a boost of its argument. I'm going to have to wade through the material a bit more.

But as far as the different h-fields representing different setups, I disagree in one respect. No matter what you do--apply boosts/rotations or various coordinate system changes--the h-field either can or cannot be transformed to the identity. If it can't, I think there is intrinsic information about the system contained in the h-field, information that doesn't go away based on coordinate-system transformations or boosts and rotations. But this is a point of interpretation, not really relevant to the question at hand.

Once we know how the connection transforms, it will be clear what the acceleration should be.

Regardless, though, the benefit of working with these ##e_\alpha## running around is that the acceleration and velocity should be invariants regardless of h-field. It is the components, when evaluated with respect to different h-fields (different coordinate basis vectors ##g_\alpha##), that should change.

Now, that said, it's clear that you weren't looking at the gauge invariant acceleration (which is what my ##a## is), but the components according to a set of coordinate basis vectors.

So if we take our gauge-invariant acceleration ##a## and extract components ##a \cdot g^\mu## for some choice of ##g^\mu## (some choice of h-field), can we make the radial acceleration vanish? Just kinda doing the h-field matrix inversion in my head here, let's say the coordinate-basis covectors are ##g^t = K \gamma (e^t - \beta e^r)## and ##g^r = K^{-1} \gamma (e^r - \beta e^t)## for ##K = \sqrt{1-2M/r}## (it might be 1/that, but it gets the point across).

The components in the coordinate basis are then

$$\begin{align*}
a^t &= -\frac{M}{r^2} K \gamma \beta\\
a^r &= \frac{M}{r^2} K^{-1} \gamma
\end{align*}$$

Hm, that would seem to indicate it's not possible to reduce these four-accleration components to zero. It's possible I'm just screwing something up royally, considering the time of night. The only way I can see, right now, that the components of acceleration could vanish in some coordinate frame is if the gauge-invariant acceleration ##a## had two terms, one in ##e_r## and the other in ##e_t##. Then the required cancellation could appear. This might be the case if I improperly calculated ##a## earlier.

Edit: I think I found my error. I constructed the gauge-invariant velocity incorrectly. Fixed some things, but I'll have to look at this with fresh eyes in the morning.
 
Last edited:
  • #25
PAllen said:
This way of doing things is all too modern for me. For me, 4 acceleration is absolute derivative of U along a path. For a constant r,theta,phi world line in SC coordinates this works out to be zero except for the r component which is:

(m/r^2 ) (1-2m/r)^-1

with a norm of: (m/r^2 )(1-2m/r)^(-3/2) [if i haven't made a stupid mistake somewhere].

So, what I thought was claimed was that there was some magic coordinate transform which would make this vector go to zero and its norm vanish, which is clearly impossible.

I did make a stupid mistake above. Fixing algebra:

r component of 4-acceleration is simply: m/r^2.
proper acceleration (norm) is simply: (m/r^2) (1-2m/r)^(-1/2)
 
  • #26
Okay, so, I took a minute to try to unknot my confusion. I think I can correctly establish the framework for doing things now. Possibly.

At any given point, there should be a local orthogonal frame of basis vectors ##e_\alpha##, and measurements at this point are made with respect to this basis. There may be, for example, a four-velocity ##u = u^\alpha e_\alpha##, but under changes of h-field, the components would change (these changes represent rotations, position-dependent coordinate transformations, and so on).

It's useful, however, to talk about a gauge-invariant four-velocity ##\tilde u = \underline h^{-1}(u)##. A frame that measures different components ##{u'}^\alpha## must have a different h-field ##\underline h'## such that ##\underline h^{-1}(u) = {\underline h'}^{-1}(u') = \tilde u##.

We notice that ##\tilde u = u^\alpha g_\alpha = {u'}^\alpha {g'}_\alpha##, but ##u = u^\alpha e_\alpha## and ##u' = {u'}^\alpha e_\alpha##. This means the ##e_\alpha## are convenient to use.

So, the ##g^\alpha## are coordinate basis vector fields, which can be expressed in terms of the local orthogonal frame vectors. Any change of coordinates results in new coordinate basis vector fields ##{g'}^\alpha##, which can still be expressed in terms of the local orthogonal basis vectors. To do otherwise--expressing the local frame in terms of the coordinate basis--rapidly gets confusing. Or at least, it rapidly confuses me.

The original post posits that the four-velocity in the local frame ##u = e_t##, I think. There may be a problem here, as then the gauge-invariant velocity ##\tilde u## no longer obeys ##|\tilde u \cdot \tilde u| = 1##, which it should. This is the same as saying ##|\underline h^{-1}(u) \cdot \underline h^{-1}(u)| = |\underline g(u) \cdot u| = 1##, which I think is pretty sound.

Beyond that, the rest of the calculation should fall out from taking the omega field as Lorentz covariant (it is otherwise invariant to changes in the h-field, as you'd expect).
 
  • #27
Mentz114 said:
If you don't believe me, re-calculate it. It's a frame field so I'm working in local Minkowski coords when the acceleration is calculated.
I will try to do so, but it will take a while. However, if you are working in local Minkowski coordinates then the form of the metric cannot be Schwarzschild. I think my skepticism is justified.
 
  • #28
Mentz114 said:
There's nothing approximate here. These are exact calculations. We have the (inverse) metric. It is encoded in the coframe cobasis vectors ( see the tensor product expression I give earlier ).

In which case the metric is not Minkowski; the cobasis vectors you wrote down are not those of the Minkowski metric.

Mentz114 said:
In the local frame the connection coefficients are Ricci rotation coefficients and they are used in calculating covariant derivs instead of the CS2's.

If the "local frame" is supposed to be Minkowski then the connection coefficients are zero.

Mentz114 said:
The global metric is in the coframe, as I said. The tetrad formed from the coframe basis projects the metric to the Minkowski (local) metric.

The tetrad gives expressions for unit vectors in the four basis directions, in terms of the global (Schwarzschild) metric, yes. That isn't the same as actually using the local Minkowski metric.

Mentz114 said:
I stated both, uμ=(1,0,0,0) and uμ=(1,0,0,0).

But those don't match the metric expression you wrote down. They aren't unit vectors unless the line element you are using is the Minkowski line element, [itex]ds^2 = - dt^2 + dr^2 + r^2 d\theta^2 + r^2 sin^2 \theta d\phi^2[/itex].
 
  • #29
You guys seem to want to confuse things deliberately.
Doesn't anybody here see the difference between the transformation properties of tensors versus vectors? Or following Dalespam policy since all of them can be called n-tensors they all behave equally?
4-acceleration is a contravariant vector, regardless of the fact it can be called a rank 1-tensor.
 
  • #30
Yeah, I think there's just a level of confusion over how frame fields work. The frame fields allow one to compute stuff with respect to a "local" Minkowski metric, but the overall metric is still Schwarzschild. The rotation coefficients are nonzero, and so on. I do agree that the four-velocity is not yet properly scaled, though.

TrickyDicky said:
You guys seem to want to confuse things deliberately.
Doesn't anybody here see the difference between the transformation properties of tensors versus vectors? Or following Dalespam policy since all of them can be called n-tensors they all behave equally?
4-acceleration is a contravariant vector, regardless of the fact it can be called a rank 1-tensor.

I only caught a glimpse of this argument in the other thread. Vectors are tensors, man, and all tensors behave the same basic way. That's my opinion on the matter. I'm not sure why someone would say they behave differently. Maybe it's just a matter of people in general failing to specify which indices are covariant vs. contravariant?

Eh, it's all rather beside the point from my perspective. We all know (or believe) that directly boosting the acceleration should give the same result as boosting the frame field and then calculating the acceleration. We're just trying to verify it.
 
  • #31
TrickyDicky said:
4-acceleration is a contravariant vector, regardless of the fact it can be called a rank 1-tensor.

I'm confused; in the other thread you said 4-acceleration was a tensor, not a contravariant vector:

TrickyDicky said:
Have you tried reading Carroll notes for instance? Then you should realize that in GR the expression with christoffel corrections transforms as a tensor, not as a contravariant vector.

The "expression with Christoffel corrections" is the 4-acceleration.
 
  • #32
DaleSpam said:
I will try to do so, but it will take a while. However, if you are working in local Minkowski coordinates then the form of the metric cannot be Schwarzschild. I think my skepticism is justified.

It only takes 5 minutes. Yes, the metric is Schwarzschild but we have a local Minkowski metric. What I've done is standard frame field stuff.
 
  • #33
PeterDonis said:
In which case the metric is not Minkowski; the cobasis vectors you wrote down are not those of the Minkowski metric.

If the "local frame" is supposed to be Minkowski then the connection coefficients are zero.

The tetrad gives expressions for unit vectors in the four basis directions, in terms of the global (Schwarzschild) metric, yes. That isn't the same as actually using the local Minkowski metric.

But those don't match the metric expression you wrote down. They aren't unit vectors unless the line element you are using is the Minkowski line element, [itex]ds^2 = - dt^2 + dr^2 + r^2 d\theta^2 + r^2 sin^2 \theta d\phi^2[/itex].
These remarks don't help because what I've done is standard frame field stuff which I suspect you are not familiar with.
 
  • #34
TrickyDicky said:
You guys seem to want to confuse things deliberately.
Doesn't anybody here see the difference between the transformation properties of tensors versus vectors? Or following Dalespam policy since all of them can be called n-tensors they all behave equally?
4-acceleration is a contravariant vector, regardless of the fact it can be called a rank 1-tensor.
Please stop polluting my thread with this stuff. Start your own thread if you want to argue about whether 4-vectors are tensors or whatever.
 
  • #35
Muphrid said:
Well, it's possible I've made an error in believing that the acceleration
...
...

Edit: I think I found my error. I constructed the gauge-invariant velocity incorrectly. Fixed some things, but I'll have to look at this with fresh eyes in the morning.
This is interesting. The connections are different between the frames, which is why they have different accelerations. I'll study what you've written later when I have more time.
 

Similar threads

  • Special and General Relativity
Replies
5
Views
894
  • Special and General Relativity
2
Replies
37
Views
4K
  • Special and General Relativity
Replies
3
Views
2K
  • Special and General Relativity
Replies
12
Views
1K
  • Special and General Relativity
Replies
3
Views
2K
  • Special and General Relativity
Replies
18
Views
2K
  • Advanced Physics Homework Help
Replies
4
Views
1K
  • Special and General Relativity
Replies
3
Views
902
  • Special and General Relativity
Replies
19
Views
3K
  • Special and General Relativity
Replies
8
Views
1K
Back
Top