Computational Representations of Message Passing
Abstract: Message passing on graphs, also known as graph convolutions, have become a popular research topic. In this piece, I aim to provide a short technical primer on ways to implement message passing on graphs. The goal is to provide clear pedagogy on what message passing means mathematically, and hopefully point towards cleaner computational implementations of the key algorithmic pieces.
Assumed knowledge: We assume our reader has familiarity with elementary graph concepts. More specifically, the terms “graph”, “nodes”, and “edges” should be familiar terms. Code examples in this technical piece will be written using the Python programming language, specifically using Python 3.7, NumPy 1.17 (in JAX), and NetworkX 2.2.
Introduction to Message Passing
Functions on Nodes
Message passing starts with a “function defined over nodes”, which we will denote here as f(v) (for “function of node/vertex v”). What is this, one might ask? In short, this is nothing more than a numeric value of some kind attached to every node in a graph. This value could be scalar, vector, matrix, or tensor.
The semantic meaning of that value is typically defined by the application domain that the graph is being used in. As a concrete example, in molecules, a “function” defined over the molecular graph could be the scalarvalued proton number. Carbon would be represented by the function f(v) = 6. Alternatively, it could be a vector of values encompassing both the atomic mass and the number of valence electrons. In this case, carbon would be represented by the function f(v) = (6, 4).
Visually, one might represent it as follows:
Message Passing
What then is message passing, or, as the deep learning community has adopted, “graph convolution”? At its core, message passing is nothing more than a generic mathematical operation defined between a node’s function value and its neighbors function value.
As an example, one may define a message passing operation to be the summation the function evaluated at a node with the function evaluated on its neighbor’s nodes. Here is a simplistic example, shown using a scalar on water:
Summation is not the only message passing operation that can be defined. In principle, given any node (or vertex) v and its neighbors N(v) values, we may write down a generic function f(v, N(v)) that defines how the function value on each node is to be shared with its neighbors.
Computational Implementations of Message Passing
For simplicity, let us stay with the particular case where the message passing operation is defined as the summation of one’s neighbors values with one’s values.
ObjectOriented Implementation
With this definition in place, we may then define a message passing operation in Python as follows:
1 2 3 4 5 6 7 8 9 10 11 12 

Thinking about computational considerations, we would naturally consider this implementation to be slow, because it involves a forloop over Python objects. If we had multiple graphs over which we wanted message passing to be performed, the typechecking overhead in Python will naturally accumulate, and may even dominate.
Linear Algebra Implementation
How might we speed things up? As it turns out, linear algebra may be useful.
We know that every graph may be represented as an adjacency matrix A
,
whose shape is (n_nodes, n_nodes)
.
As long as we maintain proper node ordering,
we may also define a compatiblyshaped matrix F
for node function values,
whose shape is (n_nodes, n_features)
.
Taking advantage of this,
in order define the “self plus neighbors” message passing operation
in terms of linear algebra operations,
we may then modify A
by adding to it a diagonal matrix of ones.
(In graph terminology,
this is equivalent to adding a selfloop to the adjacency matrix.)
Then, message passing,
as defined above,
is trivially the dot product of A
and F
:
1 2 3 4 5 6 7 8 9 

In principle, variants on the adjacency matrix are possible.
The only hard requirement for the matrix A
is that it has the shape (n_nodes, n_nodes)
.
Adjacency Variant 1: Ndegree adjacency matrix
The adjacency matrix represents connectivity by degree 1. If we take the second matrix power of the adjacency matrix, we get back the connectivity of nodes at two degrees of separation away. More generically:
1 2 3 4 5 6 7 8 

Performing message passing using the Ndegree adjacency matrix effectively describes sharing of information between nodes that are Ndegrees of separation apart, skipping intermediate neighbors.
Adjacency Variant 2: Graph laplacian matrix
The graph laplacian matrix is defined as
the diagonal degree matrix D
(where the diagonal entries are the degree of each node)
minus the adjacency matrix A
: L = D  A
.
This matrix is the discrete analog to the Laplacian operator, and can give us information about the discrete gradient between a node and its neighbors.
Message Passing on Multiple Graphs
Thus far, we have seen an efficient implementation of message passing on a single graph using linear algebra.
How would one perform message passing on multiple graphs, though?
This is a question that has applications in graph neural networks (especially in cheminformatics). For the learning task where one has a batch of graphs, and the supervised learning task is to predict a scalar (or vector) value per graph, knowing how to efficiently message pass over multiple graphs is crucial to developing a performant graph neural network model.
The challenge here, though, is that graphs generally are of variable size, hence it is not immediately obvious how to “tensorify” the operations.
Let us look at a few alternatives, starting with the most obvious (but also most inefficient), building towards more efficient solutions.
Implementation 1: Forloops over pairs of adjacency and feature matrices
If we multiple graphs, they may be represented as a list of feature matrices and a list of adjacency matrices. The message passing operation, then, may be defined by writing a forloop over pairs of these matrices.
1 2 3 4 5 

Because of the forloop, the obvious downside here is the overhead induced by running a forloop over pairs of As and Fs.
Implementation 2: Sparse Matrices
Sparse matrices are an attractive alternative. Instead of treating graphs as independent samples, we may treat them as a single large graph on which we perform message passing. If we order the nodes in our adjacency matrix and feature matrix correctly, we will end up with a block diagonal adjacency matrix, and vertically stacked feature matrices.
If we prepare the multiple graphs as a large disconnected graph,
then we will have a dense feature matrix of shape (sum(n_nodes), n_feats)
,
and a sparse adjacency matrix of shape (sum(n_nodes), sum(n_nodes))
.
Message passing then becomes a sparsedense dot product:
1 2 

