Row Major vs Column Major Vector
Reading time: 23 mins.Earlier in this lesson, we explained that vectors (or points) could be written down as [1x3] matrices (one row, three columns). However, we could have also written them down as [3x1] matrices (three rows, one column). Technically, these two ways of expressing points and vectors as matrices are perfectly valid, and choosing one style or the other is only a matter of convention.
Vector written as [1x3] matrix: \( V=\begin{bmatrix}x & y & z\end{bmatrix}\)
Vector written as [3x1] matrix: \(V=\begin{bmatrix}x\\y\\z\end{bmatrix}\)
In the first example ([1x3] matrix), we have expressed our vector or point in what we call the rowmajor order: the vector (or point) is written as a row of three numbers. In the second example, we say that points or vectors are written in columnmajor order: we write the three coordinates of the vector or point vertically as a column.
Remember that we express points and vectors as matrices to multiply them by [3x3] transformation matrices (for the sake of simplicity, we will work with [3x3] rather than [4x4] matrices). We have also learned that we can only multiply matrices when the number of columns from the left matrix and the number of rows from the right matrix is the same. In other words, the matrices [m x p] and [p x n] can be multiplied by each other, but the matrices [p x m] and [p x n] can't. Note that if we write a vector as a [1x3] matrix, we can multiply it by a [3x3] matrix (assuming this [3x3] matrix is on the right inside of the multiplication), but if we write this vector as a [3x1] matrix, then we can't multiply it by a [3x3] matrix. This is illustrated in the following examples. The inner dimensions (3 and 3) of the matrices involved in the multiplication are the same (in green), so this multiplication is valid (and the result is a transformed point written in the form of a [1x3] matrix):
$$ [1 \times \textcolor{green}{3}]*[\textcolor{green}{3} \times 3] = \begin{bmatrix} x & y & z \end{bmatrix} * \begin{bmatrix} c_{00}&c_{01}&{c_{02}}\\ c_{10}&c_{11}&{c_{12}}\\ c_{20}&c_{21}&{c_{22}}\\ \end{bmatrix} = \begin{bmatrix} x'&y'&z' \end{bmatrix} $$The inner dimensions (1 and 3) of the matrices involved in the multiplication are not the same (in red), so this multiplication is not possible:
$$ [3 \times \textcolor{red}{1}]*[\textcolor{red}{3} \times 3] \rightarrow \begin{bmatrix} x\\ y\\z \end{bmatrix} * \begin{bmatrix} c_{00}&c_{01}&{c_{02}}\\ c_{10}&c_{11}&{c_{12}}\\ c_{20}&c_{21}&{c_{22}} \end{bmatrix} $$So what do we do? The solution to this problem is not to multiply the vector or the point by the matrix, but the matrix M by the vector V. In other words, we move the point or vector to the right inside of the multiplication:
$$ [{3} \times \textcolor{green}{3}]*[\textcolor{green}{3} \times {1}] \rightarrow \begin{bmatrix} c_{00}&c_{01}&{c_{02}}\\ c_{10}&c_{11}&{c_{12}}\\ c_{20}&c_{21}&{c_{22}} \end{bmatrix} * \begin{bmatrix} x\\y\\z \end{bmatrix} = \begin{bmatrix} x'\\y'\\z' \end{bmatrix} $$Note that the result of this operation is a transformed point written in the form of a [3x1] matrix. So we get the point to start with, and we finish with a transformed point which is what we want. Problem solved. To summarize, when by convention we decide to express vectors or points in rowmajor order ([1x3]), we need to put the point on the left side of the multiplication and the [3x3] on the right inside of the multiplication sign. This is called, in mathematics, a left or premultiplication. If you decide to write the vectors in columnmajor order instead ([3x1]), the [3x3] matrix needs to be on the left side of the multiplication and the vector or point on the right side. This is called a right or postmultiplication.
We need to be careful about how these terms are used. For instance, Maya documentation says, "the matrices are postmultiplied in Maya. For example, to transform a point P from objectspace to worldspace (P'), you would need to postmultiply by the worldMatrix. (P' = P x WM)", which is confusing because it's a premultiplication, but they are speaking about the position of the matrix with respect to the point in this particular case. That's an incorrect use of the terminology. It should have been written that in Maya, points and vectors are expressed as rowmajor vectors and are premultiplied (meaning the point or vector appears before the matrix in the multiplication).
The following table summarises the differences between the two conventions (where P, V, and M respectively stand for Point, Vector, and Matrix).
RowMajor order 
ColumnMajor order 

