← Latest papers
📊 statistics

Translating predictive distributions into informative priors

This paper proposes a method using global multi-stage Bayesian optimization to translate prior information specified for observable or model-derived quantities into informative joint priors for latent parameters by minimizing the discrepancy between the elicited distribution and the prior predictive distribution.

Original authors: Andrew A. Manderson, Robert J. B. Goudie

Published 2026-03-18
📖 6 min read🧠 Deep dive

Original authors: Andrew A. Manderson, Robert J. B. Goudie

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a master chef trying to recreate a famous dish from a memory. You know exactly how the final meal should taste, smell, and look (the observable quantity). However, the recipe you have to work with is written in a secret code involving obscure chemical reactions and hidden ingredients (the model parameters).

The problem? You don't know the exact amounts of the secret ingredients to put in the pot to get that perfect taste. If you guess wrong, the dish might be inedible, or the model might behave in ways that defy reality (like a survival model predicting that people live forever, or a growth model predicting a child grows to 10 feet tall).

This paper, by Andrew Manderson and Robert Goudie, proposes a clever new way to solve this "secret ingredient" problem. Here is the breakdown in simple terms:

The Problem: The "Black Box" of Expert Knowledge

Usually, when statisticians build complex models, they need to set up priors (their initial guesses about the hidden ingredients).

  • The Easy Way: Ask an expert, "How much salt do you think is in the soup?" and just use that number. This works for simple recipes.
  • The Hard Way: In complex models (like predicting human growth or cancer cures), the "salt" isn't a single number. It's a hidden chemical reaction. Experts can't tell you the value of a hidden variable; they can only tell you what the final soup should look like. "I know the soup should be salty, but I don't know the exact grams of salt."

If you try to force the hidden variables to match the expert's guess directly, the math often breaks, or you end up with a recipe that makes no sense.

The Solution: The "Taste-Tester" Algorithm

The authors propose a method to translate the expert's description of the final dish (the target distribution) into the correct recipe (the informative prior for the hidden parameters).

Think of their method as a robotic taste-tester that uses a trial-and-error loop:

  1. The Setup: The robot has a recipe book with a few knobs (hyperparameters) it can turn. It doesn't know the right settings yet.
  2. The Guess: The robot turns the knobs to a random setting and cooks a "test batch" of soup (generates a prior predictive distribution).
  3. The Taste Test: It compares its test batch to the expert's description of the perfect dish.
    • Is it too salty? (The tails of the distribution don't match).
    • Is it too bland? (The middle is wrong).
    • It calculates a "discrepancy score" (how far off the taste is).
  4. The Optimization: The robot uses a smart search engine (called Bayesian Optimization) to tweak the knobs. It doesn't just guess randomly; it learns from previous failures to find the best settings faster.
  5. The Double Goal: The robot has two goals:
    • Goal A (Faithfulness): Make the soup taste exactly like the expert described.
    • Goal B (Uniqueness/Simplicity): If there are two ways to make the soup taste right, pick the one that is "safest" or most uncertain (so we don't accidentally assume we know more than we do).

The Three "Kitchen" Examples

The paper tests this robot in three different scenarios:

1. The "Cure" Model (Survival Analysis)

  • The Scenario: Imagine a medical study where some patients are "cured" and never get sick again, while others might still get sick later. The data is messy because we stop watching some patients before they get sick (censoring).
  • The Challenge: The expert says, "5% of people are cured, and the rest get sick within 20 years." But the math model is tricky because "cured" and "censored" look the same in the data.
  • The Result: The robot successfully adjusted the hidden knobs to create a recipe that perfectly mimicked the expert's 5% cure rate, even though the math was complex and mixed (some people cured, some not).

2. The "R-Squared" Puzzle (Linear Regression)

  • The Scenario: In a standard math model, experts often know how much of the "variance" (the wiggle room) the model should explain (called R2R^2). They don't know the specific numbers for the coefficients (the hidden ingredients).
  • The Challenge: Translating "I want the model to explain 80% of the data" into specific numbers for the hidden variables is like trying to guess the exact weight of every grain of sand in a bucket just by knowing the bucket feels heavy.
  • The Result: The robot tried different "shrinkage" recipes (ways to keep the ingredients small and tidy). It found that complex, flexible recipes worked best to match the expert's R2R^2 goal, while simple recipes failed to capture the nuance.

3. The Human Growth Chart (Nonlinear Regression)

  • The Scenario: Predicting how a human grows from age 2 to 18. The growth isn't a straight line; it's a curve with spurts.
  • The Challenge: If you give the model a "flat" guess (no prior knowledge), it might predict a child grows to 10 feet tall or shrinks to 2 feet. It needs a "guardrail" (a prior) to keep it realistic.
  • The Result: The robot took the expert's idea of "average height at age 10 is 140cm" and worked backward to find the perfect starting recipe. It successfully created a model that grew children realistically, avoiding the "10-foot tall" disaster.

Why This Matters

Before this paper, if you had a complex model and an expert who only knew the outcome but not the math, you were stuck. You either had to guess blindly or use a "flat" prior (which is like cooking with no salt, hoping the ingredients are perfect).

This method is like a universal translator. It takes the expert's "I know what the result should look like" and translates it into the "Here is the exact recipe to get there."

The Catch:
Sometimes, there isn't just one perfect recipe. There might be two different sets of ingredients that both make the soup taste right. The paper admits this and suggests a way to pick the "safest" one, but it acknowledges that sometimes the math just can't pinpoint a single unique answer.

In a Nutshell

The authors built a smart, automated system that acts as a translator between "what we know about the world" and "the hidden math we need to run." It ensures that when we build complex computer models, they respect the real-world facts we already know, preventing them from going off the rails.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →