← Latest papers
⚡ electrical engineering

System Level Synthesis for Affine Control Policies: Model Based and Data-Driven Settings

This paper introduces a novel closed-loop parameterization that extends System Level Synthesis (SLS) to time-varying affine control policies in both model-based and data-driven settings, enabling equivalent formulations of general Model Predictive Control (MPC) problems that achieve performance comparable to traditional approaches.

Original authors: Lukas Schüepp, Giulia De Pasquale, Florian Dörfler, Carmen Amo Alonso

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

Original authors: Lukas Schüepp, Giulia De Pasquale, Florian Dörfler, Carmen Amo Alonso

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

The Big Picture: Teaching a Robot to Drive Without a Map

Imagine you are trying to teach a robot to drive a car from point A to point B. The car has a weird quirk: it always drifts slightly to the right because of a heavy weight in the trunk (this is the "affine" part of the system).

For a long time, engineers had two main ways to solve this:

  1. The Map Method (Model-Based): You build a perfect mathematical map of the car's physics. You calculate exactly how the steering wheel needs to turn to counteract that heavy weight.
  2. The Memory Method (Data-Driven): You don't know the physics, but you have a video recording of the car driving perfectly in the past. You tell the robot, "Just do what worked in the video."

The Problem:
Most existing "smart" control methods (like the one called System Level Synthesis or SLS) are great at handling big, complex systems, but they are very rigid. They only work if the car behaves in a perfectly straight line (linear). If the car has that heavy weight causing a constant drift, or if the road conditions change, these old methods struggle. They try to force a straight-line solution onto a curved problem, which isn't efficient.

The New Idea: The "Drift-Aware" GPS

This paper introduces a new way to control systems called Affine System Level Synthesis.

Think of the old method as a GPS that only knows how to drive on a perfectly flat, straight highway. It gets confused if the road tilts or if the car has a heavy load.

The authors' new method is like a GPS that understands "drift." It realizes that sometimes you need to steer slightly left just to stay straight because of that heavy weight in the trunk. It allows the control policy to have two parts:

  1. The Reaction: "If the car drifts left, steer right." (This is the linear part).
  2. The Constant Push: "Also, always keep the steering wheel turned slightly right to fight that heavy weight." (This is the new "affine" part).

How They Did It (The Two Settings)

The paper shows this new method works in two different scenarios:

1. The "I Know the Rules" Scenario (Model-Based)
Imagine you have the car's manual and know exactly how heavy the trunk is.

  • What they did: They rewrote the math so the computer can plan a route that accounts for that constant weight while reacting to traffic.
  • The Result: They proved that this new way of planning is mathematically identical to the best possible traditional planning. It's just a different, more flexible way of writing the same instructions.

2. The "I Only Have a Video" Scenario (Data-Driven)
Imagine you don't have the car's manual. You don't know the weight of the trunk or the engine power. You only have a video of the car driving successfully in the past.

  • What they did: They created a trick using a "Hankel Matrix" (think of this as a giant, organized scrapbook of every move the car ever made). They showed that you can look at this scrapbook and figure out exactly how to drive the car in the future, including how to handle that constant weight, without ever knowing the weight's actual value.
  • The Result: The robot can learn to drive perfectly just by looking at past examples, even if the system has that constant "drift."

The "Aha!" Moment: Why This Matters

The authors ran a simulation using a model of a power grid generator (which naturally has friction, acting like that heavy weight in the trunk).

They compared three drivers:

  1. The Traditional Driver: Uses the standard, complex math to plan the route.
  2. The New "Drift-Aware" Driver (Model-Based): Uses their new method with the known physics.
  3. The New "Drift-Aware" Driver (Data-Driven): Uses their new method with only past video data.

The Outcome: All three drivers arrived at the destination at the exact same time, took the exact same path, and used the exact same amount of fuel.

The Takeaway

This paper doesn't invent a new type of car or a new engine. Instead, it invents a new way of writing the instruction manual for the driver.

  • Old Manual: "Turn the wheel based on where you are." (Fails if there is a constant drift).
  • New Manual: "Turn the wheel based on where you are, plus a constant adjustment for the drift."

The authors proved that this new manual works just as well as the old, complex one, but it is much more flexible. It works whether you know the car's physics perfectly or if you are learning entirely from past video footage. This opens the door for controlling complex, real-world systems (like power grids or social networks) that don't behave in perfectly straight lines.

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 →