\(P/V=\begin{bmatrix}x & y & z\end{bmatrix}\) 
\(P/V=\begin{bmatrix}x \\ y \\ z\end{bmatrix}\) 
Left or premultiplication 
Right or postmultiplication 
P/V * M 
M * P/V 
Now that we have learned about these two conventions, you might ask, "isn't that just about writing things on paper?". For example, we know how to calculate the product of two matrices, A and B: multiply each coefficient within A's current row by the associated elements within B's current column and sum up the result. Let's apply this formula using the two conventions and let's compare the results:
RowMajor order 
ColumnMajor order 

$${\begin{bmatrix}x & y & z\end{bmatrix} * \begin{bmatrix} a & b & c \\ d & e & f \\ g & h & i \end{bmatrix}}$$  $${ \begin{bmatrix} a & b & c \\ d & e & f \\ g & h & i \end{bmatrix} * \begin{bmatrix}x\\y\\z\end{bmatrix} }$$ 
$${\begin{array}{l}x' = x * a + y * d + z * g\\y' = x * b + y * e + z * h\\z' = x * c + y * f + z * i\end{array}}$$  $${\begin{array}{l}x' = a * x + b * y + c * z\\y' = d * x + e * y + f * z\\z' = g * x + h * y + i * z\end{array} }$$ 
Multiplying a point or a vector by a matrix should give us the same result whether we use row or columnmajor order. For example, you use a 3D application to rotate a point by a certain angle around the zaxis. In that case, you expect the point the be in a particular position after the rotation, no matter what internal convention the developer used to represent points and vectors. However, as you can see from the table above, multiplying a rowmajor and columnmajor point (or vector) by the same matrix clearly would give us a different result. To get back on our feet, we would need to transpose the [3x3] matrix used in the columnmajor multiplication to be sure that x', y' and z' are the same (if you need to remember what the transpose of a matrix is, check the chapter on Matrix Operations). Here is what we get:
RowMajor order 
ColumnMajor order 

