← Latest papers
📊 statistics

Pliable rejection sampling

Pliable Rejection Sampling (PRS) is a new approach that uses a kernel estimator to learn a sampling proposal, providing a method that produces high-probability i.i.d. samples with a guaranteed number of accepted samples.

Original authors: Akram Erraqabi, Michal Valko, Alexandra Carpentier, Odalric-Ambrym Maillard

Published 2026-04-27
📖 3 min read☕ Coffee break read

Original authors: Akram Erraqabi, Michal Valko, Alexandra Carpentier, Odalric-Ambrym Maillard

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 professional treasure hunter, and your job is to find gold coins scattered across a massive, dark field. To find them, you have a "detector" (the function ff) that tells you exactly how much gold is at any specific spot you point to.

The problem? Every time you use the detector, it costs you \100. If you point it at a patch of dirt and it says "zero gold," you’ve just wasted \100.

The Old Ways: The "Blind Guess" and the "Strict Rules"

Before this paper, treasure hunters had two main ways to work:

  1. Simple Rejection Sampling (The Blind Guess): You just walk around the field randomly, pointing your detector everywhere. Because most of the field is empty, you spend almost all your money pointing at dirt. You find a few coins, but you go broke very quickly.
  2. Adaptive Rejection Sampling (The Strict Rules): This is like having a rulebook that says, "You can only look for gold if the field is shaped like a perfect smooth hill." If the field has two hills, or a weird jagged shape, the rulebook breaks, and you’re back to guessing blindly.

The New Way: Pliable Rejection Sampling (The "Smart Map")

The authors of this paper created Pliable Rejection Sampling (PRS). Instead of guessing blindly or following strict rules, PRS uses a "Smart Map" strategy.

Step 1: The Reconnaissance Mission
Instead of spending your whole budget looking for gold, you take a small portion of your money and do a quick, random sweep of the field. You aren't looking for gold yet; you're just trying to get a "vibe" for where the gold might be.

Step 2: Drawing the Sketch
You take the data from that quick sweep and use a mathematical tool (a "kernel estimator") to draw a rough sketch of the field. It’s not a perfect map, but it’s a great start. It shows you, "Hey, there seems to be a pile of gold over in that corner!"

Step 3: The "Pliable" Envelope
Now, instead of walking randomly, you create a "safety net" (an envelope) based on your sketch. This net is "pliable"—meaning it’s flexible. It follows the shape of your sketch but adds a little extra "padding" around the edges to make sure you don't accidentally miss a coin because your sketch was slightly off.

Step 4: The Efficient Hunt
Now you spend the rest of your money pointing your detector only inside that safety net. Because your net is shaped almost exactly like the gold piles, almost every time you point the detector, you find gold!

Why is this a big deal? (The "Guarantee")

The "magic" of this paper isn't just that it's faster; it's that the authors proved it mathematically.

In most methods, you hope you're being efficient. With PRS, the authors provide a guarantee: as you spend more money, the amount of "wasted" guesses (pointing at dirt) becomes almost zero. Eventually, almost every dollar you spend results in finding a gold coin.

Summary in a Nutshell

  • Old way: Throwing darts at a board in the dark.
  • PRS way: Turning on a dim light, sketching the board, and then throwing darts only at the bullseye.

It’s a way to sample from complex, "difficult" mathematical shapes without needing to know exactly what those shapes look like beforehand, and without wasting massive amounts of computing power.

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 →