# [Stats4EA] Expectations are not Outcomes

post by matthewp · 2020-05-18T22:59:03.754Z · EA · GW · 5 commentsThis is the first in what might become a bunch of posts picking out issues from statistics and probability of relevance to EA. The format will be informal and fairly bite-size. None of this will be original, hopefully.

**Expectations are not outcomes**

Here we attempt to trim back the intuition that an expected value can be safely thought of as a representative value of the random variable.

**Situation 1**

A Rademacher random variable X takes the value 1 with probability 1/2 and otherwise -1. Its expectation is zero. We will almost surely never see any value other than -1 or 1.

This means that the expected value might not even be a number the distribution *could* produce. We might not even be able to get arbitrarily close to it.

Imagine walking up to a table in a casino and betting that the next roll of a die will be 7/2.

**Situation 2**

Researchers create a natural language simulation model. Upon receiving a piece of text as stimulus it outputs a random short story. What is the expectation of the story?

Let’s think about the first word. There will be some implied probability distribution over a dictionary. Its expectation is some *fractional combination of every word* in the dictionary. Whatever that means, and whatever it is useful for, it is not the start of a legible story - and should not be used as such.

What is the expected length of the story? What would a solution to that problem mean? Could one, for example, print the expected story?

**Situation 3**

Distributions with very fat tails. For instance, the Cauchy distribution has an undefined expectation.

**Implication**

It is tempting to freely substitute an expectation in as a representative of a random variable. Suppose we used the following procedure in a blanket fashion:

- We are faced with a decision depending on an uncertain outcome.
- We take the expected value of the outcome.
- We use the expectation as a scenario to plan around.

Step three is unsafe in principle - even if sometimes not in practice.

If there is a next time (the length of this series is currently fractional) I hope to touch on some scenarios less easily dismissed as the concerns of a pedant.

## 5 comments

Comments sorted by top scores.

## comment by Denis Drescher (Telofy) · 2020-05-19T12:11:00.135Z · EA(p) · GW(p)

I’ve found Christian Tarsney’s “Exceeding Expectations” insightful when it comes to recognizing and maybe coping with the limits of expected value.

The principle that rational agents should maximize expected utility or choiceworthiness is intuitively plausible in many ordinary cases of decision-making under uncertainty. But it is less plausible in cases of extreme, low-probability risk (like Pascal's Mugging), and intolerably paradoxical in cases like the St. Petersburg and Pasadena games. In this paper I show that, under certain conditions, stochastic dominance reasoning can capture most of the plausible implications of expectational reasoning while avoiding most of its pitfalls. Specifically, given sufficient background uncertainty about the choiceworthiness of one's options, many expectation-maximizing gambles that do not stochastically dominate their alternatives "in a vacuum" become stochastically dominant in virtue of that background uncertainty. But, even under these conditions, stochastic dominance will not require agents to accept options whose expectational superiority depends on sufficiently small probabilities of extreme payoffs. The sort of background uncertainty on which these results depend looks unavoidable for any agent who measures the choiceworthiness of her options in part by the total amount of value in the resulting world. At least for such agents, then, stochastic dominance offers a plausible general principle of choice under uncertainty that can explain more of the apparent rational constraints on such choices than has previously been recognized.

See also the post/sequence by Daniel Kokotajlo, “Tiny Probabilities of Vast Utilities” [EA · GW]. I’m linking to the post that was most valuable to me, but by default it might make sense to start with the first one in the sequence. ^^

Replies from: matthewp## ↑ comment by matthewp · 2020-05-19T18:20:33.616Z · EA(p) · GW(p)

Thanks - that last link was one I'd come across and liked when looking for previous coverage. My sole previous blog post was about Pascal's Wager. I'd found though when speaking about it that I was assuming too much for some of the audience I wanted to bring along; notwithstanding my sloppy writing :D So, I'm going to attempt to stay focused and incremental.

## comment by omernevo (omernev@gmail.com) · 2020-05-19T11:09:56.035Z · EA(p) · GW(p)

Thanks for writing this! It's always useful to get reminders for the sort of mistakes we can fail to notice even if when they're significant.

I also think it would be a lot more helpful to walk through how this mistake could happen in some real scenarios in the context of EA (even though these scenarios would naturally be less clear-cut and more complex).

Lastly, it might be worth noting the many other tools we have to represent random variables. Some options off the top of my head:

* Expectation & variance: Sometimes useful for normal distributions and other intuitive distributions (eg QALY per $ for many interventions at scale).

* Confidence intervals: Useful for many cases where the result is likely to be in a specific range (eg effect size for a specific treatment).

* Probabilities for specific outcomes or events: Sometimes useful for distributions with important anomalies (eg impact of a new organization), or when looking for specific combinations of multiple distributions (eg the probability that AGI is coming soon and also that current alignment research is useful).

* Full model of the distribution: Sometimes useful for simple \ common distributions (all the examples that come to mind aren’t in the context of EA, oh well).

One small note: The examples are there to make the category clearer. These aren’t all cases where expected value is wrong \ inappropriate to use. Specifically, for some of them, I think using expected value works great.

Replies from: matthewp