← Latest papers
⚡ electrical engineering

Predictor-Based Output-Feedback Control of Linear Systems with Time-Varying Input and Measurement Delays via Neural-Approximated Prediction Horizons

This paper proposes and analyzes two methods—a numerical ODE integration approach and a data-driven neural operator learning technique—for approximating the inverse delay mapping required in predictor-based output-feedback control of linear systems with time-varying input and measurement delays, proving that the resulting closed-loop system achieves global exponential stability when the prediction horizon is approximated with sufficient accuracy.

Original authors: Luke Bhan, Miroslav Krstic, Yuanyuan Shi

Published 2026-04-01
📖 5 min read🧠 Deep dive

Original authors: Luke Bhan, Miroslav Krstic, Yuanyuan Shi

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 driving a car, but there's a strange glitch: you can only see the road through a rearview mirror that shows you where you were 5 seconds ago, and your steering wheel only turns the car 5 seconds after you move it.

If you try to drive normally, you'll crash. You'll turn left to avoid a tree, but because of the delay, the car will keep going straight, hit the tree, and then turn left.

To fix this, you need a Predictor. You need a co-pilot who looks at the delayed information, calculates where the car will be in the future, and tells you to steer based on that future position, not your current (delayed) one.

This paper is about building that co-pilot for complex systems where the "delay" isn't a fixed 5 seconds. Sometimes the delay is 2 seconds, sometimes 8, and it changes constantly like traffic. The big problem? To calculate where the car will be, you need to solve a tricky math puzzle (finding the "inverse" of the delay) that usually has no simple answer.

Here is how the authors solved it, using simple analogies:

1. The Problem: The "Time Travel" Puzzle

In a perfect world, if you know the delay is exactly DD seconds, you just look back DD seconds to know where you are. But when the delay changes (Time-Varying Delay), you have to solve a riddle: "At what exact moment in the past did the signal leave, so that it arrives right now?"

Mathematically, this is like trying to find the exact key that opens a lock, but the lock changes its shape every second. For most real-world systems, there is no "closed-form" formula (a simple equation) to find this key instantly. You have to guess and check, which is slow and computationally heavy.

2. The Two Solutions: The "Calculator" vs. The "Genius AI"

The authors propose two ways to solve this riddle quickly enough to keep the car safe.

Approach A: The Step-by-Step Calculator (Numerical Integration)

Think of this as a very diligent, slow mathematician.

  • How it works: Instead of solving the whole riddle at once, the mathematician takes tiny steps. They estimate the answer, take a tiny step forward, estimate again, and repeat.
  • The Analogy: Imagine walking across a river by stepping on stones. You don't know the exact path, so you look at the next stone, step there, look at the next, and so on.
  • Pros: It's reliable and based on solid math.
  • Cons: The longer the river (the longer the time horizon), the more stones you have to step on. It gets slower and slower as the delay gets longer.

Approach B: The Trained Genius (Neural Operators)

Think of this as a super-smart AI that has practiced this riddle thousands of times.

  • How it works: The authors trained a Neural Network (a type of AI) on thousands of examples of different delays. The AI learned the pattern of how to solve the riddle without doing the math step-by-step every time. It's like a grandmaster chess player who doesn't calculate every move but "sees" the right move instantly.
  • The Analogy: Instead of counting steps to cross the river, the AI has a map and a jetpack. It knows exactly where to land instantly.
  • Pros: It is incredibly fast (up to 20x faster than the calculator method).
  • Cons: It needs to be trained first (which takes time offline), and if the delay behaves in a way it has never seen before, it might make a small mistake.

3. The Safety Net: "Good Enough" is Okay

The most important finding of the paper is about stability.

The authors proved that you don't need the co-pilot to be perfect. You just need them to be close enough.

  • The Metaphor: If your co-pilot tells you to steer 5.1 degrees instead of 5.0 degrees, the car might wobble a tiny bit, but it won't crash. As long as the error is small, the system remains stable.
  • They mathematically proved that even if you use the "Genius AI" and it makes a tiny mistake, or if the "Calculator" is slightly off, the car (the system) will still stabilize and not crash, provided the mistake isn't too big.

4. The Real-World Test

They tested this on a simulated system (like a drone or a chemical plant) with messy, changing delays.

  • The Result: The AI method (Neural Operator) was the fastest, solving the problem in milliseconds. The Calculator method was accurate but slower.
  • The Trade-off: You can choose your poison. If you need maximum precision and have a slow computer, use the Calculator. If you need to react instantly (like in high-speed robotics) and can tolerate a tiny bit of approximation error, use the AI.

Summary

This paper is about teaching machines to drive themselves when their sensors and controls are laggy and unpredictable.

  1. The Problem: The math to fix the lag is too hard to solve instantly.
  2. The Fix: Use either a slow, step-by-step math method or a fast, trained AI method to guess the solution.
  3. The Guarantee: As long as the guess is close enough, the system stays safe and stable.

It's a bridge between heavy, slow mathematics and fast, modern Artificial Intelligence, ensuring that our future automated systems don't crash just because of a little bit of lag.

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 →