Lably
Skip to content

Data-driven control system

Family of control systems

  • 7 min read
  • 4 chapters

Related on Lably

Through Optimization problem

In many control applications, trying to write a mathematical model of the plant is considered a hard task, requiring efforts and time to the process and control engineers. This problem is overcome by data-driven methods, which fit a system model to the experimental data collected, choosing it in a specific models class. The control engineer can then exploit this model to design a proper controller for the system. However, it is still difficult to find a simple yet reliable model for a physical system, that includes only those dynamics of the system that are of interest for the control specifications. The direct data-driven methods allow to tune a controller, belonging to a given class, without the need of an identified model of the system. In this way, one can also simply weight process dynamics of interest inside the control cost function, and exclude those dynamics that are out of interest.

Overview

The standard approach to control systems design is organized in two-steps:

  1. Model identification aims at estimating a nominal model of the system G^=G(q;θ^N), where q is the unit-delay operator (for discrete-time transfer functions representation) and θ^N is the vector of parameters of G identified on a set of N data. Then, validation consists in constructing the uncertainty set Γ that contains the true system G0 at a certain probability level.
  2. Controller design aims at finding a controller C achieving closed-loop stability and meeting the required performance with G^.

Typical objectives of system identification are to have G^ as close as possible to G0, and to have Γ as small as possible. However, from an identification for control perspective, what really matters is the performance achieved by the controller, not the intrinsic quality of the model.

One way to deal with uncertainty is to design a controller that has an acceptable performance with all models in Γ, including G0. This is the main idea behind robust control design procedure, that aims at building frequency domain uncertainty descriptions of the process. However, being based on worst-case assumptions rather than on the idea of averaging out the noise, this approach typically leads to conservative uncertainty sets. Rather, data-driven techniques deal with uncertainty by working on experimental data, and avoiding excessive conservativism.

In the following, the main classifications of data-driven control systems are presented.

Indirect and direct methods

There are many methods available to control the systems. The fundamental distinction is between indirect and direct controller design methods. The former group of techniques is still retaining the standard two-step approach, i.e. first a model is identified, then a controller is tuned based on such model. The main issue in doing so is that the controller is computed from the estimated model G^ (according to the certainty equivalence principle), but in practice G^≠G0. To overcome this problem, the idea behind the latter group of techniques is to map the experimental data directly onto the controller, without any model to be identified in between.

Iterative and noniterative methods

Another important distinction is between iterative and noniterative (or one-shot) methods. In the former group, repeated iterations are needed to estimate the controller parameters, during which the optimization problem is performed based on the results of the previous iteration, and the estimation is expected to become more and more accurate at each iteration. This approach is also prone to on-line implementations (see below). In the latter group, the (optimal) controller parametrization is provided with a single optimization problem. This is particularly important for those systems in which iterations or repetitions of data collection experiments are limited or even not allowed (for example, due to economic aspects). In such cases, one should select a design technique capable of delivering a controller on a single data set. This approach is often implemented off-line (see below).

On-line and off-line methods

Since, on practical industrial applications, open-loop or closed-loop data are often available continuously, on-line data-driven techniques use those data to improve the quality of the identified model and/or the performance of the controller each time new information is collected on the plant. Instead, off-line approaches work on batch of data, which may be collected only once, or multiple times at a regular (but rather long) interval of time.

Sign in to keep reading

3 more chapters are free with a Lably account.

More in Robotics