A deterministic world you still cannot compute
2026-07-26 · Dynamics & Unpredictability
The "butterfly effect" is almost always read as "small things can change the world." The original claim runs closer to the opposite: you can never know where the butterfly is — so even in a world governed entirely by iron law, with no randomness anywhere, long-range prediction is already out.
Weather forecasts reach out about a week. They do not reach out a month. You might assume that is a shortage of data, of computing power, of model resolution. Fix all three and the answer is still a bit over a week.
Here is the counterintuitive part: that ceiling comes not from what we do not know but from what we do. The equations the atmosphere obeys are deterministic — feed in the same initial state ten thousand times and you get ten thousand identical trajectories, with no dice rolled anywhere. Deterministic, and still incomputable. Pulling those two apart was this field's most expensive lesson.
Several issues here deal with "you can't predict it," each by a different mechanism. This one is about sensitive dependence: tiny differences in the initial state amplified exponentially. Topic 9 is about how a single parameter drives a system all the way into chaos. Topic 11 splits the limits of prediction into two kinds (precision limits vs computational irreducibility). Topic 12 is about what noise itself can do. This issue answers one question only: why "deterministic" does not entail "predictable."
In the winter of 1961, the MIT meteorologist Edward Lorenz was running a toy weather model on a machine called a Royal McBee LGP-30 — a few dozen multiplications a second, slow enough to watch the results print out line by line.
He wanted a second look at an earlier stretch of output, so instead of starting over he restarted from the middle, typing in the numbers from the previous printout. The run that followed should have matched the old one exactly.
It didn't. The two curves tracked each other for a while, then drifted apart, and after a few simulated "months" they were describing two entirely different weathers.
The culprit turned out to be the printer. To save paper it had printed the value held in memory, 0.506127, as 0.506. What Lorenz typed back in was an initial condition truncated in the third decimal place. He wrote the episode up as the 1963 paper Deterministic Nonperiodic Flow — a title that is itself the finding: deterministic, and never repeating.
The point of this figure is not that they eventually separate. It is how alike they are beforehand. The error was there from the first instant; it was merely small. It grew the whole time, and the moment it reached the size of the system itself, forecasting became guessing.
So the abstract slogan "determinism is not predictability" means exactly this picture: the equations settle everything, but your knowledge of the initial state has finite precision — always — and finite precision buys only finite time.
The previous section said errors get amplified. This one turns that into a quantity you can compute — the single most useful step in this issue.
In a chaotic system the distance between two nearby trajectories grows roughly exponentially: d(t) ≈ d₀ · eλt. Here d₀ is the initial discrepancy and λ is the rate at which this system amplifies error, called the Lyapunov exponent. A positive λ is the core technical meaning of the word "chaos." For Lorenz's equations λ ≈ 0.9, meaning errors double about every 0.77 time units.
Now solve that backwards. If D is the largest error you can tolerate, your prediction survives for
T ≈ (1/λ) · ln(D / d₀)
Note that d₀ sits inside a logarithm. That one detail settles everything: improve the precision of your initial state tenfold and the predictable span grows by ln10/λ — a constant. Improve it tenfold again and you get the same small increment again. Exponential investment, linear return.
In atmospheric numbers: errors double in roughly a day and a half. Even with an initial state perfect down to instrument noise, the predictability ceiling for midlatitude weather sits at about two weeks. Run the arithmetic at that doubling rate: turning a 5-day forecast into a 10-day one means cutting initial error by something like a factor of ten, and pushing five days further means another factor of ten — by which point you are up against the ceiling anyway, and past a fortnight no amount of cutting helps. That is not an engineering difficulty. It is an exchange rate.
Attach a shelf life to every forecast you rely on: how fast its error doubles, times how many doublings you can absorb. Any point forecast past its shelf life comes off the dashboard — not improved, removed, replaced by a range or a set of scenarios. And before funding "more precision," ask what it returns: in a chaotic system the spend is exponential and the time you buy is linear.
This is the step most often skipped, and it is the only place where the word earns its keep in practice: erratic is not the same as random.
Put a chaotic signal and a noise signal side by side as curves and you usually cannot tell them apart — both jitter without visible pattern. The difference shows up plainly under a different kind of plot.
Change coordinates. Instead of drawing "how a quantity varies with time," draw the state. Take the signal's value at time t as the horizontal coordinate and its value slightly later (say 0.1 time units on) as the vertical one, and drop a point for every instant. This is called delay embedding, the standard trick for reconstructing a system's state from a one-dimensional record.
That shape on the left is a strange attractor: the system's state is confined to an object of very low dimension, circling forever, never repeating, never leaving. → ref · the Lorenz system → ref · phase space & attractors
The right-hand panel has no shape to speak of. In noise there is no constraint tying the next value to this one, so it fills the box.
Operationally the distinction becomes a test: find the handful of past states most similar to the present one, and check whether they went on to do the same thing for a short while. If they did, there is deterministic structure, short-range prediction is possible, and modelling pays. If they didn't, you are looking at noise, and no amount of model complexity does anything but fit the past.
One line to remember the difference by: chaos is highly predictable in the short run and utterly unpredictable in the long run; randomness is unpredictable at both ends.
Before funding a model for a pile of data that "looks like it has a pattern," run this one test: take the k historical states most similar to the current one and see whether their short-run continuations agree. If they agree, there is a skeleton and short-horizon prediction is worth the spend. If they don't, stop the modelling budget and switch to hedging and fault tolerance, because at this resolution the thing you want to predict is noise.
What is unpredictable is the trajectory, not the statistics. Everything usable in this issue comes from that sentence.
The shape in the previous section has two lobes (Lorenz's famous butterfly; the full picture is on the reference page). You cannot say whether step 3000 lands on the left lobe or the right one. You can say, with fair accuracy, what fraction of the long run is spent on the left, what the distribution of values looks like, how often extremes occur. Those quantities are insensitive to the initial condition — on the contrary, they are precisely what remains once the differences in initial conditions have been averaged away.
This is where weather stands to climate. Climate is not "a very long weather forecast"; it asks a different question — not whether it rains that day but where the whole rainfall distribution is moving. So the standard jab, "you can't even get next week right, why should I believe 2100," conflates two kinds of question: one about a trajectory, one about the statistics of an attractor.
The second thing still available is replacing one forecast with a crowd of them: the ensemble forecast. Since the initial state necessarily carries error, don't run a single trajectory; scatter a small cloud of initial states, run several dozen, and watch when they come apart. ECMWF and the US National Meteorological Center made this operational practice in 1992.
Move budget from "a better model" to "a crowd of initial states for the model you have." Change the reporting format accordingly: not a number but a fan, plus one sentence on the step at which the ensemble comes apart. The spread is the first thing to report, because it is the only honest measure of how much today's particular forecast can be trusted.
"Chaos" is among the most casually borrowed words in complexity science. Four boundaries before you use it.
First, the popular reading of the butterfly effect is essentially backwards. Lorenz's 1972 talk at the AAAS was titled "Does the flap of a butterfly's wings in Brazil set off a tornado in Texas?" — and even that title was supplied by the session's convener. The point was that if a perturbation that small suffices to rewrite the outcome, then no particular weather event can be traced to any particular cause. The popular version reads it as "your small good deed can change the world," which points the other way: chaos guarantees no single perturbation can be identified, aimed, or used to achieve anything. What it guarantees is that attribution fails.
Second, finding chaos in real data is very hard, and most of what was found did not hold up. From the late 1980s through the 1990s, papers reporting low-dimensional chaos appeared in economics, ecology, cardiology and EEG research. Once rigorous methods such as surrogate-data testing became standard, a good share of those conclusions collapsed — short, non-stationary, noisy records make those indicators give false positives. Seizure prediction is the emblematic case: early algorithms built on chaos measures mostly failed to beat chance under proper blinded evaluation. Detecting "there is deterministic structure" and "we can predict it" are two different achievements.
Third, chaotic does not mean uncontrollable — the least intuitive item here. In 1990 Ott, Grebogi and Yorke pointed out that precisely because the system is so sensitive to perturbation, a very small perturbation can hold it in place. A strange attractor has infinitely many unstable periodic orbits embedded in it; nudge gently at the right moments and the system can be kept on one of them. The method was later realised in lasers, electronic circuits and cardiac experiments. So "it's chaotic, might as well give up" is a mistaken inference: unpredictable and unintervenable are different properties.
Fourth, the "two-week limit" is not a promise that holds every day. The Lyapunov exponent is a long-run average. Actual predictability varies sharply with where the system currently sits — some weather patterns are forecastable to ten days, others fall apart in three. What deserves reporting is therefore never "our model is good for N days" but "today's run is good for N days." Measuring the ensemble spread is how that question gets answered.
You do, by the error you can tolerate — not the system. For one and the same system, "error under 1%" and "error under 50%" differ by a constant factor in predictable time (that is the ln(D/d₀) term). Which suggests a practical move: instead of improving the model, negotiate the tolerable error first. That is often far cheaper and buys the same order of gain.
Because at finite precision the two carry the same usable information. Which hints at something: the distinction between deterministic and random is not about the world but about the resolution of your model. The same river is deterministic mechanics at the molecular scale and better described by turbulence statistics at the engineering scale. Which to use follows not from "what the world really is" but from your measurement precision and the question you are answering.
Not directly. An ensemble covers uncertainty in the initial state; error in the model itself — approximated physics, insufficient resolution — is not in there, so ensembles are routinely overconfident, spreading less than the true uncertainty. Operational practice calibrates them against historical verification (reliability diagrams, skill scores). The transferable line: any self-generated uncertainty must be checked against reality, or it measures the model's confidence rather than the world's vagueness.
What is left is a different class of object to plan. Trajectories cannot be planned; constraints, boundary conditions and structural parameters can — and those change the shape and statistics of the attractor, which is the only thing predictable in the long run. Judge a long-range plan by whether it promises "in three years we will be at this point" or "in three years our distribution will have moved here."