# UML IV: Linear Predictors

by sil ver 9 min read29th Dec 2019No comments

# 13

(This is the fourth post in a series on Machine Learning based on this book. Click here for part one; or if you have some background knowledge, this post might work as a standalone read.)

The mission statement for this post is simple: we wish to study the class of linear predictors. There are linear correlations out there one might wish to learn; also linear stuff tends to be both efficient and simple, so they may be a reasonable choice even if the real world is not quite linear. Furthermore, one can build more sophisticated classifiers by using linear predictors as building blocks (but not in this post).

In school, a function is linear iff you can write it as . In higher math, a function is linear iff for all . In the the case of and , this is the case iff it can be written as for some parameter vector . So the requirement is stronger – we do not allow the constant term the school definition has – but one also considers higher dimensional cases. The case where we do allow a constant factor is called affine-linear, and we also say that a function is homogeneous iff , which (in the case of linear functions) is true iff there is no nonzero constant factor.

In Machine Learning, the difference between linear and affine-linear is not as big of a deal as it is in other fields, so we speak of linear predictors while generally allowing the inhomogeneous case. Maybe Machine Learning is more like school than like university math ;)

For and some , a class of linear predictors can be written like so:

Let's unpack this. Why do we have an inner-product here? Well, because any function can be equivalently written as , where . The inner-product notation is a bit more compact, so we will prefer it over writing a sum. Also note that, for this post, bold letters mean "this is a vector" while normal letters mean "this is a scalar". Secondly, what's up with the ? Well, the reason here is that we want to catch a bunch of classes at once. There is the class of binary linear classifiers where but also the class of linear regression predictors where . (Despite what this sequence has looked like thus far, Machine Learning is not actually just about binary classification.) We get both of them by changing . Concretely, we get the linear regression functions by setting , i.e. the function that sends all positive numbers to 1 and all negative numbers to (and the numbers which are zero, well we'll just ignore those). The notation for any set denotes the indicator function that sends all elements in to 1 and all others in its domain to 0.

For the sake of brevity, one wants to not write the constant term but still have it around, and to this end, one can equivalently write the class as

where it is implicit that . Then the final part of the inner product will add the term , so will take on the role of in the previous definition.

We still need to model how the environment generates points. For this section, we assume the simple setting of a probability function over only and true function of the environment. We also need to define empirical loss functions for a training sequence . For binary classification, we can use the usual one that assigns the number . Since we will now look at more than one loss function, we will have to give it a more specific name than , so we will refer to it as , indicating that every element is either correctly or incorrectly classified (we call this the 0-1 loss even though the label set is now . For regression, this is of course a terrible function; hitting the precisely correct element in is not a reasonable expectation and indeed the probability mass of the hitting it event might well be 0 – and also, if is the correct answer, then is a better guess than . So instead, we want to penalize the predictor based on how far it went off the mark. If , then we define the squared distance loss function as and the absolute distance loss function as .

# Binary Linear Classification

A binary linear classifier separates the entire space in two parts along a hyperplane. This is quite easy to visualize. In the homogeneous case, the hyperplane will go through the origin, whereas in the inhomogeneous case, it may not.

(These two pictures aren't self-made.)

If one draws the vector that defines the classifier into these images (ignoring the fact that these aren't homogeneous for now), it would go orthogonal to the hyperplane. Why is this? Well actually, the feature vector comes first and then each point is measured by its similarity to the feature vector (that's what the inner product does – it measures similarity of direction and is also proportional to length). If it's similar enough, it gets classified as positive. So if we begin in the red region (where stuff is classified as ) and move along the vector , we move toward the green region (where stuff is classified as ). If, at the point at which we're directly at the boundary, we move orthogonal to , we will stay on this boundary, because moving orthogonal to neither makes us more nor less similar to . Thus, the separating hyperplane is orthogonal to .

In linear classification problems, we say that a problem is separable iff there exists a vector whose predictor gets all points in the training sequence right. Actually, in the book, this distinction is also frequently made for other learning tasks, where a problem is called realizable iff there exists a perfect predictor, but I found that this extra detail wasn't worth the complexity it introduced, so I ignored it. But it is more important in this case. One reason is that the assumption is unusually plausible, because the space might be extremely high dimensional. Why is that? Well, suppose we models documents as vectors, where there is one dimension for every possible term (so kind of for every word in the dictionary but not exactly), and one sets the coordinate for the word "crepuscular" to the number of appearances of the word "crepuscular" in the document. With dimensions at hand, it might not be so surprising if a hyperplane classifies all domain points perfectly.

So. How do we train a linear classifier? The book discusses two different algorithms. For both, we shall first assume that we are in the homogeneous case. We start with the Perceptron algorithm.

## The Perceptron algorithm

Since our classifier is completely determined by the choice of , we will refer to it as . Thus .

Recall that measures how similar a label point is to and classifies it as a 1 iff it's similar enough (and as a otherwise). This leads to a very simple algorithm: we start with ; then at iteration we take some pair that is not classified correctly – i.e. where either even though or even though – and we set . So if was classified as even though , then we add , thereby making more similar to than was; and if was classified as 1 even though , then we subtract , thereby making less similar to than was. In both cases, our classifier updates into the right direction. And that's it; that's the perceptron algorithm.

It's not obvious that this would ever terminate (because while updating towards one point will make the predictor better about that point, it might make it worse about other points), but if the problem is separable, then it actually does; always. The proof is kind of interesting and kind of boring, so I'll present a proof sketch that includes the key ideas but hides some of the non-key details.

The main idea is highly non-trivial. We assume there is no point on the hyperplane, then we begin by choosing a vector whose predictor classifies everything correctly (which exists because we assume the separable case) and also has scalar product at least with every positive point (take one that satisfies the first condition and divide it by the smallest norm of any positively labeled point). Now we observe that the similarity between and increases as increases. This is so because , and the term is positive because is by assumption such that .

So let's say we've established that grows sufficiently quickly. Next we show that grows sufficiently slowly, and in particular, slower than the previous term. Next, we observe that is obviously a constant and thus doesn't grow at all. Finally, we observe that because that's the famous Cauchy-Schwartz inequality. So we have an inequality where the left side grows faster than the right but is always smaller – this means it can only grow for so long, and that's the proof. We obtain a bound that depends on the norm of the smallest vector such that for all domain points , and on the largest norm of any domain point. This bound might be good or it might not, depending on the case at hand. Of course, the algorithm always finish faster than this bound in practice.

## Linear Programming

Linear programming is an oddly chosen name for a problem of the following form:

where and and are given. So we have a particular direction, given by , and we want to go as far into this direction as possible; however, we are restricted by a set of constraints – namely the many constraints that follow from the equation . Each constraint is much like the predictor from the previous section; it divides the entire space into two parts along a hyperplane, and it only accepts points in one of the two halves. The set of points which are accepted by all constraints is called the feasible region, and the objective is to find the point in the feasible region that is farthest in the direction of .

Here is a visualization for and :

Once we hit the triangle's right side, we cannot go any further in precisely the direction of , but going downward along that side is still worth it, because it's still "kind of" like – or to be precise, if is the vector leading downward along the rightmost side of the triangle, then , and therefore points which lie further in this direction have a larger inner product with . Consequently, the solution to the linear program is at the triangle's bottom-right corner.

The claim is now that finding a perfect predictor for a separable linear binary classification problem can be solved by a linear program. Why is this? Well for one, it needs to correctly classify some number of points, let's say , so it needs to fulfill conditions, which sounds similar to meeting constraints. But we can be much more precise. So far, we have thought of the element which determines the classifier as a vector and of all domain elements as points, but actually they are the same kind of element in the language of set theory. Thus, we can alternatively think of each domain element as a vector and of our element determining the classifier as a point. Under this perspective, each splits the space in two halves along its own hyperplane, and the point needs to lie in the correct half (for all hyperplanes) for it to classify all 's correctly. In other words, each behaves exactly like a linear constraint.

Thus, if , then we can formulate our set of constraints as simply (not because we want to avoid points on the hyperplane), where

i.e. the matrix whose row vectors are either the elements (if or the elements scaled by (if ). The -th coordinate of the vector equals precisely , and this is the term which is always positive iff the point was classified correctly, because then has the same sign as .

We don't actually care where in the feasible region we land, so we can simply set some kind of meaningless direction like .

So we can indeed rather easily turn our classification problem into a linear program, at least in the separable case. The reason why this is of interest is that linear programs have been studied quite extensively and there are even free solvers online.

## The inhomogeneous case

If we want to allow a constant term, we simply add a at the end of every domain point, and search for a vector that solves the homogeneous problem one dimension higher. This is why the difference of homogeneous vs inhomogeneous isn't a big deal.

# Linear Regression

Linear regression is where we actually need some linear algebra. And also vector calculus.

Recall that, in linear regression, we have and and a predictor for some is defined by the rule . Finally, recall that the empirical squared loss function is defined as . (We set .) The is not going to change where the minimum is, so we can multiply with to get rid of it; then the term we want to minimize looks like this:

In order to find the minimum, we have to take the derivative with regard to the vector . For a fixed , the summand is . Now the derivative of a scalar with respect to a vector is defined as

so we focus on one coordinate and compute the derivative of the such a summand term with regard to . By applying the chain rule, we obtain . This is just for one summand; for the entire sum we have . So this is the -th coordinate of a vector that needs to be zero everywhere. The entire vector then simply looks like this:

.

Now through a process that I haven't yet been able to gain any intuition on, one can reformulate this as , where is the matrix whose column vectors are the , and .

Now if is invertible the problem is easy; if not then it is still solvable, since one can prove that is always in the range of (but the proof is not that interesting, or at least not for me). It helps that is symmetric.

# Logistic Regression

Binary classification may be inelegant in sort of the same way that committing to a hypothesis class ahead of time is elegant – we restrict ourselves to a binary choice, and throw out all possibility of expressing uncertainty. The difference is that it may actually be desirable in the case of binary classification – if one just has to go with one of the labels, then we can't do any better. But quite often, knowing the degree of certainty might be useful. Moreover, even if one does just want to throw out all knowledge about the degree of certainty for the final classifier, including it might still be useful during training. A classifier that gets 10 points wrong, all of which firmly in the wrong camp, might be worse choice than a classifier which gets 11 points wrong, all of which near the boundary (because it is quite plausible that the first predictor just got "lucky" about its close calls and might actually perform worse in practice).

Thus, we would like to learn a hypothesis which, instead of outputting a label, outputs a probability that the label is , i.e. a hypothesis of the form where . For this, we need to be of the form , and obviously it should be monotonically increasing. There are many plausible candidates; one of them is the sigmoid function defined by the rule . Its plot looks like this:

In practice, one could put a scalar in front of the to adjust how confident our predictor will be.

How should our loss function be defined for logistic regression? In the case of , we want to penalize probability mass, and in the case of , we want to penalize the missing probability mass to 1. Both is achieved by setting

This is how it looks in the case of (the case of is symmetrical):