Similar to Wasserstein GAN, this is another theory-motivated paper with neat applications to deep learning. Once again, if you are looking for proof details, you are better off reading the original paper. The goal of this post is to give background and motivation.

Why Is This Paper Important?

Hyperparam optimization is a weird problem because everybody has to do it and nobody really likes it. The common options are either grid search, random search, or line search if your parameter is continuous. A mix of those does a pretty good job for most ML algorithms, even deep neural nets, which are a bit notorious for having many hyperparams.

However, I still think it’s worth keeping an eye on hyperparam optimization, for a couple reasons.

  • If hyperparam optimization is better, more aspects of neural net design can be described as a hyperparam and automated. For example, the number of layers can be an explicit hyperparam, instead of something picked by hand. Right now, people don’t do this because it’s not worth doing for most problems, but the trend in research is that everybody pushes at the limits of their tools.
  • Preliminary results like Neural Architecture Search suggests that there is learnable structure in neural net hyperparameters. It’s not yet applicable to anything, but I could see meta-learned models playing a bigger role in the future. At the same time, maybe we don’t need to throw a neural net at everything to get state-of-the-art results. (I like doing that as much as the next person, but machine learning doesn’t always have to mean deep learning.)
  • There are simply a ton of interesting research questions that appear when each data point take hours or days to collect. Similar issues show up in robotics learning - robots are expensive and often need human supervision, which makes it hard to collect the ImageNet-scale datasets that neural nets are so good at.
  • Better hyperparam optimization makes ML more accessible to others, because it reduces the amount of esoteric knowledge needed to get models to work. That’s good because people shouldn’t need to know that esoteric knowledge to solve their problems. It’s bad for me because weird deep learning expertise is one of the few things I’m good at, and I’m not sure I like knowing it could be obsolete down the line. All the more reason to pay attention.

Some Quick Background on Hyperparam Optimization

For two approachable introductions to the subject, I highly recommend two blog posts from Ben Recht’s blog, linked here and here. The key takeaways are

  • Random search is a simple, deceptively strong baseline.
  • Bayesian optimization can outperform random search by a bit.
  • However, if you give random search twice the time, it beats a lot of Bayesian optimization methods. Yes, it’s more compute time, but sometimes buying more machines is easier than integrating clever ideas into your software stack.
  • Successive halving (SH) is a nice extension of random search that lets you run many more hyperparams in the same amount of time, by pruning poor hyperparams early on. You have to be a little careful with how aggressively you prune, but in practice it does pretty well.
    • SH was later extended to the Hyperband algorithm, described here. Hyperband is one of the baseline methods used for comparison. Spearmint, a Bayesian optimization method, is the other main comparision.

Problem Setting

The paper focuses on discrete hyperparameter optimization. Generally, discrete optimization is trickier, and continuous problems can be approximated by discretizing the space, so I think this is an okay choice to make.

The paper further assumes all hyperparams are binary variables with value or . Note you can still do things like allocate hyperparams for the different learning rates you want to try.

Let’s say there are hyperparams. Then given all these assumptions, we want to learn a function , where the input is the hyperparam setting, and the output is the performance of the trained model. In the upcoming sections, we’ll use two different notations.

  • , in which case is some -bit vector.
  • , in which case we interpret as a polynomial of variables, where the variables equal either or .

Polynomial Learning as Compressed Sensing

This is the key guiding framework of the algorithm. Viewing as a polynomial, we learn a sparse, low-degree polynomial that approximates .

What’s the intuition for why you’d want to do this? Well, to be honest, I have no idea why you’d decide to look at compressed sensing, instead of the other methods out there. But I can explain why it makes sense to me, after the fact.

To do better than random search, two things must be true.

  • Your problem must have learnable structure.
  • Your hyperparam optimization methods needs to discover and exploit that latent structure.

All of machine learning can be seen as fitting low-dimensional functions to inputs in high-dimensional space. This gets at why fitting a low-degree polynomial would make sense.

But then why include sparsity? Remember that we’re going to have very few data points, because each data point requires training a neural net to convergence. Sparsity helps with this by reducing the capacity of the polynomial fitting process - it stops it from putting a little bit of weight on thousands of different terms, which is one of the easiest ways to overfit. As a side effect, sparsity tends to make interpreting models easier.

(Aside: this is one of the common complaints about deep learning - it’s hard to interpret much out of the sum of 100 activations. But in practice, most deep learning problems have a lot of data, and enforcing sparsity just ends up hurting performance.)

When deriving the algorithm, we’ll assume that evaluating for a single takes “a long time, but not too long”. By this, we mean functions run in time for a somewhat large , but still run faster than things with exponential runtime.

The Parity Function Basis

