Why is a Linear Transformation a Type-(1,1) Tensor?

marschmellow

I've seen in multiple sources that a linear transformation constitutes a tensor with one contravariant and one covariant index. Could someone explain to me why this is the case? I'm asking not because I have a solid understanding of tensors and am confused about this particular example; rather, I have a very solid understanding of linear transformations and am trying to use this knowledge to understand the co- and contravariance of indices. I understand the co- and contravariance of vectors, but something about applying this concept to indices has created a gap in my understanding.

Fredrik

It doesn't, but it can be used to define one. If L is the linear transformation (from V into V), then you can define a (1,1) tensor T by T(u*,v)=u*(L(v)) for all u* in V* and all v in V.

marschmellow

Okay I can see that, but then why do people refer to a linear transformation as a (1,1) tensor? Now that I think about it, it doesn't seem like a tensor at all--it maps a vector to a vector, not some vectors to a scalar. The tensor you created maps a vector and a covector to a scalar, but you had to add something (a linear functional) to the linear transformation to get it.

Fredrik

Because the vector space of linear maps from V into V is isomorphic to the vector space of (1,1) tensors.

marschmellow

Why just (1,1) tensors? Isn't the space of all linear maps V-->V isomorphic to any [dim(V)]^2- dimensional vector space? Do the vector spaces of (2,0) tensors and (0,2) tensors not automatically satisfy this condition?

Fredrik

Yes, for all integers n, any two n-dimensional vector spaces are isomorphic. However, in the general case, you need something like a basis for each of the spaces to explicitly define the isomorphism. In this case, you just define, for each linear L:V→V, [tex]T_L(u^*,v)=u^*(L(v))[/tex] for all [itex]u^*\in V^*[/itex] and all [itex]v\in V[/itex], and the map [itex]L\mapsto T_L[/itex] is an isomorphism. No need to use any special bases, inner products, metrics or anything of that sort.

Another reason is that this identification between those two spaces works so well with the abstract index notation. In that notation, both L and T_L above would be denoted by [itex]L^a{}_b[/itex]. The map I denoted by L is [itex]v^b\mapsto L^a{}_b v^b[/itex], and the map I denoted by T_L is [itex](\omega_a,v^b)\mapsto L^a{}_b \omega_a v^b[/itex]. (Here I'm denoting a typical member of V* by a Greek letter instead of by a Latin letter with an asterisk, because the asterisks would make the abstract index notation awkward).

I should probably tell you that I'm making another identification by isomorphism in the preceding paragraph. [itex]L^a{}_bv^b[/itex] has a free index upstairs, so it should be interpreted as a (1,0) tensor, i.e. a member of V**. Specifically, it's the map [itex]u^*\mapsto T_L(u^*,v)[/itex], which could be denoted by [itex]T_L(\cdot,v)[/itex]. But I'm using the isomorphism [itex]f:V\to V^{**}[/itex] defined by [itex]f(v)(u^*)=u^*(v)[/itex] for all [itex]v\in V[/itex] and [itex]u^*\in V^*[/itex], to identify V with V**. Since [tex]f(L(v))(u^*)=u^*(L(v))=T_L(u^*,v)=T_L(\cdot,v)(u^*)[/tex] for all [itex]u^*\in V^*[/itex], we have [itex]f(L(v))=T_L(\cdot,v)[/itex]. This means that the map [itex]T_L(\cdot,v)[/itex] is the member of V** that the isomorphism f associates with [itex]L(v)\in V[/itex].

So when I said that L is denoted by [itex]L^a{}_b[/itex] in the abstract index notation, that was strictly speaking not true, but I said it anyway, because you will see lots of statements like that in GR books. It's more accurate to say that [itex]L^a{}_b[/itex] takes [itex]v^b[/itex] to [itex]L^a{}_bv^b[/itex], which denotes [itex]T_L(\cdot,v)=f(L(v))[/itex], where f is the natural isomorphism from V to V**.

Yes, this is very confusing at first. It takes some time getting used to. I think the key to understanding these things is to understand the isomorphism I denoted by f, so if you don't understand it perfectly, you should start by making sure that you do.

marschmellow

I appreciate this very in-depth reply. I'll definitely be taking a hard look at this soon. Thanks!