The upside here is that message passing has been returned back to its natural form (a dot product). The downsides here are that the data must be prepared as a single large graph, hence we effectively lose what one would call the “sample” (or “batch”) dimension. Additionally, the most widely used deep learning libraries do not support automatic differentiation on sparsedense or densesparse dot products, hence limiting the use of this implementation in deep learning.
Implementation 3: Sizebatched matrix multiplication
An alternative way to conceptualize message passing is to think of graphs of the same size as belonging to a “size batch”. We may then vertically stack the feature and adjacency matrices of graphs of the same size together, and perform a batched matrix multiplication, ensuring that we preserve the sample/batch dimension in the final result.
In terms of Python code, this requires special preparation of the graphs.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 

In this implementation,
we use jax.lax.batch_matmul
,
which inherently assumes
that the first dimension is the sample/batch dimension,
and that the matrix multiplication happens on the subsequent dimensions.
An advantage here is that the number of loop overhead calls in Python is reduced to the number of unique graph sizes that are present in the graph. The disadvantage, though, is that we have a dictionary data structure that we have to deal with, which makes data handling in Python less natural when dealing with linear algebra libraries.
Implementation 4: Batched padded matrix multiplication
In this implementation, we prepare the data in a different way. Firstly, we must know the size of the largest graph aheadoftime.
1 

We then pad every graph’s feature matrix with zeros along the node axis until the node axis is as long as the largest graph size.
1 2 3 4 5 6 7 8 9 

We do the same with every adjacency matrix.
1 2 3 4 5 6 7 8 9 

Finally, we simply stack them into the data matrix:
1 2 

Now, the shapes of our matrices are as follows:
F
takes on the shape(n_graphs, n_nodes, n_feats)
A
takes on the shape(n_graphs, n_nodes, n_nodes)
If we desire to be semantically consistent with our shapes, then we might, by convention, assign the first dimension to be the sample/batch dimension.
Finally, message passing is now trivially defined as a batch matrix multiply:
1 2 

Visually, this is represented as follows:
To this author’s best knowledge, this should be the most efficient implementation of batched message passing across multiple graphs that also supports automatic differentiation, while also maintaining parity with the written equation form, hence preserving readability. The problems associated with a forloop, sparse matrix multiplication, and dictionary carries, are removed. Moreover, the sample/batch dimension is preserved, hence it is semantically easy to map each graph to its corresponding output value. Given the current state of automatic differentiation libraries, no additional machinery is necessary to support sparse matrix products.
The only disadvantage that this author can think of is that zeropadding may not be intuitive at first glance, and that the data must still be specially prepared and stacked first.
Concluding Words
This essay was initially motivated by the myriad of difficulttoread message passing implementations present in the deep learning literature. Frequently, a forloop of some kind is invoked, or an undocumented list data structure is created, in order to accomplish the message passing operation. Moreover, the model implementation is frequently not separated from the data preparation step, which makes for convoluted and mutually incompatible implementations of message passing in neural networks.
It is my hope that while the research field is still in vogue, a technical piece that advises researchers on easilyreadable and efficient implementations of message passing on graphs may help advance research practice. In particular, if our code can more closely match the equations listed in papers, that will help facilitate communication and verification of model implementations.
To help researchers get started, an example implementation for the full data preparation and batched padded matrix multiplies in JAX is available on GitHub, archived on Zenodo.
Acknowledgments
I thank Rif. A. Saurous for our discussion at the PyMC4 developer summit in Montreal, QC, where his laserlike focus on “tensorify everything” inspired many new thoughts in my mind.
Many thanks to my wife, Nan Li, who first pointed me to the linear algebra equivalents of graphs.
I also thank David Duvenaud and Matthew J. Johnson for their pedagogy while they were at Harvard.
Appendix
Equivalence between padded and nonpadded message passing
To readers who may need an example to be convinced that matrix multiplying the padded matrices is equivalent to matrix multiplying the originals, we show the Python example below.
Firstly, without padding:
F = np.array([[1, 0], [1, 1]])
A = np.array([[1, 0], [0, 1]])
M = np.dot(A, F)
# Value of M
# DeviceArray([[1, 0],
# [1, 1]], dtype=int32)
And now, with padding:
pad_size = 2
F_pad = np.pad(
F,
pad_width=[
(0, pad_size),
(0, 0),
]
)
A_pad = np.pad(
A,
pad_width=[
(0, pad_size),
(0, pad_size),
]
)
# F_pad:
# DeviceArray([[1, 0],
# [1, 1],
# [0, 0],
# [0, 0]], dtype=int32)
# A_pad:
# DeviceArray([[1, 0, 0, 0],
# [0, 1, 0, 0],
# [0, 0, 0, 0],
# [0, 0, 0, 0]], dtype=int32)
M_pad = np.dot(A_pad, F_pad)
# M_pad:
# DeviceArray([[1, 0],
# [1, 1],
# [0, 0],
# [0, 0]], dtype=int32)
Thank you for reading!
If you enjoyed this essay and would like to receive earlybird access to more, please support me on Patreon! A coffee a month sent my way gets you early access to my essays on a private URL exclusively for my supporters as well as shoutouts on every single essay that I put out.
Also, I have a free monthly newsletter that I use as an outlet to share programmingoriented data science tips and tools. If you'd like to receive it, sign up on TinyLetter!