# Diagrams/Dev/Transformations

## Contents

# Linear and affine transformations

A *linear transformation* on a vector space is a function satisfying

where is an arbitrary scalar and are arbitrary vectors. Linear transformations always preserve the origin, send lines to lines, and preserve the relative distances of points along any given line. The image of parallel lines under a linear transformation is again parallel lines. However, linear transformations do *not* necessarily preserve angles between lines. Examples of linear transformations include

- rotation
- reflection
- scaling
- shear

Linear transformations are closed under composition and form a monoid with the identity function as the neutral element.

An *affine transformation* is a function of the form where is a linear transformation and is some vector. Affine transformations preserve all the same things as linear transformations, *except* that they do not necessarily send the origin to itself. Affine transformations include all the above examples, along with

- translation

Affine transformations are also closed under composition, and are used as the basis for all transformations in `diagrams`

. Note that using homogeneous coordinates, affine transformations can be seen as a certain subset of linear transformations in a vector space one dimension higher. (`diagrams`

used to actually use this approach for representing affine transformations, but no longer does.)

# Matrices, inverse and transpose transformations

Any linear transformation in an -dimensional space can be represented as an matrix: in particular, the matrix whose th column is the result of applying the transformation to the unit vector with a as its th entry and s everywhere else. For example,

is the linear transformation that sends to and sends to . It's easy to see that multiplying a matrix by such a unit vector picks out a column of the matrix, as I claimed. It's also not too hard to see that the matrix's action on any other vector is completely determined by linearity. Finally, of course, one can verify that matrix multiplication is, in fact, linear.

By the inverse of a linear map (note I use "linear transformation" and "linear map" interchangeably), we mean its inverse under composition: a transformation such that . We can also think about this in terms of matrices: the inverse of a matrix is a matrix such that , the identity matrix (with ones along the diagonal and zeros everywhere else). One can check that (1) the identity matrix corresponds to the identity linear map, and (2) matrix multiplication corresponds to composition of linear maps. So these are really two different views of the same thing.

The *transpose* of a matrix (denoted ) is the matrix you get when you reflect all the entries about the main diagonal. For example,

This is (usually) not the same as the inverse, as can be easily checked. Now, how can we interpret the transpose operation on matrices as an operation on linear maps? Of course, we can just say "the transpose of a linear map is defined to be the linear map corresponding to the transpose of its matrix representation". But I actually don't have any intuitive sense for what the transpose of a linear map IS in any more fundamental sense.

What we really want to think about is the *inverse transpose*, that is, the inverse of the transpose of a matrix, denoted . Suppose we have a vector , and another vector which is perpendicular to . Now suppose we apply a linear map (represented by a matrix ) to the vector , giving us a new vector . In general, may not be perpendicular to , since linear transformations do not preserve angles. Some linear maps such as rotations and uniform scales do preserve perpendicularity (if that's a word), but not all linear maps do: for example, the 2D linear map that scales all -coordinates by 2 but leaves -coordinates unchanged. But what if we want to obtain another vector perpendicular to ? In fact, the thing to do is to multiply not by , but by the *inverse transpose* of . That is: if and are perpendicular vectors, then so are and . This can be proved by noting that the dot product of two vectors can equivalently be written (treating vectors as column matrices), and that two vectors are perpendicular iff their dot product is zero. Hence

Now, if one has a matrix it is easy to compute its transpose, and not too difficult to compute its inverse. However, in diagrams, given a transformation we *don't* have its matrix representation. Linear maps are represented more directly (and efficiently) as functions. We could generate a matrix by applying the transformation to basis vectors, but this is ugly, and converting a matrix back to a functional linear map is even uglier, and probably loses a lot of efficiency as well. What to do? We need to carry around enough extra information with each transformation so that we can extract the inverse transpose. We just have to make sure that this extra information is compositional, i.e. we know how to compose two transformations while preserving the extra information.

It's easy to see that (i.e. the inverse and transpose operations are involutions). It's not quite as obvious, but not too hard to show, that the inverse of the transpose is the same as the transpose of the inverse. Combining these facts, we see that for a given matrix there are really only four matrices of interest: , , , and . We can arrange them conceptually in a square, thus:

Then taking the inverse corresponds to a L-R reflection, and taking the transpose corresponds to a U-D reflection. Given two such sets of four linear maps, it's not hard to work out how to compose them: just compose the elements pairwise (*i.e.* compose the inverse with the inverse, the transpose with the transpose, *etc.*), keeping in mind that the inverse and transpose compose in the reverse order whereas the regular transformation and the inverse transpose compose in the normal order.

So each transformation is actually a set of *four* linear maps. To take the inverse or transpose of a transformation just involves shuffling the linear maps around. Composition works as described above. We just have to specify these four linear maps by hand for each primitive transformation the library provides, which can be done by appealing to the matrix representation of the primitive transformation in question.

Now, so far we have only represented *linear* transformations: affine transformations can be recovered by storing just a single extra vector along with the four linear transformations.

# Representation

Transformations are defined in `Diagrams.Core.Transform`

(from the `diagrams-core`

package). There are additional comments there which may be helpful. First, we define *invertible* linear transformations:

```
data (:-:) u v = (u :-* v) :-: (v :-* u)
```

That is, a linear transformation paired with its inverse. We always carry around an inverse transformation along with every transformation. All the functions for constructing primitive transformations also construct an inverse, and when two transformations are composed their inverses are also composed (in the reverse order). Note that the `:-*`

type constructor is from the `vector-space`

package. Don't worry about how it is implemented (actually I don't even know).

Then an (affine) `Transformation`

is defined as follows:

```
data Transformation v = Transformation (v :-: v) (v :-: v) v
```

There are three parts here. The first `(v :-: v)`

is the normal transformation (the linear part of it, *i.e.* without translation) paired with its inverse. The second `(v :-: v)`

is the transpose and inverse transpose. The final `v`

is the translational component of the transformation.

For examples of creating `Transformation`

s, see the remainder of the `Diagrams.Core.Transform`

module, and also the `Diagrams.TwoD.Transform`

module from the `diagrams-lib`

package.

# Specifying transformations as matrices

To turn an arbitrary matrix into a `Transformation`

would require the following:

- Assuming the matrix is represented using homogeneous coordinates, it must be checked that the matrix actually represents an affine transformation (as opposed to a general projective transformation). This corresponds to the bottom row of the matrix consisting of all zeros and a final 1.
- Extract the translational component from the final column of the matrix (except for the 1 in the bottom right corner).
- Extract the linear transformation component as the submatrix obtained by deleting the last row and column.
- Turn the matrix into a function by inlining the definition of matrix-vector multiplication.
*e.g.*the matrix

corresponds to the function .

- Compute the transpose, inverse, and inverse transpose of the matrix and turn the results into functions as well.

# Angle-preserving transformations

An angle-preserving transformation is one which preserves angles between all pairs of lines. It is possible to prove the following:

- A linear transformation is angle-preserving iff there exists a constant such that for all vectors . (See http://www.cs.bsu.edu/homepages/fischer/math445/angles.pdf.)
- Intuitively, the previous result means that any angle-preserving linear transformation (other than the constantly zero transformation) can be uniquely decomposed as a uniform scale followed by a rotation.
- An affine transformation is angle-preserving iff it can be expressed as an angle-preserving linear transformation followed by a translation.
- Angle-preserving affine transformations are closed under composition.

The last two points in particular imply that we can uniquely represent angle-preserving affine transformations by a triple where ( indicates a rotation by ), and given this representation we may compute

It is also easy to compute the inverse

and the transpose of the linear part:

(The above calculations are simplified by the observation that rotations and uniform scales commute, though of course transformations do not commute in general.)

As a concrete proposal, we can change `T2`

from a synonym for `Transformation R2`

to a sum type

data T2 = Ortho Angle Double R2 | GenT2 (Transformation R2)

and change things like `rotate`

to construct an `Ortho`

instead of a `Transformation R2`

. There is a bit of trickiness to be worked out with the function `scaling`

, which currently has type `Scalar v -> Transformation v`

, i.e. it is supposed to work over any vector space, but we want it to do something special for `R2`

. I am not sure what the right solution is.

In any case, some benefits of such a scheme would be:

- Angle-preserving transformations are precisely those which preserve circular arcs. If we add a new primitive type of arc segment, we can look at the final transformation applied to the segment to determine whether we can simply issue a primitive arc command (if the transformation is an
`Ortho`

) or if we must issue an arc command wrapped in a transform (or approximate the arc with Beziers).

- For typical applications,
`Ortho`

transformations make up the vast majority of transformations actually used. Intuitively, it seems this should lead to a performance boost, since`Ortho`

values consist of simple first-order data, making it easier for GHC to optimize e.g. chains of repeated transformations. General`Transformation`

values, on the other hand, are functions, which can be tricky for GHC to optimize e.g. when deeply nested.