Learn the Basics || Quickstart || Tensors || Datasets & DataLoaders || Transforms || Build Model || Autograd || Optimization || Save & Load Model

Automatic Differentiation with torch.autograd

When training neural networks, the most frequently used algorithm is back propagation. In this algorithm, parameters (model weights) are adjusted according to the gradient of the loss function with respect to the given parameter.

To compute those gradients, PyTorch has a built-in differentiation engine called torch.autograd. It supports automatic computation of gradient for any computational graph.

Consider the simplest one-layer neural network, with input x, parameters w and b, and some loss function. It can be defined in Storch in the following manner:

val x = torch.ones(5)  // input tensor
val y = torch.zeros(3) // expected output
val w = torch.randn(Seq(5, 3), requiresGrad=true)
val b = torch.randn(Seq(3), requiresGrad=true)
val z = (x matmul w) + b
val loss = torch.nn.functional.binaryCrossEntropyWithLogits(z, y)

Tensors, Functions and Computational graph

This code defines the following computational graph:

Example computation graph

In this network, w and b are parameters, which we need to optimize. Thus, we need to be able to compute the gradients of loss function with respect to those variables. In order to do that, we set the requiresGrad property of those tensors.

You can set the value of requiresGrad when creating a tensor, or later by using x.requiresGrad_(true) method.

A function that we apply to tensors to construct computational graph is in fact an object of class Function. This object knows how to compute the function in the forward direction, and also how to compute its derivative during the backward propagation step. A reference to the backward propagation function is stored in gradFn property of a tensor. You can find more information of Function in the documentation.

gradFn is not yet available in Storch.

println(s"Gradient function for z = ${z.gradFn}")
println(s"Gradient function for loss = ${loss.gradFn}")

Computing Gradients

To optimize weights of parameters in the neural network, we need to compute the derivatives of our loss function with respect to parameters, namely, we need $\frac{\partial loss}{\partial w}$ and $\frac{\partial loss}{\partial b}$ under some fixed values of x and y. To compute those derivatives, we call loss.backward(), and then retrieve the values from w.grad and b.grad:

loss.backward()
println(w.grad)
// Some(tensor dtype=float32, shape=[5, 3], device=CPU 
// [[0.2661, 0.1179, 0.0027],
//  [0.2661, 0.1179, 0.0027],
//  [0.2661, 0.1179, 0.0027],
//  [0.2661, 0.1179, 0.0027],
//  [0.2661, 0.1179, 0.0027]])
println(b.grad)
// Some(tensor dtype=float32, shape=[3], device=CPU 
// [0.2661, 0.1179, 0.0027])
  • We can only obtain the grad properties for the leaf nodes of the computational graph, which have requiresGrad property set to true. For all other nodes in our graph, gradients will not be available.
  • We can only perform gradient calculations using backward once on a given graph, for performance reasons. If we need to do several backward calls on the same graph, we need to pass retainGraph=true to the backward call.

Disabling Gradient Tracking

By default, all tensors with requiresGrad=true are tracking their computational history and support gradient computation. However, there are some cases when we do not need to do that, for example, when we have trained the model and just want to apply it to some input data, i.e. we only want to do forward computations through the network. We can stop tracking computations by surrounding our computation code with torch.noGrad block:

var z = torch.matmul(x, w) + b
// z: Tensor[Float32] = tensor dtype=float32, shape=[3], device=CPU 
// [1.3755, -0.6023, -4.8127]
println(z.requiresGrad)
// true
torch.noGrad {
  z = torch.matmul(x, w) + b
}
println(z.requiresGrad)
// false

Another way to achieve the same result is to use the detach() method on the tensor:

val z = torch.matmul(x, w)+b
// z: Tensor[Float32] = tensor dtype=float32, shape=[3], device=CPU 
// [1.3755, -0.6023, -4.8127]
val zDet = z.detach()
// zDet: Tensor[Float32] = tensor dtype=float32, shape=[3], device=CPU 
// [1.3755, -0.6023, -4.8127]
println(zDet.requiresGrad)
// false

There are reasons you might want to disable gradient tracking:

More on Computational Graphs

Conceptually, autograd keeps a record of data (tensors) and all executed operations (along with the resulting new tensors) in a directed acyclic graph (DAG) consisting of Function_ objects. In this DAG, leaves are the input tensors, roots are the output tensors. By tracing this graph from roots to leaves, you can automatically compute the gradients using the chain rule.

In a forward pass, autograd does two things simultaneously:

The backward pass kicks off when .backward() is called on the DAG root. autograd then:

DAGs are dynamic in PyTorch An important thing to note is that the graph is recreated from scratch; after each .backward() call, autograd starts populating a new graph. This is exactly what allows you to use control flow statements in your model; you can change the shape, size and operations at every iteration if needed.

Optional Reading: Tensor Gradients and Jacobian Products

In many cases, we have a scalar loss function, and we need to compute the gradient with respect to some parameters. However, there are cases when the output function is an arbitrary tensor. In this case, PyTorch allows you to compute so-called Jacobian product, and not the actual gradient.

For a vector function $\vec{y}=f(\vec{x})$, where $\vec{x}=\langle x_1,\dots,x_n\rangle$ and $\vec{y}=\langle y_1,\dots,y_m\rangle$, a gradient of $\vec{y}$ with respect to $\vec{x}$ is given by Jacobian matrix:

$$\begin{align}J=\left(\begin{array}{ccc} \frac{\partial y_{1}}{\partial x_{1}} & \cdots & \frac{\partial y_{1}}{\partial x_{n}}\\ \vdots & \ddots & \vdots\\ \frac{\partial y_{m}}{\partial x_{1}} & \cdots & \frac{\partial y_{m}}{\partial x_{n}} \end{array}\right)\end{align}$$

Instead of computing the Jacobian matrix itself, PyTorch allows you to compute the Jacobian Product $v^T\cdot J$ for a given input vector $v=(v_1 \dots v_m)$. This is achieved by calling backward with $v$ as an argument. The size of $v$ should be the same as the size of the original tensor, with respect to which we want to compute the product:

val inp = torch.eye(4, Some(5), requiresGrad=true)
val out = (inp+1).pow(2).t()
out.backward(torch.onesLike(out), retainGraph=true)
println(s"First call\n${inp.grad}")
out.backward(torch.onesLike(out), retainGraph=true)
println(s"\nSecond call\n${inp.grad}")
inp.grad.zero_()
out.backward(torch.onesLike(out), retainGraph=true)
println(s"\nCall after zeroing gradients\n${inp.grad}")

Notice that when we call backward for the second time with the same argument, the value of the gradient is different. This happens because when doing backward propagation, PyTorch accumulates the gradients, i.e. the value of computed gradients is added to the grad property of all leaf nodes of computational graph. If you want to compute the proper gradients, you need to zero out the grad property before. In real-life training an optimizer helps us to do this.

Previously we were calling backward() function without parameters. This is essentially equivalent to calling backward(torch.tensor(1.0)), which is a useful way to compute the gradients in case of a scalar-valued function, such as loss during neural network training.

Further Reading