← Latest papers
📊 statistics

Do Stationarity Transformations Actually Improve Time Series Forecasts? A Controlled Experimental Evaluation

This controlled experimental evaluation reveals that standard stationarity transformations generally fail to improve time series forecast accuracy—often worsening performance for trended data—except in cases of heteroscedasticity where variance stabilization proves beneficial, suggesting that empirical out-of-sample testing should guide transformation selection over theoretical assumptions.

Original authors: Bhanu Suraj Malla, Yuqing Hu

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

Original authors: Bhanu Suraj Malla, Yuqing Hu

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 trying to predict the weather for next week. For decades, the standard advice from the "experts" has been: "Before you try to predict the weather, you must first strip away all the patterns that make the weather change, like the seasons or the general warming trend, until the data looks completely flat and boring."

The logic was that if the data is "boring" (statisticians call this stationary), the prediction machine will work better.

This paper is a giant reality check. The authors set up a massive laboratory experiment to test if this old advice actually works. They built 12 different types of "fake weather" (synthetic data) with known patterns—some had trends, some had seasons, some had wild swings in intensity—and then tried to predict them using 7 different prediction machines. They tested 14 different ways of "cleaning" the data before feeding it to the machines.

Here is what they found, translated into everyday language:

1. The "Scrubbing" Mistake (Differencing)

The most common way to "clean" data is called differencing. Imagine you have a video of a car driving up a hill. The car is clearly going up. To make the video "stationary" (flat), you take a knife and cut out the "going up" part, leaving you with a video of the car just vibrating in place.

  • The Paper's Finding: This is a disaster for prediction. By cutting out the "going up" part, you threw away the most obvious clue about where the car is going.
  • The Result: In almost every case, this "scrubbing" made the predictions worse, not better. It's like trying to guess where a runner will be in 10 seconds by ignoring the fact that they are running forward. The paper found that even for models that were supposed to need this "scrubbing," it actually hurt their performance.

2. The One Exception: The "Volume Knob" (Variance Stabilization)

There was one type of cleaning that actually helped: Variance Stabilization (using Log or Box-Cox transforms).

  • The Analogy: Imagine you are listening to a radio station where the volume suddenly gets incredibly loud and then very quiet. It's hard to hear the song. You don't cut out the song; you just turn on a "compressor" that keeps the volume steady so you can hear the music clearly.
  • The Paper's Finding: When the data had "wild volume swings" (heteroscedasticity), using a "volume knob" to smooth out the loud and quiet parts improved the predictions. This works because it fixes a problem with the noise without deleting the signal (the actual pattern).

3. The "Perfect Match" Myth

A common belief is: "If I have a trend, I should use a trend-removing tool. If I have seasons, I should use a season-removing tool."

  • The Paper's Finding: Even when they used the "perfect" tool for the specific problem (e.g., using a trend-remover on a trend), it still made the predictions worse 82% of the time.
  • Why? Because the tool that removes the "problem" also accidentally removes the "clue" the computer needs to guess the future. It's like trying to fix a wobbly table by sawing off the leg that's wobbly. Sure, it's no longer wobbly, but now the table is broken and useless.

4. The Real-World Test

To make sure this wasn't just a lab trick, they tested these ideas on real data: TSA airport passenger numbers. This data has a clear trend (people are flying more again), clear seasons (holidays), and changing volume.

  • The Result: The "scrubbing" methods (differencing) made the predictions terrible. The "volume knob" methods (Log/Box-Cox) actually helped a little bit. The best result? Just using the raw data without the aggressive "scrubbing."

The Big Takeaway

The paper argues that we have been following a rulebook that is too focused on making data look "statistically perfect" (stationary) rather than "predictively useful."

  • Old Rule: "Make the data flat and boring before you predict."
  • New Rule: "Don't throw away the baby with the bathwater."

If you have data that swings wildly in volume, smooth the volume. But if you have a clear trend or season, leave it alone. The prediction machines are smart enough to handle the trends; if you try to "fix" them by removing the pattern, you are actually blinding the machine.

In short: Sometimes, the best way to prepare your data for a prediction is to do absolutely nothing to it.

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 →