How Many Shots Are Enough for a Quantum Circuit?

This paper introduces IncrementalExecution, a black-box online framework that dynamically optimizes the number of quantum circuit shots by identifying the point of diminishing returns to balance execution costs and result fidelity without relying on specific circuit structures or noise models.

Original authors: Giuseppe Bisicchia, Alessandro Bocci, Ernesto Pimentel, Antonio Brogi

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

Original authors: Giuseppe Bisicchia, Alessandro Bocci, Ernesto Pimentel, Antonio Brogi

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

The Big Problem: The "Blind Taste Test"

Imagine you are a chef trying to perfect a new soup recipe. You can't taste the whole pot at once; you have to take small spoonfuls (samples) to guess the flavor.

  • The Soup: A quantum computer circuit.
  • The Spoonfuls: "Shots." In quantum computing, you can't just run a program once and get a perfect answer. Because of the weird nature of quantum physics, you have to run the same program many times to get a reliable picture of the result.
  • The Dilemma: If you take too few spoonfuls, your guess about the flavor might be wrong. If you take too many, you waste time and money (since quantum computers are expensive to rent).

The big question the authors ask is: How many spoonfuls do you actually need before you can stop tasting and be confident you know the flavor?

The Old Way vs. The New Way

The Old Way (The Guesswork):
Previously, developers had to guess a fixed number of shots (e.g., "Let's run this 10,000 times") based on rules of thumb or complex math formulas that assumed they knew exactly how the quantum computer would behave.

  • The Flaw: Quantum computers are noisy and unpredictable. Sometimes 10,000 shots are overkill (wasting money); other times, they aren't enough (giving a bad result). It's like guessing you need exactly 50 spoonfuls of soup without ever tasting the first one.

The New Way (The "Diminishing Returns" Approach):
The authors introduce a new framework called IncrementalExecution. Instead of guessing a number, they suggest a smart, step-by-step approach.

Think of it like filling a bucket with a leaky hose:

  1. You start pouring water (running shots).
  2. You check the water level (the data) after every few seconds.
  3. You keep pouring as long as the water level is rising significantly.
  4. The Stop Signal: The moment you notice that adding more water barely changes the level anymore, you stop. You've reached the "point of diminishing returns."

How It Works (The "Black Box" Magic)

The authors call their method a "black box" approach. This means they don't need to know:

  • How the soup recipe is written (the circuit structure).
  • How the stove is broken (the noise model of the hardware).

They just look at the results coming out.

  1. Run a small batch: Execute the circuit 50 times.
  2. Check the pattern: Look at the results.
  3. Run another batch: Execute it 50 more times.
  4. Compare: Did the new 50 shots change the overall picture much?
    • Yes? Keep going.
    • No? The pattern has stabilized. Stop now. You saved money!

The "Diminishing Returns" Concept

The paper relies on a simple economic idea: Diminishing Returns.
Imagine you are studying for a test.

  • First hour: You learn 50% of the material. Huge gain!
  • Second hour: You learn another 30%. Good gain.
  • Third hour: You learn 10%.
  • Fourth hour: You learn 1%.
  • Fifth hour: You learn 0.1%.

At some point, the effort (time/money) isn't worth the tiny gain in knowledge. The paper's software automatically finds that exact moment for quantum circuits and tells you to stop.

What They Found (The Results)

The authors tested this idea on 33,750 different settings across 180 different quantum circuits and simulated noisy computers. They ran 7.3 million experiments in total.

Here is what they discovered:

  1. It Works: They can reliably stop early without losing accuracy.
  2. It Saves Resources: Their smart method often uses far fewer shots than the "safe" fixed numbers or the strict math formulas used before.
  3. It's Flexible: They found that different "rules" work better for different types of problems.
    • Analogy: Sometimes you need a very sensitive spoon to taste a delicate soup (strict settings). Other times, a rougher spoon is fine for a hearty stew (loose settings). Their system lets you choose the right "spoon" for the job.
  4. It Handles Noise: Even though quantum computers are messy and noisy, this method is robust enough to handle the chaos without needing to know the specific cause of the noise.

Why This Matters

In the world of quantum computing, time is money. Every extra second a quantum computer runs costs the user real cash. By figuring out exactly when to stop, this framework helps users:

  • Save money.
  • Get results faster.
  • Avoid wasting resources on unnecessary calculations.

Summary

The paper presents a smart, automatic "stop-watch" for quantum computers. Instead of blindly running a program a million times just to be safe, this new tool watches the results in real-time. As soon as the results stop changing significantly, it says, "Okay, we have enough data. Let's stop." It's a practical, cost-saving tool that works without needing to understand the complex physics behind the machine.

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 →