7 Applications in science, medicine, and operations research

10 min read

Aside, Card, CardGrid, LinkCard, Steps, Tabs, TabItem, Badge, } from '@astrojs/starlight/components';

Core idea

Probability is not a topic that lives only in textbooks of coin tosses and dice — it is the working language of modern science, medicine, and operations. The same handful of tools introduced in earlier topics (the Addition and Multiplication Laws, independence, the Laws of Large Numbers, Gaussian limits, Bayes' rule, expected utility) become enormously powerful when pointed at the messy real world. The numbers feeding into the model are rarely known to many decimal places, but as the statistician George Box put it, all models are wrong, but some are useful.

Author's framing: The way we interpret probabilities can shift with context — frequentist, subjective, propensity — but the calculus is the same. The applications in this topic all reduce, eventually, to the same small set of rules manipulated under different names.

This topic walks through that translation. It shows how a botanist's puzzle about pollen became Einstein's proof that atoms exist; how casinos lent their name to a numerical method for the bomb; how repeating a 0 three times turns a noisy channel into a near-perfect one; how a prospective parent decides whether to risk an amniocentesis; and how a queue of cars at a petrol station, the lifetime of a light bulb, and the spread of a disease all yield to the same probabilistic skeleton.

Why it matters

Most of the apparently fancy machinery of applied science — finite-element simulations, randomised clinical trials, error-correcting codes in your phone's modem, the call-centre staffing model, the survival curve in a drug trial — is probability theory wearing a domain costume. Recognising the costume is liberating: once you see that a Markov chain underwrites both the page-rank algorithm and the recovery curve from an infectious disease, you stop having to learn each field from scratch. You start asking the right probabilistic question and let the discipline supply the parameters.

From precision to good-enough

A theme runs through every example: you rarely get a precise number out, and you rarely need one. What you need is the right shape — does this distribution have a heavy tail? Is the variance bounded? Is the next state independent of the past? Once the shape is fixed, simulation or a small calculation gives you a usable answer. Box's aphorism is a working motto, not a hedge.

Why simulation beat closed form

Many of these problems used to be the province of mathematicians who could solve the integrals. The arrival of cheap random-number generators rearranged the field: an undergraduate with a laptop can now answer questions about polymer chains, queue lengths, or reliability under load that defeated the closed-form analysts of 1950. The deep ideas (laws of large numbers, central limit theorem) are unchanged. What changed is that simulation became a respectable first move, not a last resort.

Key takeaways

Mental model — probability applications by domain

Mental model — probability applications by domain

Practical application

Picking the right tool for the question

A useful diagnostic is to ask, before reaching for any formula, what is being averaged, and over what?

Pick one wrong and the answer can be qualitatively misleading — assuming independence when there is contagion is the canonical failure mode in epidemiology, finance, and reliability alike.

When to simulate instead of solve

  1. State the question precisely. "What is the most likely number of distinct values in 37 spins of a roulette wheel?" is answerable; "Is roulette fair?" is not.

  2. Identify the random inputs. What distributions do they follow, and are they independent of each other? Estimate the parameters from data, not intuition.

  3. Write the simplest simulator you can. A loop that samples inputs, runs the model, records the output, and repeats.

  4. Run enough trials. Precision grows like the square root of the number of replicates (de Moivre). One million trials gives you about three significant figures.

  5. Cross-check. Wherever a closed-form answer is available, even for a simplified version of the problem, compare. Discrepancies usually mean a bug in the simulator, not a flaw in the theory.

  6. Report uncertainty. A single point estimate is a trap — give a Monte Carlo confidence interval.

When simulation is the wrong move

Worked walk-throughs

Science — Brownian motion as a random walk

Robert Brown saw pollen grains jittering in water in 1827; eighty years later Einstein explained why. Imagine a particle making one step left or right per tick, each direction equally likely. After many steps, its position is the sum of many independent +1/-1 random variables; the Central Limit Theorem says the sum is approximately Gaussian. Squeeze the step size down and the tick frequency up in just the right ratio and the discrete random walk becomes the continuous Brownian motion: position at time t is normally distributed with mean zero and variance proportional to t. In three dimensions, the same logic applies independently per axis. Einstein's quantitative predictions about the magnitude of the jiggle let Jean Perrin measure Avogadro's number a few years later — and ended any serious doubt that atoms were real.

The same random-walk skeleton underwrites diffusion in physics, the Black-Scholes equation in finance, and the noise in a galvanometer.

Science — Genetics and epidemiology

Mendelian genetics is a probability problem dressed in biology. Cross two heterozygous parents and each offspring independently inherits one allele from each — the 3:1 ratio of dominant to recessive phenotypes follows from a tree of independent binary draws. Over a population, the Hardy-Weinberg equilibrium describes allele frequencies as a stationary distribution, exactly the language we will reuse for Markov chains below.

Epidemiology is the same logic, scaled up. A simple SIR model divides a population into Susceptible, Infected, and Recovered; transitions between states happen with rates set by contact patterns and recovery times. The reproduction number R — expected secondary infections from a single case — is a single summary statistic with outsized policy weight: R below 1 and the outbreak fades; above 1 and it grows. Realistic models add age structure, contact networks, and stochastic noise, but the probabilistic chassis is unchanged.

Medicine — Bayes at the bedside

Consider the amniocentesis decision that the statistician Juanjuan Fan and her partner faced. Maternal age and a blood test gave a prior probability of Down's syndrome of 1 in 80. An encouraging ultrasound updated that, via Bayes' rule, to 1 in 120. Amniocentesis itself would give a definitive answer — but the procedure carries a 1 in 200 risk of miscarrying a healthy foetus. Should they take the test?

Expected utility is the framework, but the utilities are not monetary — they are the parents' preferences over four outcomes: healthy birth, Down's birth, miscarriage of a healthy foetus, and termination after a positive test. Assign numerical utilities to each outcome, weight by the conditional probabilities under each action, and the action with the higher expected utility wins. The point is not that the maths makes the choice for you; it is that the maths forces you to be explicit about the trade-offs that intuition tends to leave fuzzy.

The same template runs through clinical decisions about screening, biopsy, and adjuvant therapy.

Medicine — Clinical trials

A randomised controlled trial is a probability-engineered comparison. Randomisation makes the two groups (treatment, control) statistically equivalent on every variable, observed or not. Blinding removes placebo and observer effects. The trial then tests a precise hypothesis: that two distributions (outcomes under treatment versus control) differ by more than chance can plausibly explain. Sample size is chosen so the test has a desired power — the probability of detecting a real effect of a given size.

Survival analysis adds time: how long until the event of interest? The Kaplan-Meier curve and the Cox proportional-hazards model are workhorses, both built on the probability that a patient who has survived to time t survives the next interval. Adaptive trial designs go further, updating randomisation probabilities as data accumulates — a Bayesian generalisation of the classical fixed-sample test.

Operations research — Queueing and reliability

Paul, the petrol-station owner, wants to know how many pumps to install. The relevant inputs — arrival rate of cars, distribution of service times, probability that a frustrated driver leaves — are routinely measurable. The output — expected queue length, lost custom, profit per pump — drops out of a queueing simulation or, in nice cases, from the closed-form formulas of M/M/k queueing theory. The same model staffs call centres, sizes server farms, and times the green phase of traffic lights.

Reliability engineering is the dual: instead of arrivals into a system, components fail out of it. A light bulb's lifetime follows a distribution (often Weibull); a redundant array of bulbs lasts much longer than any individual one. Failure trees combine component reliabilities into system reliability; the Apollo program institutionalised the technique. The probabilistic skeleton is again the same — independent events, rare-event distributions, expected values.

Operations research — Markov chains and error-correcting codes

A Markov chain is a process where the next state depends only on the current one, not the full history. The transition matrix encodes the probabilities. Many of the topic's examples are Markov chains in disguise — the random walk, the SIR model, the queue, the genetics drift model. Long-run behaviour collapses to a single object, the stationary distribution, which can usually be computed by solving a small linear system. Google's PageRank was, originally, the stationary distribution of a Markov chain on the web graph.

Error-correcting codes use redundancy the way reliability uses redundant components. Send each bit three times — 000 for 0, 111 for 1 — and decode by majority vote. A 1% channel error rate, raised to the third power and recombined via the binomial, collapses to about 0.03%: a 30-fold improvement at a 3x bandwidth cost. Real codes (Hamming, Reed-Solomon, LDPC, polar) achieve much better trade-offs, but the principle — buy reliability with redundancy — is the same.

Example: A simple Markov chain for customer behaviour

Suppose a coffee shop classifies each customer on a given day as one of three states: new, returning, lapsed. From historical data the manager estimates daily transition probabilities:

| From / To | New | Returning | Lapsed | | --------- | ---- | --------- | ------ | | New | 0.10 | 0.70 | 0.20 | | Returning | 0.00 | 0.85 | 0.15 | | Lapsed | 0.05 | 0.30 | 0.65 |

This is a Markov chain on three states. The manager wants to know two things. First, what fraction of customers will be in each state in the long run, regardless of where they started? That is the stationary distribution — solve the matrix equation that says the distribution does not change after a day, and you find roughly 1% new, 67% returning, 32% lapsed. Second, what is the expected time before a new customer first lapses? That is a hitting-time calculation on the same chain, again a small linear system.

Notice what the model bought: the manager went from "lots of customers come and go" to a quantitative answer about steady-state behaviour and time-to-lapse, using nothing more than a 3x3 matrix and a probability skeleton. The same chassis with different states answers questions about machine wear, disease progression, search-engine traffic, or the genetic drift of an allele. That is the topic's punchline: the calculus is the same.

Caveats

Continue exploring

Tags