Use Normal Predictions
post by Jan Christian Refsgaard · 20220109T17:52:49.260Z · EA · GW · 1 commentsThis is a link post for https://www.lesswrong.com/posts/GMCs73dCPTL8dWYGq/usenormalpredictions
Contents
Quick recap about the normal distribution How to make predictions Why do I want to do this How to track your calibration Still not convinced? Advanced Techniques Final Remarks None 1 comment
Making predictions is a good practice, writing them down is even better.
However, we often make binary predictions when it is not necessary, such as
 Biden win popular vote: 91%
 Danish COVID deaths above 10.000 by January 1. 2022: 84%
Alternatively, we could make predictions from a normal distribution, such as ('~' means ‘comes from’):
 Biden’s popular vote ~ N(0.54, 0.03)
 Danish COVID deaths by January 1. 2022 ~ N(15,000, 5,000)
While making "Normal" predictions seems complicated, this post should be enough to get you started, and more importantly to get you a method for tracking your calibration, which is much harder with dichotomous predictions.
The key points are these:
 Predicting from a normal is surprisingly easy.
 Getting an actionable number for how over/under confident you are requires only simple math!
 The normal distribution carries more information than the Bernoulli (binary outcome such as coins) and will therefore give you more information to act on!
Things this post will answer:
 How do I make a normal prediction?
 Why do I want to do this?
 How do I track my calibration?
Quick recap about the normal distribution
The normal distribution is usually written as N(,) has 2 parameters:
 a location parameter (pronounced mu) which is both the most likely and the average value
 a scale parameter (pronounced sigma) which captures uncertainty, high implying high uncertainty
the 689599.7 rule states that:

68% of your predictions should fall in

95% of your predictions should fall in

99.7% of your predictions should fall in
Finally 50% of the predictions should fall within , which can be used as a quick spot check.
How to make predictions
To make a prediction, there are two steps. Step 1 is predicting . Step 2 is using the 689599.7 rule to capture your uncertainty in .
I tried to predict Biden’s national vote share in the 2020 election. From the polls, I got 54% as a point estimate, so that seemed like a good guess for . For I used the 689599.7 rule and tried to see what that would imply for different values of . Here is a table for 25%
Intervals  68%  95%  99.7% 

5256%  5058%  4860%  
5157%  4860%  4563%  
5058%  4662%  4266%  
4959%  4464%  3969% 
implies a 97.5% (95% interval + tail half tail) chance that Biden would get more than 50% of the votes ); I was not that confident. implies a 84% chance that Biden would get more than 50% of the votes (68% + 32%/2), so there is 16% chance Trump wins, I likewise found this too high, so I settled on .
Why do I want to do this
Biden Got 52% of the vote share, which was within 1 sigma of my prediction. There are two weak lessons that I drew from this ONE data point.
 The pollsters screwed up, so I should have regressed towards the mean (50%), such as predicting 53% instead of 54%
 The prediction was exactly from , so the was on the 50%/50% boundary just as expected. This was lucky, but it's weak evidence that the was well chosen.
Imagine I instead had predicted Biden wins (the popular vote) 91%, well guess what he won, so I was right... and that is it. Thinking I should have predicted 80% because the pollsters screwed up seems weird, as that is a weaker prediction and the bold one was right! I would need to predict a lot of other elections to see whether I am over or under confident.
How to track your calibration
Note: In the previous section we used and for predictions. In this section we will use and where i is the index (prediction 1, prediction 2... prediction N). We will use for the calibration point estimate; this means that is a number such as 1.73. In the next post in this series, we will use for the calibration distribution, this means that is a distribution like your predictions and thus has an uncertainty.
I also made a terrible prediction, during the early lock down in 2020. I predicted N(15,000, 5,000) COVID deaths by 2022 in Denmark. It turned out to be 3,200, which is standard deviations away, so outside the 95% interval!
In this section we will transform your predictions to the Unit normal. This is called zscoring, because if all predictions are on the same scale, then they are comparable:
Normally when you convert to zscores you use the data itself to calculate and , which guarantee a N(0,1). Here, we will use our predicted and . This means there will be a discrepancy between and our . This discrepancy describes how under/over confident your intervals are, and thus describes your calibration, such that if = 2 then all your intervals should be twice as wide to achieve
First we zscore our data by calculating how many they are away from the observed data , using this formula:
Second we calculate as the RMSE (root mean squared error) of all predictions:
And that is, let's calculate for my two predictions, first we calculate the variances:
Then we calculate
So if these were my only two predictions, then I should widen my future intervals by 73%. In other words, because is 1.73 and not 1, thus my intervals are too small by a factor of 1.73.
Still not convinced?
Here are some bonus arguments:
 Weak 50/50: Sometimes you are actually 50/50, such as Scott's prediction that Bitcoin had a 5050 shot of going over 3000 in 2019; that could be reformulated as "Bitcoin ~ N(3000, 1500)" such that a price of 10000 counts against the prediction. Now a weak prediction still gives evidence of calibration!
 Overshooting and Undershooting: If Biden had gotten 20 or 80% of the votes, both things would be strong evidence of my prediction being wrong, where the binary predictions can only be 'wrong in one direction'
 High Confidence Predictions are easier to calibrate: In Binary land a 99% prediction is very hard to calibrate because you need to make hundreds of them to get enough data (unless many turn out wrong of course). A Corresponding Normal prediction would have a small σ and thus give as much evidence of calibration as a 60% prediction.
 Right for the Wrong Reason: All of N(50.67, 0.5), N(54, 3), N(58, 6), give Biden a 91% win chance, but for very different reasons, and will thus lead people to update differently after observing .
Advanced Techniques
Sometimes your beliefs do not follow a Normal distribution. For example, the Bitcoin prediction N(3000, 1500) implies I believe there is a 2.5% chance the price will become negative, which is impossible. There are 3 solutions in increasing order of fanciness to deal with this:
 Have different for each direction such as (HN = Half Normal):
This means if it's above then , while if it's below then . If you do this, then you can use "the relevant " when calibrating and ignore the other one, so if the price of bitcoin ended up being then z becomes :
 Often you believe something goes up or down by a factor, such as Bitcoin dropping to half or doubling. For ease of example let imagine that Scott thought there was a 68% chance that Bitcoin’s value would change by less than a factor of 2.
zscoring works the same way, so if the Bitcoin price was 10.000 then:
 (If this makes no sense, then ignore it): Using an arbitrary distribution for predictions, then use its CDF (Universality of the Uniform) to convert to , and then transform to zscore using the inverse CDF (percentile point function) of the Unit Normal. Finally use this as in when calculating your calibration.
Final Remarks
I want you to stop and appreciate that we can get a specific actionable number after 2 predictions, which is basically impossible with binary predictions! So start making normal predictions, rather than dichotomous ones!
As a final note, keep this distinction in mind:
 If the data and the prediction are close, then you are a good predictor
 If the mean prediction error on the zscale is close to 1, then you are a well calibrated predictor.
Getting good at 1 requires domain knowledge for each specific prediction, while getting good at 2 is a general skill that applies to all predictions.
This post we calculated the point estimate based on 2 data points. There is a lot of uncertainty in a point estimate based on two data points, so we should expect the calibration distribution over to be quite wide. The next post in this series will tackle this by calculating a Frequentest confidence interval for and a Bayesian posterior over . This allows us to make statements such as: I am 90% confident that , so it's much more likely that I am badly calibrated than unlucky. With only two data points it is however hard to tell the difference with much confidence.
Finally I would like to thank my editors Justis Mills and eric135 [LW · GW] for making this readable.
1 comments
Comments sorted by top scores.
comment by Charles Dillon (Charles_Dillon ) · 20220111T11:04:39.472Z · EA(p) · GW(p)
Worth noting that Metaculus has the ability to record continuous distribution predictions, including both normal predictions and much more complicated distributions. E.g. https://www.metaculus.com/questions/5301/acityexodus/
If you want to record your predictions for your own questions on Metaculus you can also create private questions here. https://www.metaculus.com/questions/create/