← Latest papers
🤖 machine learning

Single vs. Multiple Branches in DeepONet and S-DeepONet: Network Architecture Follows Coupling in Multiphysics Systems

This paper demonstrates that for DeepONet and S-DeepONet architectures, single-branch designs outperform multi-branch variants in tightly coupled multiphysics systems by fostering shared latent representations, while multi-branch approaches remain superior for decoupled tasks, collectively enabling full-field predictions up to 1.8×1041.8 \times 10^4 times faster than traditional solvers.

Original authors: Jaewan Park, Kazuma Kobayashi, Qibang Liu, Seid Koric, Diab Abueidda, Syed Bahauddin Alam

Published 2026-06-12
📖 5 min read🧠 Deep dive

Original authors: Jaewan Park, Kazuma Kobayashi, Qibang Liu, Seid Koric, Diab Abueidda, Syed Bahauddin Alam

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 teach a computer to predict how complex physical systems behave—like how heat spreads through a metal block while electricity flows through it, or how steel cools and changes shape as it solidifies. These aren't just simple problems; they are "multiphysics" puzzles where different forces (heat, electricity, stress) are tightly tangled together, influencing each other constantly.

For a long time, scientists have used powerful computer simulations (like Finite Element Analysis) to solve these puzzles. But these simulations are slow, like trying to solve a Rubik's cube by checking every single move one by one. To speed things up, researchers use "surrogate models"—AI shortcuts that learn from past simulations to predict the future instantly.

This paper asks a very practical question: When building these AI shortcuts, should we design them to treat different physical forces as separate teams working in parallel, or as one big, unified team working together?

The authors tested two main architectural styles using a type of AI called DeepONet:

  1. The "Single-Branch" Team (The Unified Squad): Imagine a single group of workers who all look at the entire picture together. They share a common notebook (a shared "latent space") where they write down everything they see. They discuss the heat, the electricity, and the stress all at the same time, understanding how one affects the other immediately.
  2. The "Multi-Branch" Team (The Specialized Departments): Imagine two separate teams. One team only looks at the heat, and the other team only looks at the electricity. They work in isolation, write their own reports, and then only at the very end do they slap their reports together to see the final result.

The Experiments: Three Different Puzzles

The researchers tested these two approaches on three different scenarios to see which "team structure" worked best.

1. The Simple Puzzle (Reaction-Diffusion)

  • The Scenario: A single physical process (like a chemical spreading in water) with two different inputs (a source and a reaction rate).
  • The Result: The Multi-Branch team won. Since the inputs were independent (one didn't really change the other), having specialized experts who focused on just one thing allowed them to be slightly more precise. It's like having a specialist for the engine and a specialist for the tires when building a car; they don't need to talk much to do their jobs well.

2. The Tangled Puzzle (Electro-Thermal)

  • The Scenario: Electricity flowing through a wire creates heat, and that heat changes how electricity flows. They are locked in a dance where you can't separate them.
  • The Result: The Single-Branch team crushed it. The Multi-Branch team struggled because by the time they tried to combine their separate reports, they had already missed the subtle ways the heat and electricity were influencing each other in real-time. The Unified Squad, sharing a common understanding from the start, captured these interactions perfectly. The error for the Multi-Branch team was huge (over 15% in some cases), while the Single-Branch team was nearly perfect (under 1%).

3. The Heavy Lifting Puzzle (Steel Solidification)

  • The Scenario: Molten steel cooling down. As it cools, it shrinks and creates stress. The temperature dictates the stress, and the stress changes the temperature. It's a highly complex, "path-dependent" system (the history of how it cooled matters).
  • The Result: Again, the Single-Branch team was the clear winner. The steel's behavior is so tightly coupled that separating the "temperature team" from the "stress team" led to significant errors. The Unified Squad, which learned the relationship between heat and stress simultaneously, predicted the stress levels much more accurately.

The Big Takeaway

The paper's main discovery is a simple rule of thumb for designing these AI models: Match the AI's structure to the physics.

  • If the physics are "decoupled" (independent): Use Multi-Branch networks. Let the specialists do their own thing.
  • If the physics are "coupled" (tightly tangled): Use Single-Branch networks. Force the AI to learn the connections between the forces from the very beginning, just like a monolithic (all-in-one) solver in traditional engineering.

The Speed Bonus

Beyond just accuracy, the paper highlights a massive speed advantage. Once these AI models are trained, they can predict the behavior of these complex systems 18,000 times faster than the traditional, heavy-duty computer simulations.

  • Traditional Solver: Takes about 5.5 minutes to solve one scenario.
  • AI Surrogate: Takes about 0.02 seconds.

This means that tasks that used to take hours or days can now be done in milliseconds, opening the door for real-time monitoring and control in things like manufacturing and energy systems.

Summary Analogy

Think of it like cooking a complex stew.

  • If you are making a salad where the tomatoes don't change the lettuce, you can have one person chop the tomatoes and another chop the lettuce, then mix them at the end (Multi-Branch).
  • But if you are making a stew where the meat changes the flavor of the broth, and the broth changes how the meat cooks, you need one chef who tastes, adjusts, and stirs everything together constantly (Single-Branch). If you try to cook the meat and the broth separately and mix them at the end, the stew will taste wrong.

This paper proves that for "stews" (tightly coupled physics), the single chef approach is not just better; it's necessary for getting the right result.

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 →