 # Calibrating Classifier Probabilties

You’ve built your classifier, run cross-validation and have a super high AUC. So you are done right? Maybe not.

Most classifiers output a score of how likely an observation is to be in the positive class. Usually these scores are between 0 and 1 and get called probabilities. However these probabilities often do not reflect reality, e.g. a probability of 20% may not mean it has a 20% chance of happening, it could have a 10%, 50%, 70%, etc. chance of happening. Our aim should be that our model outputs accurately reflect posterior probabilities $$P(Y=1|x)$$.

In the post we will mainly focus on binary classifiers. Later in the post will will talk about how to extend these ideas to mutliclass problems.

# Why it happens

Our models can output inaccurate probabilities for a variety of reasons:

• Flawed model assumptions (e.g. independence in a Naive Bayes Model)
• Hidden features not available at training time
• Deficiencies in the learning algorithm.

In terms of learning algorithms, as noted in Niculescu-Mizil et al and through my own research:

• Naive Bayes tends to push probabilities toward the extremes of 0 and 1.
• SVMs and boosted trees tend to push probabilities away from 0 and 1 (toward the centre)
• Neural networks and random forests tend to have well calibrated probabilities.
• Regularisation also tends to push probabilities toward the centre.

# Do we care?

Whether or not we want well calibrated probabilities depends entirely on the problem we are trying to solve.

If we only need to rank observations from most likely to least likely, then calibration is unnecessary.

Examples of problems I have worked on where calibrated probabilities are extremely important:

• Loan default prediction – Banks will generally be setting thresholds on the probabilities, auto-reject if probability of default is above 30%, etc.
• Ad Click Prediction – Decided what ad to show, how much to bid. You might use a baseline Click Through Rate (CTR), and compare your prediction to this to see how much more you are willing to pay for this ad impression. 1
• Demographics Estimation of Websites – Imagine you have predictions of gender/ages, as probabilities, for a number of web users. Estimating the gender distribution on a website, can be done by just averaging the probabilities of the users seen on the site. Any bias in the probabilities, will generate a bias in your estimate.

# Visualisation

A reliability diagram is a relatively simple technique for visualising how well calibrated our classifier is.  As described in Niculescu-Mizil et al:

On real problems where the true conditional probabilities are not known, model calibration can be visualized with reliability diagrams (DeGroot & Fienberg, 1982). First, the prediction space is discretized into ten bins. Cases with predicted value between 0 and 0.1 fall in the first bin, between 0.1 and 0.2 in the second bin, etc.
For each bin, the mean predicted value is plotted against the true fraction of positive cases. If the model is well calibrated the points will fall near the diagonal line.

Below we provide a piece of R code for producing relibability diagrams. Here we generalise the number of bins to be a user defined parameter.

In the figure below we show an example reliability plot. Ideally the reliability plot (red line) should be as close to the diagonal line as possible. As there is significant deviation from the diagonal, calibrating the probabilities will possible help. It is also worth mentioning that if you take the mean of the score distribution, it should ideally be close to the prior.

# Techniques for calibration

## Overfitting

The most important step is to create a separate dataset to perform calibration with. Our steps for calibration are:

• Split dataset into test and train
• Split the train set into model training and calibration.
• Train the model on train set
• Score test and calibration set
• Train the calibration model on calibration set
• Score the test set using calibration

How much data to use for calibration will depend on the amount of data you have available. The calibration model will generally only be fitting a small number of parameters (so you do not need a huge volume of data). I would aim for around 10% of your training data, but at a minimum of at least 50 examples.

## Platt Scaling

Platt Scaling essentially involves fitting a logistic regression on the classifier output. Originally developed to fit probabilities to the outputs of SVM 2, it is also well suited to the output of most other classifiers.

The reliability diagram below shows the original reliability plot (green) and after Platt Scaling (red).

The Platt Scalding should not change the rank of the observations, so measures such as AUC will be unaffected. However, measures like Log Loss 3 will be improved. In this example, Log Loss was originally 0.422 and improved to 0.418. In Platt’s original paper suggests , instead of using the original {0,1} targets in the calibration sample, it suggests to mapping to:

$$t_+=\frac{N_+ + 1}{N_+ + 2}$$

$$t_-=\frac{1}{N_-+2}$$

where $$N_+$$  and $$N_-$$ are the number of positive and negative examples in the calibration sample.

To some extent this introduces a level of regularisation. Imagine if you only gave probabilities of either 0 or 1 and you correctly predicted all examples. Your Log Loss would be zero. With Platt’s transformation, you Log Loss would be non-zero. As the Log Loss is what you are optimising when fitting the logistic regression, a level of regularisation is introduced.

In my experiments, this transformation had little to no effect on the reliability diagram and Log Loss, so seems an unnecessary step. It may be useful if you have very few examples and overfitting is more of a concern (therefore regularisation would help). You could also use a ridge or lasso regression.

## Isotonic Regression

With Isotonic Regression you make the assumption:

$$y_i = m(f_i) + \epsilon_{i}$$

where $$m$$ is an isotonic (monotonically increasing or decreasing) function. This is the exact same assumptions we would use for least squares, except $$m$$ is now a isotonic function instead of linear.

Below is an R example of how to perform isotonic regression using the isoreg function.

In the figure below we show an example of the sort of function fitted by the isotonic regression model: Notice how it goes up in steps instead of a smooth curve. To smooth the fit, we perform a linear interpolation between each step. In the reliability plot above, the original uncalibarated scores are shown in green and the isotonic regression scores are shown in red. In this example we find isotonic regression actually made it worse. The Log Loss for instance went from 0.422 to 0.426. The AUC was also reduced.

# Multiclass Classification

What happens if you have more than two classes? Firstly I would recommend visualising the problem as a series of reliability diagrams. For k classes, you can create k reliability diagrams.

Secondly, you can take the score for each of your k classes and plug them into a multinomial logistic regression. The superb glmnet package implements a multinomial logistic regression. You can set the regularisation parameter to something quite small. One word of caution, if you have many classes, overfitting can become an issue. At this point it is worth optimising the regularisation parameter.

If your favourite machine learning model (e.g. SVM) doesn’t directly support multi-class classification, you can fit a 1 vs. all set of classifiers and then plug each of those scores into the  multinomial logistic regression.

# Summary

Classifier probability calibration can be an important step in your machine learning pipeline. The first step is to always visualise and see how much of an issue you have. In general I have found Platt Scaling to be the simplest and most effective approach to most calibration of classification problems.

2. See Platt’s original paper: http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.41.1639
3. Log loss definition: https://www.kaggle.com/wiki/LogarithmicLoss

## 6 thoughts on “Calibrating Classifier Probabilties”

1. Pablo says:

Hi Daniel,

IS IT POSSIBLE TO DO A PARAMETER EXPLORATION WHERE THE SCORE FUNCTION (MAKE_SCORE) IS SOMETHING THAT CALIBRATES THE PROBABILITIES NOT (NECESSARILY) THE BINARY CLASSIFICATION??
SO IT WILL SEARCH FOR A COMBINATIONS OF PARAMETERS FOR A CERTAIN MODEL TRAIN-CALIBRATE AND THEN CHECK IF THE CALIBRATION IS CORRECT IN THE TEST SET.

I think that the question is better explained in this post:
http://stats.stackexchange.com/questions/178125/machine-learning-how-do-we-usually-select-the-best-combination-of-parameters-to?noredirect=1#comment337351_178125

2. dn says:

Hi Pablo,

If I have understood correctly, I think the answer is yes.

How I would set it up is, split the data into train and calibration. Build your model on the train. Consider that model now fixed and don’t change it (this will mean you calibration step will never change the AUC performance of your model).

By then minimising the Log Loss on the calibration set (apply CV on the calibration data), you will be improving the how well calibrated it is. So in your reliability plots, the lines should get closer to the diagonal.

Dan

3. Diego de Las Casas says:

Hi,

Thanks for the post! I can’t find references to isotonic regression for calibration using R anywhere…

I used your code as a base for mine, but found a bug in the fit.isoreg function and thought you should know about it:

In line 22 you wrote:

This does not work, sometimes the lower step will be closer than the upper step and the value will be assigned to a step lower.
I it changed to:

upper.step.n j))

which always get the smallest adjusted.knot that is bigger than j.

Hope it helps!

Thanks again,
Diego

4. Diego de Las Casas says:

Hi,

Thanks for the post! I can’t find references to isotonic regression for calibration using R anywhere…

I used your code as a base for mine, but found a bug in the fit.isoreg function and thought you should know about it:

In line 22 you wrote:

This does not work, sometimes the lower step will be closer than the upper step and the value will be assigned to a step lower.
I it changed to:

upper.step.n j))

which always get the smallest adjusted.knot that is bigger than j.

Hope it helps!

Thanks again,
Diego

P.S. — for some reason my first comment did not have the right correction. Sorry for the recomment.

1. Diego de Las Casas says:

Got what is going wrong, the comment is being treated as html.

The line is:
1. dn says: