Constraint residuals, graph posteriors, and determinant-corrected full-space targets in Bayesian inverse problems

This paper demonstrates that in finite-dimensional Bayesian inverse problems with equality constraints, sampling via penalized residuals in the full parameter-state space yields a posterior distinct from the reduced-space posterior due to a missing Jacobian determinant factor, and it derives specific determinant corrections required to ensure that zero-noise residual limits correctly recover the graph-lifted reduced posterior.

Original authors: Jonathon Cottom, Emilia Olsson

Published 2026-06-09
📖 5 min read🧠 Deep dive

Original authors: Jonathon Cottom, Emilia Olsson

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 trying to solve a mystery. You have a set of clues (data) and a theory about how the world works (a mathematical model). Your goal is to figure out the true "secret ingredient" (the parameter) that caused the clues you see.

In the world of science, this is called a Bayesian inverse problem. Usually, scientists try to solve this by looking at the "secret ingredient" directly. But sometimes, the math is so hard that they try a different trick: they look at the secret ingredient and the result it produces together, and they just punish any answer where the result doesn't match the rules.

This paper, written by Jonathon Cottom and Emilia Olsson, points out a subtle but dangerous trap in that "different trick." They show that simply punishing the wrong answers isn't enough; you might accidentally punish the right answers too, just because of how you wrote the math.

Here is the breakdown using everyday analogies:

1. The Two Ways to Solve the Puzzle

Imagine you are trying to find the perfect recipe for a cake (the parameter). You know the cake must rise to a specific height (the state equation).

  • The "Reduced" Way (The Clean Approach): You assume that for every recipe, there is exactly one height the cake will reach. You calculate that height first, then check if it matches your goal. This is the "gold standard" but can be very slow and computationally expensive.
  • The "Full-Space" Way (The Penalty Approach): You write down the recipe and the height together. You tell your computer: "If the height is wrong, give it a big penalty score." You hope that by making the penalty huge, the computer will only keep the recipes where the height is perfect.

2. The Trap: The "Volume" Problem

The authors discovered that the "Full-Space" way has a hidden flaw.

Imagine you are trying to find a needle in a haystack.

  • The Problem: If you change the way you measure the "wrongness" of the height (for example, measuring it in inches instead of centimeters, or squaring the error), you change the volume of the space where the "wrong" answers live.
  • The Consequence: Even though the "perfect" recipes (the ones where the height is exactly right) are the same in both cases, the probability of picking a specific perfect recipe changes.

The Metaphor:
Think of the "perfect" recipes as a thin, flat sheet of paper floating in 3D space.

  • If you use a "naive" penalty (just squaring the error), the math accidentally stretches or squishes the air around that sheet. It makes some parts of the sheet look "thicker" (more likely) and other parts "thinner" (less likely) just because of how you measured the error.
  • The result? You end up with a biased list of recipes. You might think a specific cake recipe is the best, not because it fits the data, but because your math accidentally made that spot on the "sheet" look bigger.

3. The Solution: The "Determinant Correction"

The paper provides a fix. It's like adding a specific "volume adjustment" knob to your math.

  • The Fix: Before you apply the penalty, you must multiply your math by a specific number (called the determinant of the Jacobian).
  • What it does: This number acts like a counter-weight. If your measurement method squished the space, this number puffs it back up. If it stretched the space, this number squeezes it back down.
  • The Result: Once you add this correction, the "Full-Space" method gives you the exact same list of best recipes as the "Reduced" (gold standard) method.

4. Why This Matters

The authors aren't saying the "Full-Space" method is bad. In fact, it's very popular because it's often easier to run on computers.

However, they are saying: You cannot just assume that "zero error" equals "correct probability."

  • Feasibility vs. Calibration: Getting the error to zero is like making sure you are standing on the right street (Feasibility). But getting the correct probability is like knowing exactly which house on that street you should knock on (Calibration).
  • The Warning: If you use advanced computer methods (like ADMM or MCMC) to solve these problems, you must include this "volume correction." If you don't, your computer might be very efficient at finding the right street, but it will be knocking on the wrong doors.

Summary in One Sentence

When using computer tricks to solve complex scientific puzzles by punishing errors, you must add a specific mathematical "volume correction" to ensure you aren't accidentally biasing your results just because of how you measured the error.

The Paper's Core Message:

  1. Don't confuse "zero error" with "correct answer."
  2. Algebraically equivalent ways of writing an equation can lead to different answers if you don't fix the volume.
  3. The Fix: Multiply your penalty by the "Jacobian determinant" (a specific number that accounts for how the math stretches space).
  4. The Tool: The authors created a software package called detcorr to help scientists check if they have applied this fix correctly.

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 →