✦ For everyone, free.

Practical knowledge for real and everyday life

Home

1.10.4 Component Tensor Notation

Component Tensor Notation is a method to express tensors using indices, revealing their structure and transformation properties within multilinear algebra.

Component Tensor Notation is a notational approach in which a tensor is represented explicitly as an array, or table, of numerical entries, each entry indexed by a specific combination of coordinate values relative to a chosen basis, rather than by formal index labels standing for slots. Where index notation, in either its component or abstract form, writes expressions such as T^i_jk to describe an entire family of components at once, component tensor notation is concerned with the individual numerical entries themselves, the way they are arranged, listed, and read off once a basis has actually been fixed and specific numerical index values have been substituted.

This notation is the most concrete of all tensor notations, since it reduces a tensor to nothing more than a structured list, or nested list, of numbers, with no remaining formal machinery beyond how those numbers are arranged and labeled. It plays the essential role of connecting the abstract and symbolic layers of tensor algebra to actual numerical data, which is indispensable whenever a tensor must be evaluated, stored, or computed with directly.


The Structure of a Component Array

Dimension and Rank Determine Array Shape

A tensor of rank r in an n-dimensional vector space has n^r individual components, arranged conceptually as an r-dimensional array with each side of length n. A scalar, rank 0, is a single number. A vector, rank 1, is a one-dimensional list of n numbers. A matrix, rank 2, is a two-dimensional grid of n × n numbers. A rank-3 tensor is a three-dimensional block of n × n × n numbers, and so on for higher ranks, each additional rank adding one further dimension to the array's shape.

number of components = nr

Reading a Specific Entry

A specific component is obtained by substituting concrete numerical values for every index, such as T^2_{13} for a (1,2) tensor in a space with at least three dimensions, which selects the single numerical entry located at upper-index position 2, first lower-index position 1, and second lower-index position 3 within the full component array.


Listing Conventions

Explicit Enumeration for Low Rank

For a vector, components are conventionally listed as an ordered tuple, v = (v^1, v^2, …, v^n), or as a column of numbers. For a matrix, components are listed as a rectangular grid, with the upper index conventionally indexing rows and the lower index indexing columns.

M = M11M21 M12M22

Slicing for Higher Rank

Tensors of rank three or higher are typically listed by slicing along one index, presenting the result as a sequence of lower-rank arrays, most commonly a stack or sequence of matrices, one matrix for each fixed value of the remaining index. This slicing convention makes higher-rank component data readable using the same two-dimensional grid format already familiar from matrices, applied repeatedly across the additional index.

T^i_jk, k=1 ... slices for k = 2, 3, ...

Component Notation in Computation

Direct Correspondence With Arrays in Software

Component tensor notation corresponds directly to how tensors are represented in numerical software, as multidimensional arrays, so that each index in the mathematical notation maps to one array dimension in an implementation, and each mathematical operation, contraction, tensor product, corresponds to a specific loop structure or array operation over those dimensions. This direct correspondence is a large part of why component notation remains indispensable for practical computation.

Verifying Formulas by Explicit Small Cases

Because component notation lists every individual numerical entry, it is often used to verify a general tensor identity by checking it explicitly in a small, concrete case, such as n = 2 or n = 3, writing out every component by hand and confirming the identity holds entry by entry. This kind of explicit verification is typically impractical in coordinate-free notation, which suppresses the individual entries needed for such a check.


Relation to Other Notational Layers

Component Notation as the Concrete Endpoint

Abstract index notation and direct notation both describe a tensor without committing to specific numerical values; component notation is the concrete endpoint reached once a basis has been fixed and every index has been assigned a definite numerical value. Every tensor equation expressed abstractly can, in principle, be unpacked into a corresponding set of component equations, one equation for each valid combination of free-index values, and it is this unpacked, fully explicit form that constitutes component notation proper.

Basis Dependence as a Defining Feature

Unlike abstract or coordinate-free notation, component notation is inherently tied to the specific basis in which the numbers were computed; the same tensor produces an entirely different array of numbers in a different basis, related by the standard tensor transformation law. This basis dependence is not a flaw but a defining feature of the notation, since its entire purpose is to expose the concrete numerical content of a tensor within one particular, chosen frame of reference.


Practical Role in the Overall Notational System

The Bridge Between Symbol and Number

Component tensor notation functions as the bridge connecting the symbolic and structural apparatus of tensor algebra, index rules, contraction, symmetry, to the actual numbers that a tensor takes on in any given situation. Every symbolic manipulation performed in index or abstract notation ultimately describes, and must be consistent with, how the corresponding numerical components behave, and component notation is the layer at which that consistency becomes directly checkable.

When Component Notation Is the Natural Choice

Component notation is the natural choice whenever a tensor's numerical values are the object of direct interest, such as reporting the measured entries of a physical stress tensor, initializing a tensor in a program, or working through a fully explicit worked example, in contrast to the more structural or basis-independent notations used for stating general theorems or tracking abstract relationships between tensors.