$${\begin{bmatrix}x & y & z\end{bmatrix} * \begin{bmatrix} a & b & c \\ d & e & f \\ g & h & i \end{bmatrix}}$$  $${ \begin{bmatrix} a & d & g \\ b & e & h \\ c & f & i \end{bmatrix} * \begin{bmatrix}x\\y\\z\end{bmatrix} }$$ 
$${\begin{array}{l}x' = x * a + y * d + z * g\\y' = x * b + y * e + z * h\\z' = x * c + y * f + z * i\end{array} }$$  $${\begin{array}{l}x' = a * x + d * y + g * z\\y' = b * x + e * y + h * z\\z' = c * x + f * y + i * z\end{array} }$$ 
In conclusion, going from rowmajor order to columnmajor order involves swapping the point or vector and the matrix in the multiplication and transposing the [3x3] matrix to guarantee that both conventions give the same result (and vice versa).
From these observations, we can see that any series of transformations applied to a point or a vector when a rowmajor convention is used can be written in sequential order (or reading order). Imagine, for instance, that you want to translate point P with matrix T, then rotate it around the zaxis with Rz, then around the yaxis with Ry. You can write:
$$P'=P * T * R_z * R_y$$If you were to use a columnmajor notation, you would need to call the transform in reverse order (which one might find counterintuitive):
$$P'=R_y * R_z * T * P$$So you may think, "there must be a reason to prefer one system to another". Both conventions are correct and give us the same result, but for some technical reasons, Maths and Physics texts generally treat vectors as column vectors.
The order of transformation when we use columnmajor matrices is more similar in mathematics to how we write function evaluation and composition.
The rowmajor matrix convention makes matrices easier to teach, which is why we use it for Scratchapixel (as well as Maya and DirectX. They are also defined as the standard in the RenderMan specifications). However, some 3D APIs, such as OpenGL, use a columnmajor convention.
Implication in Coding: Does it Impact Performance?
There is another potentially essential aspect to consider if you need to choose between rowmajor and columnmajor, but this has nothing to do with the conventions themselves and whether one is more practical. It has more to do with the computer and the way it works. Remember that we will be dealing with [4x4] matrices. Typically the implementation of a matrix in C++ looks like this:
class Matrix44 { ... float m[4][4]; };
As you can see, the 16 coefficients of the [4x4] matrix are stored in a twodimensional array of floats (or doubles, depending on the precision you need. Our C++ Matrix class is a template). This means that in memory, the 16 coefficients will be laid out in the following manner: c00, c01, c02, c03, c10, c11, c12, c13, c20, c21, c22, c23, c30, c31, c32, c33\. In other words, they are laid out contiguously in memory. Now let's see how these coefficients are accessed in a vectormatrix multiplication where vectors are written in rowmajor order:
// rowmajor order x' = x * c00 + y * c10 + z * c20 y' = x * c01 + y * c11 + z * c21 z' = x * c02 + y * c12 + z * c22
As you can see, the matrix elements for x' are not accessed sequentially. In other words, to calculate x', we need the 1st, 5th, and 9th float of the matrix 16 floats array. To calculate y', we need to access this array's 2nd, 6th, and 10th float. And finally, for z', we need the array's 3rd, 7th, and 11th float. In computing, accessing elements from an array in a nonsequential order is not necessarily good. It potentially degrades the cache performance of the CPU. We won't go into too many details here, but let's say that the closest memory that the CPU can access is called a cache. This cache is very fast to access but can only store a very limited number of data. When the CPU needs to access some data, it first checks if it exists in the cache. If it does, the CPU access this data right away (cache hit), but it doesn't (cache miss); it first needs to create an entry in the cache for it, then copy to this location the data from the main memory. This process is more timeconsuming than when the data already exists in the cache, so ideally, we want to avoid cache misses as much as possible. Additionally, when copying the particular data from main memory, the CPU also copies a chunk of the data that lives right next to it (for instance, the next 24 bytes) because hardware engineers figured that if your code needed to access an element of an array, it was likely to access the elements following it soon after as well. Indeed, in programs, we often loop over elements of an array in sequential order, and this assumption is likely to be true. Applied to our matrix problem, accessing the coefficients of the matrix in nonsequential order can therefore be a problem. Assuming the CPU loads the requested float in the cache plus the 3 floats next to it, our current implementation might lead to many caches misses since the coefficients used to calculate x' y' and z' are 5 floats apart in the array. On the other hand, if you use a columnmajor order notation, computing x', for instance, requires access to the matrix's 1st, 2nd, and 3rd elements.
// columnmajor order x' = c00 * x + c01 * y + c02 * z y' = c10 * x + c11 * y + c12 * z z' = c20 * x + c21 * y + c22 * z
The coefficients are accessed in sequential order, which also means that we make good use of the CPU cache mechanism (only 3 cache misses instead of 9 in our example). In conclusion, from a programming point of view, implementing our point or vectormatrix multiplication using a columnmajor order convention might be better, performancewise, than the version using the rowmajor order convention. Practically though, we haven't been able to demonstrate that this was the case (when you compile your program using the optimization flags O, O2, or O3, the compiler can do the work for you by optimizing loops over multidimensional arrays) and we have been successfully using the rowmajor order version without any loss of performance compared to a version of the same code using a columnmajor order implementation.
template<typename T> class Vec3 { public: Vec3(T xx, T yy, T zz) : x(xx), y(yy), z(zz) {} T x, y, z, w; }; template<typename T> class Matrix44 { public: T m[4][4]; Vec3<T> multVecMatrix(const Vec3<T> &v) { #ifdef ROWMAJOR return Vec3<T>( v.x * m[0][0] + v.y * m[1][0] + v.z * m[2][0], v.x * m[0][1] + v.y * m[1][1] + v.z * m[2][1], v.x * m[0][2] + v.y * m[1][2] + v.z * m[2][2]); #else return Vec3<T>( v.x * m[0][0] + v.y * m[0][1] + v.z * m[0][2], v.x * m[1][0] + v.y * m[1][1] + v.z * m[1][2], v.x * m[2][0] + v.y * m[2][1] + v.z * m[2][2]); #endif } }; #include <cmath> #include <cstdlib> #include <cstdio> #include <ctime> #define MAX_ITER 10e8 int main(int argc, char **argv) { clock_t start = clock(); Vec3<float> v(1, 2, 3); Matrix44<float> M; float *tmp = &M.m[0][0]; for (int i = 0; i < 16; i++) *(tmp + i) = drand48(); for (int i = 0; i < MAX_ITER; ++i) { Vec3<float> vt = M.multVecMatrix(v); } fprintf(stderr, "Clock time %f\n", (clock()  start) / float(CLOCKS_PER_SEC)); return 0; }
Rowmajor and ColumnMajor Order in Computing
For the sake of completeness, let's mention that the terms rowmajor and columnmajor order can also be used in computing to describe how elements of multidimensional arrays are laid out in memory. In rowmajor order, the elements of a multidimensional array are laid out one after the other, from left to right, top to bottom. This is the method used by C/C++. For example, the matrix:
$$M = \begin{bmatrix}1&2&3\\4&5&6\end{bmatrix}$$Could be written in C/C++ as:
float m[2][3]={{1, 2, 3}, {4, 5, 6}};
And the elements of this array would be laid out contiguously in linear memory as follows:
1 2 3 4 5 6
In columnmajor order, which is used by languages such as FORTRAN and MATLAB, elements of the matrix are stored in memory from top to bottom, left to right. Using the same matrix example, the elements of the matrix would be stored (and accessed) in memory in the following way:
1 4 2 5 3 6
Knowing how the elements of a matrix are laid out in memory is important, especially when you try to access them using pointer offset and for loop optimization (we have explained previously in this chapter that it could affect the CPU cache performance). However, since we will only be considering C/C++ as our programming language, columnmajor ordering (applied to computing) is of little interest to us. We are only mentioning what the terms mean in computing so that you are aware that they might describe two things depending on the context in which they are used. Therefore, you should be careful not to mix them up. In mathematics, they describe whether you treat vectors (or points) as rows of coordinates or as columns and the second. In computing, they represent how a specific programming language store and accesses elements of the multidimensional array (which matrices are) in memory.
OpenGL is an interesting case in that regard. When GL was initially created, the developers chose the rowmajor vector convention. Developers who extended OpenGL thought they should go back to columnmajor vectors, which they did. However, for compatibility reasons, they didn't want to change the code for the pointmatrix multiplication and decided instead to change the order in which the matrix coefficients were stored in memory. In other words, OpenGL stores the coefficients in columnmajor order, which means that the translation coefficients m03, m13, and m23 from a matrix using columnmajor vector have indices 13, 14, 15 in the float array as would the translation coefficients m30, and m31 and m32 from a matrix using rowmajor vector.
Summary
The differences between the two conventions are summarised in the following table:
RowMajor Vector (Mathematics) 
ColumnMajor Vector (Mathematics) 

\(P/V=\begin{bmatrix}x & y & z\end{bmatrix}\) 
\(P/V=\begin{bmatrix}x \\ y \\ z\end{bmatrix}\) 
Premultiplication \(vM\) 
Postmultiplication \(Mv\) 
Call order and the order in the transforms are applied the same: "take P, transform by T, transform by Rz, transform by Ry" is written as \(P'=P*T*R_z*R_y\) 
Call order is the reverse of the order in the transforms are applied: "take P, transform by T, transform by Rz, transform by Ry" is written as \(P'=R_y*R_z*T*P\) 
API: Direct X, Maya 
API: OpenGL, PBRT, Blender 
The rows of the matrix represent the bases (or axes) of a coordinate system (red: xaxis, green: yaxis, blue: zaxis) 
The columns of the matrix represent the bases (or axes) of a coordinate system (red: xaxis, green: yaxis, blue: zaxis) 
$${\begin{bmatrix} \color{red}{c_{00}}& \color{red}{c_{01}}&\color{red}{c_{02}}&0\\ \color{green}{c_{10}}& \color{green}{c_{11}}&\color{green}{c_{12}}&0\\ \color{blue}{c_{20}}& \color{blue}{c_{21}}&\color{blue}{c_{22}}&0\\0&0&0&1 \end{bmatrix} }$$  $${ \begin{bmatrix} \color{red}{c_{00}}& \color{green}{c_{01}}&\color{blue}{c_{02}}&0\\ \color{red}{c_{10}}& \color{green}{c_{11}}&\color{blue}{c_{12}}&0\\ \color{red}{c_{20}}& \color{green}{c_{21}}&\color{blue}{c_{22}}&0\\0&0&0&1\end{bmatrix} }$$ 
The translation values are stored in the c30, c31, and c32 elements. 
The translation values are stored in the c03, c13, and c23 elements. 
$${\begin{bmatrix} 1&0&0&0\\ 0&1&0&0\\ 0&0&1&0\\ Tx&Ty&Tz&1\end{bmatrix} }$$  $${\begin{bmatrix} 1&0&0&Tx\\ 0&1&0&Ty\\ 0&0&1&Tz\\ 0&0&0&1\end{bmatrix} }$$ 
Transpose the matrix to use it as a columnmajor ordered matrix 
Transpose the matrix to use it as a rowmajor ordered matrix 
RowMajor Vector (Mathematics) 
ColumnMajor Vector (Mathematics) 

API: Direct X, Maya, PBRT 
API: OpenGL 
A reader posted a question on Stackoverflow suggesting the table above needed to be The topic is confusing. Despite our best attempts to shed some light on the matter, many people still need clarification. Our answer on Stackoverflow could hopefully bring another insight into the question.
You have the theory (what you do in mathematics with a pen and paper) and what you do with your implementation (C++). These are two different problems.

Mathematics: you can use two notations, either column or rowmajor. With a major row vector, on paper, you need to write the vectormatrix multiplication vM where v is the row vector (1x4) and M your 4x4 matrix. Why? Because you can mathematically only write [1x4]*[4x4], and not the other way around. Similarly, if you use a column, the vector needs to be written down vertically or in notation [4x1] (4 rows, 1 column). Thus, the multiplication with a matrix can only be written as follows: [4x4][4x1]. Note that the matrix is put in front of the vector: Mv. The first notation is called a left or premultiplication (because the vector is on the left side of the product), and the second (Mv) is called a right or postmultiplication (because the vector is on the right side of the product). As you see, the terms derive from whether the vector is on the left side (in front of or "pre") or on the right side (after or "post") of the matrix.
Now, if you need to transform a vector (or a point), you need to pay attention to the order of multiplication when you write them down on paper. For example, if you want to translate something with matrix T and then rotate with R and then scale with S, then in a columnmajor world, you need to write v' = S * R * T * v. In a rowmajor world, you need to write v' = v * T * R * S.
That's for the theory. Let's call this part the row/column vector convention issue.

Computer: then comes the point when you decide to implement this in C++, say. The good thing about this is that C++ doesn't impose anything about anything. You can map the values of your matrix's coefficients in memory the way you want, and you can write the code to perform a matrix multiplication by another matrix the way you want. Similarly, how you access the coefficients for a vectormatrix multiplication is entirely up to you. You need to clearly distinguish how you map your coefficients in memory and what conventions you need to use from a mathematical viewpoint to represent your vectors. These are two independent problems. Let's call this part the row/columnmajor memory layout issue.
For instance, you can declare a matrix class as an array of 16 contiguous floats. That's fine. Where coefficients m14, m24, and m34 represent the translation part of the matrix (Tx, Ty, Tz), you assume your "convention" is rowmajor even though you are told to use OpenGL matrix convention, which is said to be columnmajor. Here the possible confusion comes from the mapping of the coefficients in memory being different from the mental representation you are making yourself of a "columnmajor" matrix. You coded "row," but you were said to use (from a mathematical point of view) "column", hence your difficulty in making sense of whether you do things right or wrong.
What's important is to see a matrix as a representation of a coordinate system defined by three axes and a translation. Where and how you store this data in memory is entirely up to you. Assuming the three vectors representing the three axes of the coordinate system are named AX(x,y,z), AY(x,y,z), AZ(x,y,z), and the translation vector is denoted by (Tx, Ty, Tz), then mathematically if you use column vector you have:
$$ M = \begin{bmatrix} AXx & AYx & AZx & Tx\\ AXy & AYy & AZy & Ty\\ AXz & AYz & AZz & Tz\\ 0 & 0 & 1 & 1 \end{bmatrix} $$The axes of the coordinate system are written vertically. So now, if you have, you use rowmajor:
$$ M = \begin{bmatrix} AXx & AXy & AXz & 0\\ AYx & AYy & AYz & 0\\ AZx & AZy & AZz & 0\\ Tx & Ty & Tz & 1 \end{bmatrix} $$The axes of the coordinate system are written horizontally. When it comes to the computer world, you must choose how you will store these values in the computer's memory. For example, you can do the following:
float m[16] = { AXx, AXy, AXz, 0, AYx, AYy, AYz, 0, AZx, AZy, AZz, 0, Tx, Ty, Tz, 1};
Or:
float m[16] = { AXx, AXy, AXz, Tx, AYx, AYy, AYz, Ty, AZx, AZy, AZz, Tz, 0, 0, 0, 1};
Or:
float m[16] = { AXx, AYx, AZx, Tx, AXy, AYy, AZy, Ty, AXz, AYz, AZz, Tz, 0, 0, 0, 1};
None of these choices indicate which "mathematical" row/column vector convention you use. You are just storing 16 coefficients in memory in different ways, and that's perfectly fine as long as you know what that way is so that you can access them appropriately later on. Remember that a vector multiplied by a matrix should give you the same vector whether you use a row or columnmathematical notation. Thus what's important is that you multiply the (x,y,z) coordinates of your vector by the right coefficients from the matrix, which requires the knowledge of how "you" have decided to store the matrix coefficient in memory:
Vector3 vecMatMult ( Vector3 v, float AXx, float AXy, float AXz, float Tx, float AYx, float AYy, float AYz, float Ty, float AZz, float AZy, float AZz, float Tz) { return Vector3( v.x * AXx + v.y * AYx + v.z * AZx + Tx, v.x * AXy + v.y * AYy + v.z * AZy + Ty, v.x * AXz + v.y * AZz + v.z * AZz + Tz }
We wrote this function to underline the fact that no matter which convention you use, the result of the vector * matrix multiplication is just a multiplication and addition between the vector's input coordinates and the coordinate system's axis coordinates AX, AY, and AZ (regardless of the notation you use, and regardless of how you store them in memory). If you use:
float m[16] = { AXx, AXy, AXz, 0, AYx, AYy, AYz, 0, AZx, AZy, AZz, 0, Tx, Ty, Tz, 1};
You need to call the following:
vecMatMult(v, m[0], m[1], m[2], m[12], m[4], m[5], m[6], m[13], ...
If you use:
float m[16] = { AXx, AYx, AZx, Tx, AXy, AYy, AZy, Ty, AXz, AYz, AZz, Tz, 0, 0, 0, 1};
You need to call the following:
vecMatMult(v, m[0], m[4], m[8], m[3], m[1], m[5], m[9], m[10], ...
Does that tell you which convention you use? Unfortunately, no. You need to call the right coefficients in the right places when you do a vec * mat multiplication. And that's all there is to it, as disconcerting as it may seem.
mt11 = ml11 * mr11 + ml12 * mr21 + ml13 * mr31 + ml14 * mr41
where ml
is the lefthand matrix, and mr
is the righthand one: mt = ml * mr
. However, note that we haven't been using brackets []
for the indices because we don't want to suggest we access elements stored in a 1D array here. We are referring to the coefficients of matrices as used in the mathematical notation (and not those stored in memory). If you want to write this in C++, it depends on how you have stored your coefficients in memory, as explained above with the vectormatrix product.