A posteriori closure of turbulence models: are symmetries preserved?

This paper evaluates an a posteriori turbulence closure for a shell model that integrates physical equations into a neural network, finding that while it successfully reproduces high-order statistical moments, it fails to preserve scale invariance symmetries near the cutoff, revealing a fundamental limitation for subgrid-scale modeling.

Original authors: André Freitas, Kiwon Um, Mathieu Desbrun, Michele Buzzicotti, Luca Biferale

Published 2026-02-24
📖 5 min read🧠 Deep dive

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 the next month. You have a supercomputer, but even with all its power, it can't track every single molecule of air, every tiny swirl of wind, and every drop of rain. There are simply too many details.

So, scientists use a trick called Large Eddy Simulation (LES). Think of it like watching a storm from a helicopter. You can clearly see the massive, swirling clouds (the "large eddies"), but you can't see the tiny, chaotic gusts of wind right under the helicopter blades (the "subgrid scales"). To make the simulation work, you have to guess what those tiny gusts are doing based on the big clouds you can see. This guessing game is called closure.

For decades, scientists have used rough rules of thumb to make these guesses. But recently, they started using Artificial Intelligence (AI) to learn the rules directly from data.

The Experiment: A Simplified Universe

In this paper, the researchers didn't try to simulate the entire atmosphere (which is too hard). Instead, they used a "toy universe" called a Shell Model.

  • The Analogy: Imagine a set of Russian nesting dolls, but instead of being inside each other, they are arranged in a line. Each doll represents a different size of wind swirl. The biggest doll is the biggest storm; the smallest doll is the tiniest breeze.
  • The Problem: The AI is only allowed to see the big dolls. It has to guess what the tiny, hidden dolls are doing so the whole line of dolls behaves realistically.

The New Approach: "Learning by Doing"

Most AI models are trained like a student taking a pop quiz. They are shown a picture of the big dolls and asked, "What are the small dolls doing right now?" If they get it wrong, they are corrected immediately. This is called an a priori approach.

The researchers in this paper tried something different, which they call Solver-in-the-Loop (or A Posteriori).

  • The Analogy: Instead of a pop quiz, imagine the AI is the pilot of a drone flying through a storm. It doesn't just guess the wind; it flies the drone. If it guesses the wind wrong, the drone drifts. The AI learns not just to be right for one second, but to keep the drone flying smoothly for a long time, even if it makes small mistakes along the way. It learns how its own errors ripple through time.

The Results: A Tale of Two Successes

The researchers tested their AI pilot and found it was incredibly good at some things, but had a specific blind spot.

1. The Good News (The Big Picture):
The AI was fantastic at predicting the average behavior of the storm. It could tell you how much energy the big clouds had, how fast they were spinning, and the general "mood" of the turbulence. If you looked at the statistics of the big dolls, the AI's simulation looked almost identical to the real thing.

2. The Bad News (The Hidden Symmetry):
Here is where the paper gets interesting. In turbulence, there is a hidden "rule of symmetry." It's like a secret handshake between the big dolls and the tiny dolls. No matter how you zoom in or out, the relationship between the sizes of the swirls should look the same (this is called scale invariance).

  • The Discovery: The researchers found that while the AI was great at the big picture, it broke this secret handshake near the cutoff point (where the big dolls end and the tiny hidden ones begin).
  • The Metaphor: Imagine a dance floor where everyone is dancing in a perfect, repeating pattern. The AI kept the big dancers moving perfectly. But right at the edge of the stage, where the big dancers hand off the rhythm to the invisible tiny dancers, the AI got the rhythm slightly wrong. The tiny dancers started stumbling, and the perfect pattern broke.

Why Did This Happen?

The authors suggest the problem isn't that the AI wasn't "smart" enough or that they didn't give it enough data. The problem is structural.

  • The Memory Problem: The AI they used is Markovian. In plain English, this means it has no memory. It only looks at the current state of the big dolls to guess the tiny ones. It doesn't remember how the big dolls got there.
  • The Real World: In real turbulence, the tiny swirls don't just react to the current big swirl; they react to the history of the big swirls. It's like trying to predict a car's speed by only looking at the gas pedal right now, without remembering if the driver just slammed on the brakes five seconds ago.
  • The Solution: To fix this, the AI needs to be given a "memory" (mathematically, a memory kernel) so it can remember the past interactions between the big and small scales.

The Takeaway

This paper is a success story with a warning label.

  • Success: We can now build AI that simulates turbulence very accurately for the big, visible parts of the flow.
  • Warning: If we want to simulate the extreme events (the rare, wild fluctuations) or the exact interaction between the visible and invisible parts, a simple "guess the next step" AI isn't enough. We need an AI that understands the history of the flow, not just the present moment.

It's like saying, "We built a car that drives perfectly on a straight highway, but it struggles to navigate a sharp turn because it forgot where it came from." The next step is to give the car a memory so it can handle the whole journey.

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 →