Skip to main content

Lorentz Transform Summary and Levi-Cevita symbols: EM II Notes 2014_08_06

Summary of what's gone on before.  In the last two days, unbeknownst to me at the time, we first showed that the Lorentz/Fitzgerald contraction only happens in the direction of the velocity of a frame.  Coupling this with rotational symmetry, yesterday, it was shown how the vector version of the Lorentz transform could be derived.  Yesterday's treatment needs to be repeated from end to start to truly  count as a derivation though, I suppose.

Picking up where I left off yesterday, the second half of the vector Lorentz transform, the expression for time in the primed frame can be written as

$t^{\prime} = \gamma\left(t - \vec{v}\cdot\vec{r}\right)$

Once again, this shows that only the component of the position vector parallel to the velocity gets to play.  However, here you should notice that the velocity vector is not normalized, not divided by it's magnitude.  In other words, while only the component of the position vector parallel to the velocity gets to play, the entire magnitude of the velocity gets to play.  This is also noted in the notes where the expression for $\gamma$ in this case is

$\gamma = \left(1 - v^2\right)^{1/2}$

Finally, in the section 1.2 ending on page 9, it's observed that what will become known as the spacetime line element is invariant between frames

$x^2 + y^2 + z^2 - t^2 = x^{\prime 2} + y^{\prime 2} + z^{\prime 2} - t^{\prime 2}$.

Consequently, we also just introduced hyperbolic geometry.

Index Notation
The first really interesting thing here is the totally-antisymmetric tensor.  I think this might be called the Levi-Civita symbol elsewhere.  I need to look it up.

Here's the definition:

$\epsilon_{ijk} = -\epsilon_{ikj} = -\epsilon_{jik} = -\epsilon_{kji}$.

Then, it only remains to define the value of $\epsilon_{123} = 1$ and we get that

$\epsilon_{123} = \epsilon_{231} = \epsilon_{312} = 1$, $\epsilon_{132} = \epsilon_{321} = \epsilon_{213} = -1$

With our new symbol, we can write down the vector cross product more concisely,

$\left(\vec{A} \times \vec{B}\right) = \epsilon_{ijk}A_jB_k$

Hunh, and now I have a question.

QUESTION:  Why is swizzling the indices between the following two versions of the same equation 'convenient'?

$\left[\vec{A}\times\left(\vec{B} \times \vec{C}\right)\right]_i = \epsilon_{ijk}\epsilon_{klm}A_jB_lC_m$

and the 'more convenient version'

$\left[\vec{A}\times\left(\vec{B} \times \vec{C}\right)\right]_i = \epsilon_{ijk}\epsilon_{lmk}A_jB_lC_m$

Memorize the following:

$\epsilon_{ijk}\epsilon_{lmk} = \delta_{il}\delta_{jm} - \delta_{im}\delta_{jl}$

QUESTION:  I'm guessing the second 'more convenient' version above was handy in deriving the Levi-Civita to delta function identity above?



Comments

Popular posts from this blog

Cool Math Tricks: Deriving the Divergence, (Del or Nabla) into New (Cylindrical) Coordinate Systems

Now available as a Kindle ebook for 99 cents ! Get a spiffy ebook, and fund more physics The following is a pretty lengthy procedure, but converting the divergence, (nabla, del) operator between coordinate systems comes up pretty often. While there are tables for converting between common coordinate systems , there seem to be fewer explanations of the procedure for deriving the conversion, so here goes! What do we actually want? To convert the Cartesian nabla to the nabla for another coordinate system, say… cylindrical coordinates. What we’ll need: 1. The Cartesian Nabla: 2. A set of equations relating the Cartesian coordinates to cylindrical coordinates: 3. A set of equations relating the Cartesian basis vectors to the basis vectors of the new coordinate system: How to do it: Use the chain rule for differentiation to convert the derivatives with respect to the Cartesian variables to derivatives with respect to the cylindrical variables. The chain ...

The Alcubierre Warp Drive Tophat Function and Open Science with Sage

I transferred yesterday's Mathematica file with the Alcubierre warp drive[2] line element and space curvature calculations to the  +Sage Mathematical Software System  today, (the files been  added to the public repository [3]).  If you haven't used Sage before, it's a Python based software package that's similar in functionality to Mathematica.  Oh, and it' free.  I also worked a little more on understanding the theory, but frankly, I made far more progress with the software than the theory.  What follows will be a little more of the Alcubierre theory, plus, a cool Sage interactive demo of one of the Alcubierre functions[1], as well as a bit about my first experience with using Sage. Theory The theory is fun, but it's moving slowly.  Here's the chalk board from this morning's discussion Alcubierre setup the derivation using something called the 3+1 formalism which means we consider space to be flat, (in this case), slices that are labelled ...

How Many Files Can You Add to a GPT Project? An Interview with GPT-5 on Limits, Context Engineering Tips, and Chats

 Setting the scene: I’m tinkering with Project TouCans, knee-deep in radio logs, SQLite dumps, and Cesium code. Naturally, I’m wondering if shoving all this into one GPT Project is a recipe for brilliance… or for disaster. So I turn to Vril — you know, after Brainy from the Legion of Super-Heroes , because what else do you call your AI sidekick who always has the answers? Time to ask him straight up. [ As an aside, yes, GPT-5 has decided to sometimes call me Vail. I'm not sure why to be honest. Also, I asked Vril, er GPT-5, to write up our interview for me. Apparently, me asking it to 'Bro' up a few stories, just for fun, has convinced Vril that I use 'Like,' more than I actually might. ] Me (Vail): So Vril, how many files can I throw into a GPT Project before it just starts choking? Like, is there some magic number where the context window taps out and everything falls apart? GPT-5 (Vril): Great question. There’s no single hard file limit. What matters is ...