knitr::opts_chunk$set( collapse = TRUE, comment = "#>" )
if(!requireNamespace("fabricatr", quietly = TRUE)) { install.packages("fabricatr") } library(CausalQueries) library(fabricatr) library(knitr)
Here is an example of a model in which X
causes M
and M
causes Y
. There is, in addition, unobservable confounding between X
and Y
. This is an example of a model in which you might use information on M
to figure out whether X
caused Y
making use of the "front door criterion."
The DAG is defined using dagitty
syntax like this:
model <- make_model("X -> M -> Y <-> X")
We might set priors thus:
model <- set_priors(model, distribution = "jeffreys")
You can plot the dag thus.
plot(model)
Updating is done like this:
# Lets imagine highly correlated data; here an effect of .9 at each step data <- fabricate(N = 5000, X = rep(0:1, N/2), M = rbinom(N, 1, .05 + .9*X), Y = rbinom(N, 1, .05 + .9*M)) # Updating model <- model |> update_model(data, refresh = 0)
Finally you can calculate an estimand of interest like this:
query_model( model = model, using = c("priors", "posteriors"), query = "Y[X=1] - Y[X=0]", ) |> kable(digits = 2)
This uses the posterior distribution and the model to assess the average treatment effect estimand.
Let's compare now with the case where you do not have data on M
:
model |> update_model(data |> dplyr::select(X, Y), refresh = 0) |> query_model( using = c("priors", "posteriors"), query = "Y[X=1] - Y[X=0]") |> kable(digits = 2)
Here we update much less and are (relatively) much less certain in our beliefs precisely because we are aware of the confounded related between X
and Y
, without having the data on M
we could use to address it.
Say X
, M
, and Y
were perfectly correlated. Would the average treatment effect be identified?
Any scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.