4.10.10 · D2Advanced Topics (Elite Level)

Visual walkthrough — Metric tensor — raising - lowering indices

1,822 words8 min readBack to topic

Step 0 — What is a "component"? (the thing we're translating)

The subtle bit: if the basis arrows are not at right angles, the honest recipe "how many , how many " is not the same as "how far does reach along each arrow". Those are two different questions, and each gets its own list of numbers. That is the whole story of this page.

  • The red arrows are the basis — deliberately not perpendicular.
  • The yellow arrow is .
  • The dashed blue lines are the parallelogram rule: slide along , then along , to reach the tip. Their lengths give the contravariant numbers .

Step 1 — The second list: projection instead of recipe

WHY a dot product answers "how far along". For any two arrows, , and is exactly the length of 's shadow on (times ). So the dot product is the "reach along" measurement — that is why we chose it and not, say, an area.

WHAT IT LOOKS LIKE. Drop a perpendicular from the tip of onto each basis arrow.

  • Yellow: the vector (unchanged from Step 0).
  • Green dashed lines: the perpendicular drops. The foot of each drop marks the shadow.
  • Compare with Step 0's blue parallelogram: the two constructions land at different places on the arrows. That mismatch is why in general.

Step 2 — When the two lists agree (build intuition on the easy case)

WHY. With right angles, sliding along is the perpendicular drop onto — the parallelogram becomes a rectangle, and its side is the shadow. With unit length there is no rescaling either.

This is the ordinary Cartesian world of high school — which is precisely why nobody ever told you there were two kinds of components. The moment the axes tilt or stretch, the two lists split apart, and we need a translator. That translator is the metric.


Step 3 — Introduce the metric: a table of arrow dot-products

WHY this table is exactly what we need. It records the two things that broke Step 2's easy world: lengths of the arrows (diagonal entries) and their tilt (off-diagonal entries). Nothing more, nothing less. It is symmetric, , because .

  • Diagonal cells (blue) = squared lengths of each arrow.
  • Off-diagonal cells (yellow) = the shared tilt , where is the angle between the arrows.
  • When , , the yellow cells vanish, and we're back in Step 2. See how the table contains the easy case.

Step 4 — Derive lowering: turn the recipe into shadows

WHAT / WHY, line by line. Start from the definition of the shadow (Step 1), then substitute the recipe (Step 0):

Term by term:

  • — the shadow question we want the answer to.
  • — replace by its recipe (the numbers we have).
  • pull the scalar out front — dot product is bilinear, numbers slide out.
  • is by definition an entry of the metric table.

So the metric is the machine that converts the list you have (recipe, upper) into the list you want (shadow, lower).

The picture shows the arithmetic for : each contravariant number gets multiplied by the tilt/length stored in row of the table, and the results are summed. When the metric is off-diagonal the term leaks into — that leak is the tilt.


Step 5 — Derive raising: you must use the inverse table

WHY the inverse and not again. Lowering multiplied by . To go back we must cancel that multiplication — and the thing that cancels a matrix is its inverse. Multiply the lowering formula by and sum:

The loop returns you home — because is exactly "table then undo-table = do nothing".


Step 6 — Every case, on one plate (degenerate & signed metrics)

We must never leave a scenario undrawn. Three regimes cover them all:

  • Left panel (green): identity — the two lists sit on top of each other.
  • Middle (blue): diagonal stretch — perpendicular but rescaled, arrows still line up in direction, numbers rescale.
  • Right (red): a negative sign flips the covariant version onto the other side — the hallmark of an indefinite metric.

The degenerate warning: if some had determinant (a squashed basis where one direction collapses), the inverse would not exist and raising would be impossible. A usable metric must be non-degenerate — that's the price of two-way translation.


The one-picture summary

One diagram, the entire walkthrough: contravariant (recipe / parallelogram) on the left, covariant (shadows / perpendicular drops) on the right, and the metric table (down = lower) and its inverse (up = raise) as the two arrows crossing between them.

Recall Feynman retelling — say it to a friend

A vector is one physical arrow, but there are two honest ways to put numbers on it. Recipe numbers (, upper): "walk this many of arrow-1, then this many of arrow-2." Shadow numbers (, lower): "how far do I reach along arrow-1, along arrow-2." On graph paper with square perpendicular cells these two are the same, so school never split them. Tilt or stretch the paper and they disagree. The metric is just the little table of dot-products of your measuring arrows — their lengths (diagonal) and their tilt (off-diagonal). Multiplying your recipe numbers by that table gives the shadow numbers: that's lowering. To go back you use the inverse table : that's raising. In Minkowski one diagonal entry is , so lowering the time slot flips its sign — the entire strangeness of spacetime, in one minus sign.

Which construction gives contravariant components?
The parallelogram / recipe: how many of each basis arrow, .
Which construction gives covariant components?
The perpendicular shadow (projection), .
Why do the two lists coincide in Cartesian coordinates?
The basis is orthonormal (): no tilt, unit length, so recipe = shadow.
What must be true of for raising to be possible?
It must be non-degenerate () so the inverse exists.

Connections