- Getting started
- Custom functions
- Recurrent nets
- Logging training
- Visualising network graphs
- Probabilistic programming
- Stochastic gradients
They claim certain fancy applications are easier in pytorch’s dynamic graph construction style, which resembles (in outcome if not implementation details) the dynamic styles of jax, most julia autodiffs, and tensorflow in “eager” mode.
PyTorch has a unique [sic] way of building neural networks: using and replaying a tape recorder.
Most frameworks such as TensorFlow, Theano, Caffe and CNTK have a static view of the world. One has to build a neural network, and reuse the same structure again and again. Changing the way the network behaves means that one has to start from scratch. [… Pytorch] allows you to change the way your network behaves arbitrarily with zero lag or overhead.
Of course the overhead is not truly zero; rather they have shifted the user overhead baseline down a little compared to tensorflow. Discounting their hyperbole, it still provides relatively convenient autodiff.
The price we pay is that they have chosen different names and calling conventions for all the mathematical functions I use than either tensorflow or numpy, who already chose different names than one another (for no good reason as far as I know), so there is pointless friction in swapping between these frameworks. Presumably that is a tactic to low-key engineer a captive audience.
An incredible feature of pytorch is its documentation, which is clear and consistent and somewhat comprehensive. That is hopefully no longer a massive advantage over Tensorflow whose documentation was garbled nonsense when last I was using it.
There is (was?) some bad advice in the manual:
nnexports two kinds of interfaces — modules and their functional versions. You can extend it in both ways, but we recommend using modules for all kinds of layers, that hold any parameters or buffers, and recommend using a functional form parameter-less operations like activation functions, pooling, etc.
Important missing information:
If my desired loss is already just a composition of existing functions, I don’t need to define a
And: The given options are not a binarism but two things you need to do in concert. A better summary would be:
If you need to have a function which is differentiable in a non-trivial way, implement a Function
If you need to bundle a Function with some state or differentiable parameters, additionally wrap it in a
Some people claim you can also create custom layers using plain python functions. However, these don’t work as layers in an
nn.Sequentialmodel at time of writing, so I’m not sure how to take this advice.
It’s just as well it’s easy to roll your own recurrent nets because the default implementations are bad
The default RNN layer is heavily optimised using cuDNN, which is sweet, but for some complicated technical reason I do not give an arse about,
only have a choice of 2 activation functions, and neither of them is “linear”.
Fairly sure this is no longer true. However, the default RNNs are still a little weird, and assume a 1-dimensional state vector. A DIY approach might fix this. Recent pytorch includes JITed RNN which might even make this DIY style performant. I have not used it.
Easier: just use lighting if that fits the workflow.
Also I have seen visdom promoted? This pumps graphs to a visualisation server. Not pytorch-specific, but seems well-integrated.
Visualising network graphs
Fiddly. The official way is via ONNX.
conda install -c ezyang onnx pydot # or pip install onnx pydot
Then one can use various graphical model diagrams things.
brew install --cask netron # or pip install netron brew install graphviz
pip install git+https://github.com/szagoruyko/pytorchviz
from pytorchviz import make_dot y = model(x) make_dot(y, params = dict(model.named_parameters()))
PyHessian is a pytorch library for Hessian based analysis of neural network models. The library enables computing the following metrics:
- Top Hessian eigenvalues
- The trace of the Hessian matrix
- The full Hessian Eigenvalues Spectral Density (ESD)
Provided quantities include:
- Individual gradients from a mini-batch
- Estimates of the gradient variance or second moment
- Approximate second-order information (diagonal and Kronecker approximations)
Motivation: Computation of most quantities is not necessarily expensive (often just a small modification of the existing backward pass where backpropagated information can be reused). But it is difficult to do in the current software environment.
Lightning is a common training/utility framework for Pytorch.
Lightning is a very lightweight wrapper on PyTorch that decouples the science code from the engineering code. It’s more of a style-guide than a framework. By refactoring your code, we can automate most of the non-research code.
To use Lightning, simply refactor your research code into the LightningModule format (the science) and Lightning will automate the rest (the engineering). Lightning guarantees tested, correct, modern best practices for the automated parts.
- If you are a researcher, Lightning is infinitely flexible, you can modify everything down to the way
.backwardis called or distributed is set up.
- If you are a scientist or production team, lightning is very simple to use with best practice defaults.
Why do I want to use lightning?
Every research project starts the same, a model, a training loop, validation loop, etc. As your research advances, you’re likely to need distributed training, 16-bit precision, checkpointing, gradient accumulation, etc.
Lightning sets up all the boilerplate state-of-the-art training for you so you can focus on the research.
These last two paragraphs constitute a good introduction to the strengths and weaknesses of lightning: “Every research project starts the same, a model, a training loop, validation loop” stands in opposition to “Lightning is infinitely flexible”. >An alternative description with different emphasis “Lighting can handle many ML projects that naturally factor into a single training loop but does not help so much for other projects.”
If my project does have such a factorisation, Lightning is extremely useful and will do all kinds of easy parallelisation, natural code organisation and so forth. But if I am doing something like posterior sampling, or nested iterations, or optimisation at inference time, I find myself spending more time fighting the framework than working with it.
If I want the generic scaling up, I might find myself trying one of the generic solutions like Horovod.
Like python itself, much messy confusion is involved in making everything seem tidy and obvious.
Trainer class is hard to understand because it is an object defined across many files and mixins with confusing names.
One useful thing to know is that a
Trainer has a
model member which contains the actual
LightningModule that I am training..
If I subclass
ModelCheckpoint then I feel like the
on_save_checkpoint method should be called as often as
_save_model; but they are not.
TODO: investigate this.
on_train_batch_end does not get access to anything output by the batch AFAICT, only the epoch-end callback gets the
output argument filled in.
See the code comments.
One can hack the backward gradient to impose them, but why not just use one of the pre-rolled ones by Szymon Maszke ?
Einops makes life better; it reshapes and operates on tensors in an intuitive and explicit way. It is not specific to pytorc, but the best tutorials are for pytorch:
fastai is a deep learning library which provides practitioners with high-level components that can quickly and easily provide state-of-the-art results in standard deep learning domains, and provides researchers with low-level components that can be mixed and matched to build new approaches. It aims to do both things without substantial compromises in ease of use, flexibility, or performance. This is possible thanks to a carefully layered architecture, which expresses common underlying patterns of many deep learning and data processing techniques in terms of decoupled abstractions. These abstractions can be expressed concisely and clearly by leveraging the dynamism of the underlying Python language and the flexibility of the PyTorch library. fastai includes:
- A new type dispatch system for Python along with a semantic type hierarchy for tensors
- A GPU-optimized computer vision library which can be extended in pure Python
- An optimizer which refactors out the common functionality of modern optimizers into two basic pieces, allowing optimization algorithms to be implemented in 4–5 lines of code
- A novel 2-way callback system that can access any part of the data, model, or optimizer and change it at any point during training
- A new data block API
Like other deep learning frameworks, there is some basic NLP support in pytorch; see pytorch.text.
flair is a commercially-backed NLP framework.
I do not do much NLP but if I did I might use the helpful utility functions in AllenNLP.
Outside of NLP there is a system of params and registrable which is very handy for defining various experiments via easy JSON config. Pro-tip from Aladsair Tran: use YAML, it is even nicer because it can handle comments.
That is handy, but beware, AllenNLP is a heavy dependency because it imports megabytes of code that is mostly about NLP, and some of that code has fragile dependencies. Perhaps the native pytorch lightning YAML config is enough.
Apparently you use normal python garbage collector analysis.
A snippet that shows all the currently allocated Tensors:
import torch import gc for obj in gc.get_objects(): try: if torch.is_tensor(obj) or (hasattr(obj, 'data') and torch.is_tensor(obj.data)): print(type(obj), obj.size()) except Exception as e: pass