To fit a low-degree polynomial, first note that the Boolean functions form an inner product space. Define the inner product as

where the expectation is the uniform distribution over -bit vectors. We can verify this satisfies the inner product definitions.

  • Symmetry:

  • Linearity: for some constant ,

    For functions ,

  • Positive definiteness.

For to be , note , so the only way for to equal is if everywhere.

Next, we want to find an orthonormal basis for this inner product space. For these functions, there’s a well known example. Let be a subset of indicies to . Define as

The functions (known as the parity functions) form an orthonormal basis.

Why is this an orthonormal basis? A set is orthonormal if it satisfies two properties.

  • For every , .
  • For every where , .

Now, we show the parity functions have this property.

In the upcoming sections, sometimes means an index from to , and sometimes means a number from to that should be interpreted as bits of binary. It should be inferable from context.

  • By definition, . Note that or , depending on how many matching bits there are between and . In either case, , so .
  • For any two different subsets , there exists some in one, but not the other. Without loss of generality, let and . We can write as

Take the expectation over , and factor it into the conditional expectation on .

The inner expectation equals , for some constant that doesn’t depend on . Thus we can write the expectation as

Thus, the set is orthonormal. This leaves showing they form a basis. For this, note that there’s an isomorphism between functions and vectors in , where the mapping is

Isomorphisms preserve dimensionality, so the function space must have. must have dimension . There are different subsets of , so the parity functions must span the entire space.

Low Degree Approximation

Because the parity functions form an orthonormal basis, any function over can be decomposed into a sum of parity functions, where the coefficient comes from the inner product. Let be the set of all subsets of to . Then for any ,

At this point we draw a comparison to Fourier series to build some intuition. Any periodic signal that’s sufficiently well behaved can be decomposed into a sum of sinusoids. The sinusoids form an orthonormal basis (which you can prove by throwing enough trigonometry identities at the problem.)

Intuitively, the earlier terms represent low-frequency components of the signal, and the later terms represent high-frequency components. To reconstruct exactly, we should do.

We can’t compute this exactly because the sum is infinite. However, we can approximate the signal by truncating the sum at some maximum

This corresponds to dropping all the high frequency terms. Depending on the signal, this can still be a pretty good approximation.

Now, apply the same motivation to modeling . We can write as

Computing this exactly is intractable because there are subsets. However, note that each term is the product over a choice of indices. When , we get a -degree constant term. When is all numbers from to , we get an -degree term.

So, what if we limited to just the subsets where $$ S \le d$$?

This reduces the number of terms from to , turning an exponentially big problem into a polynomially big one.

The approximation above is the best -degree approximation, if you measure approximation error between and as . But the best approximation isn’t necessarily a sparse one, and once we enforce sparsity, is a good approximation guaranteed to still exist? It turns out the answer is yes. From the paper:

Fact 4. [Man94] Let be such that . Then there exists such that is sparse and . Function is constructed by taking all coefficients of magnitude or larger in ’s expansion as a polynomial.

Not only does this guarantee that a sparse approximation exists, if is a -degree polynomial, is also guaranteed to be degree , because it is formed by selecting terms that already exist in , and those terms must be degree or lower.

Polynomial Recovery Algorithm

Let’s assume we have evaluations of at different points . The first trick for fitting a sparse polynomial is a classic: formulate the problem as a linear regression problem in a larger feature space. There are features, one for each subset with . We want to find coefficients that minimize the mean squared error.

To encourage sparsity, we apply another classic solution - add L1 regularization.

After solving this, we take the coefficients with the largest magnitude, where is a hyperparam for how sparse we want the polynomial to be.

(Yes, the hyperparam optimization method itself has hyperparams. It’s great.)

This gives the main subroutine, called Polynomial Sparse Recovery.

PSR algorithm

When called, it returns a sparse polynomial , and the set of all variables that depends on.

Runtime Bound For PSR

Let be an -bounded function. Let be an orthonormal polynomial basis bounded by . Then the PSR algorithm finds a that’s within of in time with sample complexity .

In this statement, is the size of the polynomial basis. For the special case of parity functions, we have and , giving .

See paper for the proof.

Harmonica: The Full Algorithm

We assume is the error %, and that we want to minimize it. Sample some values by training some models, and fit a sparse polynomial .

Since has at most terms, each of which is degree , it can depend on at most different variables. With the right choice of , brute forcing all possibilities is small enough to be doable. Note that is likely dwarfed by the runtime for doing the linear regression.

However, this only gives settings for the variables that depends on. Thus, the full algorithm proceeds in stages. At each stage, we fit a sparse polynomial , find the settings that minimize , freeze those hyperparams, then iterate in the smaller hyperparam space. Applying this multiple times shrinks the hyperparam space, until it’s small enough to use a baseline hyperparam optimization method, like random search or successive halving.

(In practice, the authors find the best settings instead of just the best one, then pick one of those at random in the later stages. For example, if , and stage 1 decided values for 10 hyperparams, in stage 2 we sample one of the settings to deciding the first 10, then sample randomly for the remaining 20.)

Harmonica algorithm

Experiments

The problem used is CIFAR-10, trained with a deep Resnet model. The model has 39 hyperparams, deciding everything from learning rate to L2 regularization to connectivity of the network, batch size, and non-linearity. To make the problem more difficult, 21 dummy hyperparams are added, giving 60 hyperparams total.

Harmonica is evaluated with 300 samples at each stage (meaning 300 trained models), with degree , sparsity , and . They perform 2-3 stages of PSR (depending on the experiment), and use successive halving as the base hyperparam optimizer.

Results Summary

Harmonica outperforms random search, Hyperband and Spearmint.

Test error

In this plot, the different between Harmonica 1 and Harmonica 2 is that in Harmonica 2, the final stage is given less time. This gives worse performance, but better runtime. The faster version (Harmonica 2) runs 5x faster than Random Search and outperforms it. The slower version (Harmonica 1) is still competitive with other approaches in runtime while giving much better results. Even when the base hyperparam optimizer is random search instead of successive halving, it outperforms random search in under half the time.

Run time

As Harmonica discovers settings for the important hyperparams, the average test error in the restricted hyperparam space drops. Each stage gives another drop in performance, but the drop is small between stage 2 and stage 3 - I’m guessing this is why they decided to only use 2 stages in the timing experiments.

Average test error

To show that the chosen terms are meaningful, the coefficients in each stage are sorted by magnitude, to show which hyperparams influence error the most. Results are shown for a 3-stage Harmonica experiment, where sparsity for the first 2 stages and for the 3rd stage.

Table of important hyperparams

The minimizing settings often line up with human convention. Batch norm should be on (vs off), the activation function should be ReLU (vs sigmoid or tanh), and Adam should be used (vs SGD).

Many of the important hyperparams line up with convention - batch norm should be one, the activation function should be ReLU, and Adam is a better optimizer than SGD. Check the original paper for more details on the hyperparam definition.

One especially interesting term is the one discovered at stage 1-8. The dummy variable is extra and can be ignored. The authors say that in their code, if Optnet and Share gradInput are both true, training becomes unpredictable. The learned is minimized if this term equals , which happens if only one of Optnet and Share gradInput is true at a given time.

Advantages

In each stage of Harmonica, each model can be evaluated in parallel. By contrast, Bayesian optimization techniques are more difficult to parallelize because the derivation often assumes a single-threaded evaluation.

Enforcing hyperparam sparsity leads to interpretability - weights of different terms can be used to interpret which hyperparams are most important and least important. The approach successfully learned to ignore all dummy hyperparams.

Disadvantages

A coworker mentioned that Harmonica assumes a fixed computation budget for each stage, which doesn’t make it as good in an anytime setting (which is a better fit for Bayesian optimization.)

My intuition says that this approach works best when you have a large number of hyperparameters and want to initially narrow down the space. Each stage requires hundreds of models, and in smaller hyperparam spaces, evaluating 100 models with random search is going to enough tuning already. That being said, perhaps you can get away with fewer if you’re working in a smaller hyperparam space.

In the first two stages, Harmonica is run on a smaller 8 layer network, and the full 56 layer Resnet is only trained in the final stage. The argument is that hyperparams often have a consistent effect as the model gets deeper, so it’s okay to tune on a small network and copy the settings to a larger one. It’s not clear whether a similar trick was used in their baselines. If they weren’t, the runtime comparisons arne’t as impressive as they look.

The approach only works if it makes sense for the features to be sparse. This isn’t that big a disadvantage, in my experience neural net hyperparams are nearly independent. This is backed up by the Harmonica results - the important terms are almost all degree 1. (The authors observed that they did need for best performance.)

The derivation only works with discrete, binary features. Extending the approach to arbitrary discrete hyperparams doesn’t look too bad (just take the closest power of 2), but extending to continuous spaces looks quite a bit trickier.

Closing Thoughts

Overall I like this paper quite a bit. I’m not sure how practical it is - the “tune on small, copy to large” trick in particular feels a bit sketchy. But that should only affect the runtime of the algorithm, not the performance. I think it’s neat that it continues to work in empirical land.

One thing that’s nice is that because the final stage can use any hyperparam optimization algorithm, it’s easy to mix-and-match Harmonica with other approaches. So even if Harmonica doesn’t pan out in further testing, the polynomial sparse recovery subroutine could be an interesting building block in future work.