← Latest papers
⚡ electrical engineering

Distributed model predictive control without terminal cost under inexact distributed optimization

This paper proposes a novel distributed model predictive control scheme for linear discrete-time systems with coupled constraints that guarantees closed-loop stability without a terminal cost by incorporating a relaxed dynamic programming-based stability constraint and solving the resulting optimization problem via a violation-free distributed approach with constraint tightening.

Original authors: Xiaoyu Liu, Dimos V. Dimarogonas, Changxin Liu, Azita Dabiri, Bart De Schutter

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

Original authors: Xiaoyu Liu, Dimos V. Dimarogonas, Changxin Liu, Azita Dabiri, Bart De Schutter

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 a group of autonomous delivery trucks driving down a highway in a tight formation. They need to stay close to each other to save fuel, but they must never crash, and they all need to agree on how fast to go. This is a classic problem in Distributed Model Predictive Control (MPC).

Think of MPC as a "crystal ball" for each truck. Every second, each truck looks ahead into the future (say, 10 seconds), calculates the best path for itself and its neighbors, and then only takes the very first step of that plan before recalculating everything again.

However, doing this calculation for a whole fleet is hard. If every truck tries to solve the math for the entire group at once, it's too slow. So, they try to solve it locally, each truck doing its own math while talking to its neighbors. But here are the two big headaches this paper solves:

  1. The "Safety Net" Problem: Usually, to prove the trucks won't crash or go out of control, engineers have to design a complex "safety net" at the very end of the prediction (called a terminal cost). It's like forcing every truck to promise, "I will be at a specific parking spot exactly 10 seconds from now." This is very rigid and hard to coordinate.
  2. The "Rushed Math" Problem: In the real world, trucks have limited computing power and can't wait forever for the math to be perfect. They have to stop calculating early. If they stop too early, they might accidentally break the rules (like driving too close to the truck in front) because their math wasn't finished.

The Paper's Solution: A New Way to Drive

This paper proposes a clever new way to manage this fleet without the rigid "safety net" and without breaking the rules, even when the math is rushed.

1. No More "Parking Spot" Promises (No Terminal Cost)

Instead of forcing every truck to promise a specific destination at the end of the 10-second window, the authors introduce a new rule based on Relaxed Dynamic Programming.

  • The Analogy: Imagine a teacher telling a student, "You don't need to finish the whole book by Friday. Just make sure that every time you read a chapter, you've learned something new and are getting closer to understanding the story."
  • How it works: The paper adds a specific constraint to the math. It tells each truck: "Your effort today must be slightly better than your effort yesterday, adjusted by a safety factor." This creates a "downward slope" in the math. As long as the trucks keep sliding down this slope, the system is guaranteed to be stable and safe, without needing to force them to a specific "parking spot" at the end.

2. The "Invisible Fence" for Rushed Math (Constraint Tightening)

Since the trucks have to stop calculating early (inexact optimization), there's a risk they might accidentally drift into a "no-go zone" (like getting too close to another truck) before the math is fully settled.

  • The Analogy: Imagine you are walking through a narrow hallway with a friend, but you are both wearing blindfolds and only checking your position every few seconds. To be safe, you don't walk right down the center line; you walk a few inches away from the walls. This extra space is your "buffer."
  • How it works: The paper uses a technique called Constraint Tightening. It tells the trucks: "For the purpose of your calculations, pretend the hallway is narrower than it actually is."
    • If the real rule is "Stay 10 meters apart," the math tells the truck to "Stay 12 meters apart" during the calculation.
    • This creates a safety buffer. Even if the truck stops calculating early and makes a small mistake, it will still be safely within the real 10-meter limit.
    • Crucially, the paper introduces a method to update these "invisible fences" dynamically as the trucks talk to each other, ensuring they never run out of space (feasibility) during the calculation process.

The Result: A Parallel Dance

The authors tested this with a simulation of three trucks following a leader.

  • Parallel Processing: Each truck does its own math at the same time (in parallel), just like a team of dancers practicing their own moves simultaneously before coming together.
  • Stability: The simulation showed that even with the "rushed math" (stopping iterations early), the trucks stayed stable, kept their distance, and followed the leader perfectly. The "cost" (a measure of how well they are doing) went down to zero, proving the system is working.

Summary

In short, this paper teaches a fleet of robots how to:

  1. Stay stable without forcing them to hit a specific target at the end of their plan (removing the "terminal cost").
  2. Stay safe even when they have to stop calculating before the math is perfect, by building a temporary "safety buffer" into their rules (using "constraint tightening").

It's like teaching a group of dancers to stay in perfect formation even if they can't hear the music perfectly and have to guess the next step, by giving them a little extra personal space to avoid tripping over each other.

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 →