← Latest papers
📊 statistics

Feasibility Determination for Subjective Probability Constraints

This paper proposes a statistically valid procedure that directly utilizes Bernoulli-distributed simulation data to efficiently determine the feasibility of systems under subjective probability constraints with multiple thresholds, outperforming existing methods adapted for normal distributions while offering heuristic approaches for dynamically adjusting thresholds.

Original authors: Taehoon Kim, Sigrun Andradottir, Seong-Hee Kim, Yuwei Zhou

Published 2026-05-27
📖 4 min read☕ Coffee break read

Original authors: Taehoon Kim, Sigrun Andradottir, Seong-Hee Kim, Yuwei Zhou

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 general trying to pick the best strategy from a list of 100 different battle plans. However, you don't know exactly how well each plan will work because war is chaotic and full of luck. You can only run simulations to see what might happen.

Your goal isn't just to find the "best" plan; it's to find the plans that are safe enough to use. You have specific rules, like: "The chance of losing more than 10% of our troops must be less than 5%."

This paper is about how to test these battle plans efficiently when the data you get from simulations is simple: a Yes (1) or a No (0). In the paper's language, this is called "Bernoulli distributed data."

Here is the breakdown of the problem and the authors' solution, using everyday analogies.

The Problem: The "Batching" Bottleneck

Traditionally, statisticians have a rule for testing these kinds of problems: "Don't look at individual coin flips; look at the average of 100 flips at a time." They do this because averages behave nicely (they look like a bell curve), making the math easier.

The authors say this is like trying to taste a soup by only taking a spoonful every hour. It's safe, but it's wasteful.

  • If you need to know if a soup is too salty, you don't need to wait an hour to taste a whole bowl. You can taste a drop immediately.
  • In the simulation world, waiting to gather "batches" of data to make them look "normal" wastes a huge amount of computer time. You might run 1,000 extra simulations just to satisfy a math rule that doesn't actually fit your "Yes/No" data.

The Solution: The "Random Walk" Detective

The authors propose a new method called MPB (Multi-pass Bernoulli Feasibility). Instead of waiting for batches, they treat every single simulation result as a clue immediately.

They use a concept called a Random Walk, which is like a drunk person walking down a hallway with two walls:

  • Wall A (Feasible): If the person hits this wall, the plan is Safe.
  • Wall B (Infeasible): If the person hits this wall, the plan is Unsafe.
  • The Middle: As long as the person is in the middle, you keep walking (running more simulations).

The genius of their method is how they set the walls. Instead of just measuring distance (e.g., "Is the plan 5% better?"), they measure the odds (e.g., "Is the plan 1.5 times more likely to succeed?"). This is more practical because it handles extreme probabilities (like a 99% success rate) much better than simple distance measurements.

The "Subjective" Twist: The Flexible Commander

Real-world decision-makers are rarely rigid. A commander might say:

  1. "I want a 90% chance of victory." (Too hard? No plan works.)
  2. "Okay, let's try 85%." (Still too hard.)
  3. "How about 80%?" (Ah, we found some!)

Old methods forced you to test all these percentages at once, which is slow. The authors' method allows for a Multi-Pass approach:

  • Pass 1: Test a wide range of strict rules (e.g., 90%, 80%, 70%).
  • Pass 2: If you found too many good plans, tighten the rules (try 85%, 82%). If you found none, loosen the rules (try 75%, 70%).

They also invented a way to recycle data. Imagine you tested a plan against a 90% rule. When you later decide to test it against an 85% rule, you don't throw away the first test results. You reuse them. It's like using the same ingredients to bake a cake, then using the leftover batter to make cookies, rather than starting from scratch.

The Results: Speed and Accuracy

The authors ran thousands of experiments to prove their method works.

  • Accuracy: Their method guarantees that they won't make a mistake more than 5% of the time (a standard safety net).
  • Speed: Compared to the old "batching" method (called RF), their new method was 3 to 9 times faster. In one specific example involving inventory management, the new method used only 33% of the computer time required by the old method.
  • The "Heuristic" Bonus: They also showed that their "Multi-Pass" approach (testing loose rules first, then tightening them) is even faster than testing everything at once, saving massive amounts of time when you have many systems to check.

Summary

In short, this paper says: "Stop waiting for big batches of data to make your math easy. Just look at the 'Yes/No' results as they come in, use a smart 'odds-based' walking model to decide if a plan is safe, and reuse your data when you change your mind about the rules."

This saves time, saves computer power, and helps decision-makers find good solutions much faster without losing accuracy.

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 →