by jbco
1 min read

1

This is a special post for quick takes by jbco. Only they can create top-level comments. Comments here also appear on the Quick Takes page and All Posts page.
2 comments, sorted by Click to highlight new comments since:
[-]jbco10

I have been digging causality recently, and I cannot understand what the "do-operator" does. Like I understand how it relates to the notion of intervention, like "what happens to our system when this happens", but I don't understand the difference with a simple "conditioned on/knowing" operator. 

I feel like the semantic difference is that the "knowing" operator always relies on the probability that X happens, whereas do(X) is more deterministic.

Is my intuition right or somehow right? Or did I get something wrong?

AFAIK the distinction is that:

  • When you condition on a particular outcome for , it affects your probabilities for every other variable that's causally related to , in either direction.
    • You gain information about variables that are causally downstream from  (its "effects"). Like, if you imagine setting  and then "playing the tape forward," you'll see the sorts of events that tend to follow from  and not those that tend to follow from some other outcome .
    • And, you gain information about variables that are causally upstream from  (its "causes").  If you know that , then the causes of  must have "added up to" that outcome for . You can rule out any configuration of the causes that doesn't "add up to" causing , and that affects your probability distributions for all of these causative variables.
  • When you use the do-operator to set  to a particular outcome for X, it only affects your probabilities for the "effects" of , not the "causes."  (The first sub-bullet above, not the second.)

For example, suppose hypothetically that I cook dinner every evening. And this process consists of these steps in order:

  • "": considering what ingredients I have in the house
  • "": deciding on a particular meal to make, and cooking it
  • "": eating the food
  • "": taking a moment after the meal to take stock of the ingredients left in the kitchen

Some days I have lots of ingredients, and I prepare elaborate dinners. Other days I don't, and I make simple and easy dinners.

Now, suppose that on one particular evening, I am making instant ramen (). We're given no other info about this evening, but we know this.

What can we conclude from this?  A lot, it turns out:

  • In , I'll be eating instant ramen, not something else.
  • In , I probably didn't have many ingredients in the house. Otherwise I would have made something more elaborate.
  • In , I probably don't see many ingredients on the shelves (a result of what we know about ).

This is what happens when we condition on .

If instead we apply the do-operator to , then:

  • We learn nothing about , and from our POV it is still a sample from the original unconditional distribution for .
  • We can still conclude that I'll be eating ramen afterwards, in .
  • We know very little about  (the post-meal ingredient survey) for the same reason we know nothing about .

Concretely, this models a situation where I first survey my ingredients like usual, and am then forced to make instant ramen by some force outside the universe (i.e. outside our W/X/Y/Z causal diagram). 

And this is a useful concept, because we often want to know what would happen if we performed just such an intervention!

That is, we want to know whether it's a good idea to add a new cause to the diagram, forcing some variable to have values we think lead to good outcomes.

To understand what would happen in such an intervention, it's wrong to condition on the outcome using the original, unmodified diagram – if we did that, we'd draw conclusions like "forcing me to make instant ramen would cause me to see relatively few ingredients on the shelves later, after dinner."