A Data Model Is Not Just a “Likelihood”

Summary

The same expression serves two different roles — as a distribution over data, and as a function of parameters — and conflating them costs you the ability to do workflow. The likelihood is all Bayesian inference needs; the data model is what Bayesian data analysis needs. Two worked cases show the gap concretely: analytically integrating out censored observations, and coding a zero-inflated Poisson, both of which produce a likelihood from which the original data model cannot be recovered.

Overview

The distinction (Ch. 5.4, p. 70)

With data fixed and attention on , the function “is sometimes formulated as a function of , the ‘likelihood’ of conditional on .” But “the same mathematical expression is also used to denote the data model conditional on parameters.”

“This duality has led to a sloppy use of the term ‘likelihood’ to denote both, but this is not correct: the function considered as a distribution of the data is different than when used as part of a distribution of parameters.”

The diagnostic example: “many discrete-data models (for example, binary or count data) have continuous likelihoods when considered as functions of the parameters.”

Where the data model — not the likelihood — is required

Generative data models are needed for:

“For some of these, we also need to be able to express the posterior distribution and sample (or, in some cases, analytically integrate) over it.”

Main Content

Where the boundary blurs: latent and censored data

“In simple models, the data model is easy to distinguish from the prior. But with hierarchical and missing data models there is no sharp division between parameters and data, as a model can have latent data that are not observed but are still given a generative model.”

Partial censoring (Ch. 5.4, pp. 70-71)

Observations plus censored observations known only to exceed a threshold :

Here gets the same generative data model as , and has no model at all.

“If we define the model before the data are observed, then it is not possible to say in a model like this where the data model ends and the prior begins. It depends upon which observations are censored, once the data arrive.”

“Measurement error models also have this property, so this isn’t an unusual circumstance.”

How a computational shortcut destroys the data model

One could sample with MCMC alongside the parameters. But it is common to analytically integrate it out:

giving the posterior

under .

“Knowing the likelihood component does not tell us what was the original data model for .”

Different data models integrate to the same likelihood factor. See Incremental Development and Testing - Black Cat Adoptions (Ch. 22) for a case study working through several ways of handling censoring in a survival model.

Where language limitations force you to write the likelihood

Zero-inflated Poisson (Ch. 5.4, p. 71)

The data model — each has probability of being zero, and probability of coming from a Poisson:

Stan does not (yet) support mixture modeling using ~, so the corresponding likelihood must be written directly — and it looks different from the data model:

Note the structure at : the zero could have come from either component, so both paths contribute.

The lesson: “Even if the computation happens to be easier by writing the likelihood directly, it is useful for communication to present the original data model, and in any case the data model is needed for various predictive checking approaches and making actual predictions.”

The zero-inflated negative binomial in LOO Model Checking and Comparison - Roaches (Ch. 24) exercises exactly this structure.

Choosing the data model is a modeling decision too

The overlooked half of model specification (Ch. 5.4, p. 71)

“In treatments of Bayesian statistics, the data model is often assumed known, and there is much discussion of the choice of prior. In real problems, though, the data model needs to be chosen too: the researcher must decide

  • what information to consider as ‘data’ to be modeled,
  • which predictors to include,
  • how the predictors will be included in the model,
  • and choices of parameterization and functional form.

These choices are found also in non-Bayesian modeling, but aspects of them are different, because distributions and parameters may have different interpretations in Bayesian models.”

This is the same point There Is No Safe Haven makes about subjectivity, and it is developed further in Specifying the Data Model and the Prior: “Many writers on statistics strain at the gnat of the prior distribution while swallowing the camel of the likelihood.”

When a wrong data model still works

Similar likelihoods, similar posteriors

“It also often happens that different data models have very similar likelihoods. In such a case, a model can be clearly wrong but still give inferences that are not much different from what would be obtained from a better data model.

For example, even if is discrete, it is possible that the likelihood from a normal model is not much different than a likelihood from a proper discrete-data model, and then there would not be much difference in posterior either.”

The workflow implication: “This partially explains why it can be useful to start with a faster-to-compute normal model for the first results and later in the workflow check whether using a more realistic data model changes the conclusions.”

Demonstrated concretely in Debugging a Model - World Cup Football §23.5, where a continuous score-differential model is compared against a discrete-data model.

Connections

See Also